What Happens After Someone Fills In Your Contact Form

The short answer: A submitted form is not a handled enquiry. Between the click and a person replying there are six or seven separate steps, and most businesses have never tested them end to end. The fix is not a better form. It is tracing the whole path yourself, from a real phone, and fixing the step where it stops.

The path, not the form

Here is what has to happen after someone taps Send:

1. The form validates and submits without silently dropping a field.
2. The submission is stored somewhere you can look it up later.
3. A notification reaches the people responsible.
4. One named person picks it up and owns the reply.
5. That person replies within a time the business has agreed on.
6. The visitor gets a confirmation that tells them what happens next.
7. A record of the conversation survives past that person's inbox.

Most enquiry problems are one of these steps failing quietly, not a design problem on the page. Businesses often redesign the form when the actual break is step three or four.

Five breaks worth checking first

A notification is not a delivery. A message arriving in a shared channel or a general inbox feels like the job is done. Nobody has replied yet. If everyone can see it, it is easy for each person to assume someone else is on it.

A confirmation with no commitment. "Thanks, we'll be in touch" tells the visitor nothing. "We reply to enquiries within one business day, and if it is urgent call (825) 967-9337" sets an expectation you can be held to, which is the point.

Delivery failures you never see. Forms that email from your own domain can fail SPF or DKIM checks and land in spam, and some form tools fail silently when a required field changes. If you have never submitted a test enquiry and confirmed it arrived, assume some are being lost.

No owner on the weekend. Plenty of enquiries arrive Friday evening. Decide who checks and when, even if the answer is "Monday morning," and make the confirmation message say so.

Records that only live in one inbox. If the only copy of a conversation is in the inbox of whoever replied, you cannot answer basic questions later: how many enquiries came in, how many turned into work, what people were asking about.

Following up without breaking CASL

Canada's anti-spam legislation applies to the messages you send afterwards, so the enquiry itself matters legally. In the CRTC's guidance on implied consent, an inquiry or application about your business gives you implied consent to send commercial electronic messages for six months. A purchase or contract gives you two years from that transaction.

Three practical consequences:

• Replying to someone's question sits comfortably inside that window. Adding them to a newsletter that keeps sending eighteen months later does not, unless you obtained express consent.
• Every commercial message needs your identification details and a working unsubscribe, and unsubscribes must be honoured within 10 business days.
• You have to be able to show how consent arose. The CRTC expects records kept close to when consent was obtained, which means the form submission, its timestamp and what the person agreed to should be stored, not just remembered.

Enquiry data is also personal information. Alberta's guidance on protecting personal information covers what you collect, why, and how long you keep it. Decide the retention period on purpose rather than keeping every submission forever by default.

Where an assistant helps, and where it does not

A website assistant answers the routine questions at the moment someone is deciding: what a service includes, what you need from them, how pricing gets scoped, whether you serve their area. It can collect contact details for follow-up when the person agrees, and hand the conversation to a person when it needs judgment.

What it does not do is reply on your behalf. A visitor who has been told a person will follow up is waiting for a person. Any assistant worth putting on your site should have clear limits, a visible route to a human, and a record of the conversation the team can review. Unanswered questions are useful too, since they show what your website has not explained yet.

One more thing to check while you are in there: Google ended chat and call history in Business Profiles in July 2024. If a listing still says customers can message you, that is a dead route. Make sure the phone number and website link on the profile go somewhere a person actually answers.

The 20-minute test

Do this from your phone, on mobile data, not from the office network:

1. Submit a real enquiry through your own form, using a personal email address.
2. Time how long until a human reply arrives. Not the automatic one, the real one.
3. Check whether the confirmation message says when to expect a reply and how to reach a person sooner.
4. Check your spam folder for the confirmation, and ask whoever should have been notified whether they saw it.
5. Try submitting with a field left blank, and confirm the error message says what to fix.
6. Look up that enquiry in whatever system holds it a day later. If you cannot find it, there is no record.
7. Call the phone number on your Google Business Profile and see where it rings.

Write down which steps failed. That list is a better project plan than any website redesign.

Where Lumin fits

Most enquiry problems are plumbing between tools rather than design, which is the sort of work we do:

• AI assistants that answer routine pre-sale questions, capture details with consent and escalate to a person, with the conversation kept for review.
• Connected workflows that route an enquiry to a named owner, confirm receipt and keep a record you can count later.

If you want a hand running the test above and fixing what it turns up, book a discovery call.