Why website enquiries get missed between your form, inbox and CRM

You paid for a website. Someone took the time to explain what they needed. Then nothing happened—not because you didn't want the work, but because the enquiry never reached the right person with enough information to respond.

Before buying another tool, follow one enquiry through the system you already have. The useful question isn't just “Does the form work?” It's “Can we see what the customer asked, who owns the reply, and what happens next?”

1. Check whether the enquiry was actually saved

A thank-you screen is not the same as a usable customer record. Start with the form's submission history or whichever system is supposed to retain the enquiry. Find the original request and its submission time. If you cannot find it, investigate capture before changing email notifications.

Keep the customer's service selection and written question alongside their contact details. A name and email alone leave the person replying to guess why the customer contacted you. Record only the information needed to handle the request, with access limited to the people doing that work.

2. Separate the record from the notification

An enquiry can be saved while its email alert goes elsewhere. Check who is meant to receive notifications, whether their account is active, and whether mailbox rules or junk filtering moved the message.

For example, HubSpot documents both user-level notification settings and form recipients. It also notes that a contact-owner notification has nobody to notify when the contact has no owner. Those are separate checks—not proof that every missing enquiry is an email problem. See HubSpot's notification guidance.

Treat the email as an alert to work waiting, not your only record that the work exists.

3. Check the handoff into your CRM

If the form and CRM are connected through automation, find the specific submission in the automation's history. Did it trigger? Did the next step complete? Does the resulting record contain the actual request?

Timing matters too. Zapier distinguishes polling triggers, which check periodically, from instant triggers. Confirm the behaviour of your particular connection before assuming a short delay means a failure. Zapier explains the distinction here.

Don't replay an entire batch blindly. First check whether some records or messages already exist. Otherwise, fixing a missed handoff can create duplicate contacts or send a customer the same introduction twice. HubSpot's workflow troubleshooting reference includes examples of failures involving existing records and missing associations.

4. Give each enquiry one accountable person

“It goes to the team inbox” still doesn't tell you who is replying. Assign one owner and a backup for when that person is unavailable. Agree a response target that fits your staffed hours and tell customers honestly what to expect.

Before replying, read the request and any conversation already underway. If someone has already answered, continue that discussion. Don't restart with a second “Thanks for reaching out.”

Your working record should show the original request, source, owner, last contact, next action and due date. A reply is a completed action only once it has actually been sent—not when a draft has been written.

5. Test the whole journey

Use a clearly labelled test enquiry with contact details you control. Include a distinctive phrase in the message so you can follow the same test from the form to the inbox and tracker.

Check these five points:

• The submission is retained with its time and full message.
• The intended person receives an alert.
• The CRM or tracker has the correct details, without an unnecessary duplicate.
• An owner and next action are visible.
• The reply process works and its outcome can be recorded.

Keep the test out of genuine lead and sales totals. Repeat the check after relevant changes to the form, inbox rules or integration—not just on launch day.

A simple daily check catches what alerts miss

Compare new submissions against your working tracker. Look for missing records, unassigned enquiries and replies that are overdue. Review individual records, not only totals: one duplicate and one missing enquiry can make two systems appear to agree.

Here's a hypothetical example: three people submitted enquiries yesterday. Two have replies recorded. The third has a CRM entry but no owner. That isn't a reason to replace the whole CRM. The immediate fix is to assign and answer the enquiry, then correct the rule that left it unassigned.

Fix the broken step before rebuilding everything

Sometimes the answer is a recipient setting. Sometimes it's a clearer daily routine. Sometimes the existing tools genuinely need a better connection. A custom CRM should be a considered option, not the default answer to a missed email.

Bozman Horizon helps map these handoffs and scope a practical system around the work. Explore CRM and business systems and tell us which step is getting missed. Start with your tools and the problem—not passwords or private customer records.