Website and CRM: why enquiries vanish between the form and the sales team
- Email is the least reliable link in the chain: messages land in spam, in tabs, and nowhere at all.
- The right pattern sends every enquiry to several places at once: CRM, messenger and a backup record.
- The most expensive losses are not technical but in response time — an hour is enough for interest to cool.
- Checking your own chain takes ten minutes, and is worth doing monthly.
The ads are running, analytics shows conversions, and the sales team says there are hardly any enquiries. Usually both are right: the enquiries exist, and not all of them reach the sales team.
Where the chain breaks
| Link | What goes wrong | How you notice |
|---|---|---|
| The form | Validation fails without explanation, a needless field is required | Analytics shows form opens with no submissions |
| Sending | The script fails silently, the visitor sees “thank you” | Only a test submission reveals it |
| The message lands in spam or in the Promotions tab | Enquiries arrive in batches | |
| CRM | A deal is created with nobody assigned | Cards that never move |
| The manager | Saw it in the evening, called back the next day | Nobody measures time to first response |
Why email is a poor single link
The standard way a site sends mail is roughly this: the server tries to deliver the message and then forgets about it. From there it can go to spam, to a secondary tab, into a corporate filter, or nowhere. The site never learns about it and never tells you.
So email should be one of three channels. The pattern that works: the enquiry goes to the CRM, is duplicated into a messenger and is written to a table on the site itself. Breaking all three paths at once takes effort.
The messenger notification is the most underrated part of the setup. It arrives in a second, it is visible on a phone immediately, and people react to it faster than to email. We built it for ourselves and stopped finding out about enquiries a day late.
What the enquiry itself should carry
- As few fields as possible. Name and phone; the manager can ask the rest.
- Source. Which page it came from, which campaign, which query.
- Language. On a multilingual site the manager needs to know which language to call in.
- Duplicate flag. One person clicking three times is one enquiry.
Response time beats everything else
Someone submits an enquiry while reading your site. Twenty minutes later they are reading a competitor’s. Two hours later they have already agreed terms with someone. So automate at least part of the first response: an instant “we have it, we will call within the hour” costs nothing and keeps the person in place.
A ten-minute self-check
- Submit an enquiry through every form on the site, including the one in the footer.
- Check all three destinations: CRM, messenger, email.
- Look at whether the record carries the source and the page.
- Measure how long it took the sales team to call.
- Repeat from a phone and from another language version.
Failing at least one step is normal for sites nobody has checked since launch. Run this monthly: things break quietly, after a plugin update or a changed mailbox password.
We will wire up the form, CRM and messenger so that no enquiry is lost, and show you exactly where they come from.