The enquiry that sat there all afternoon
Someone fills in the form on your website at eleven in the morning. It goes to info@ or a shared sales inbox. Three people can see it. Each assumes one of the others will pick it up. The one who usually does is out on a visit. By the time anyone replies it is the next morning, and the reply is a polite 'thanks for getting in touch, when would be good for a call?'
Meanwhile the person who enquired filled in two other forms on competitors' sites that same morning. One of them rang back within the hour.
Why the reply is slow
It is rarely because your team does not care. The causes are structural:
- Nobody owns the inbox, so every enquiry is everybody's job and therefore nobody's.
- Enquiries arrive mixed in with supplier emails, newsletters and spam, so the important ones are not obvious.
- The person who should reply needs information first, such as whether you cover that area, what the lead time is, or a rough price, and has to go and find it.
- There is no signal when an enquiry has gone unanswered, so the delay is invisible until the customer chases.
An automatic 'we have received your message' email does not fix any of these. It tells the customer nothing they did not already know.
What the delay costs
| What happens | What you lose |
|---|---|
| Competitor replies first | The enquiry, often before you knew it existed |
| Customer loses interest | Momentum while they were ready to act |
| Rushed reply to catch up | A generic answer that does not address their question |
| Ad spend on enquiries nobody answers | Money paid for leads you never really worked |
The last row is the one owners notice when they look at it. If you pay for Google Ads or Meta ads to generate enquiries and then leave them sitting, a large share of that spend is buying leads for your competitors.
How we speed up the first reply
- Capture: every web form, including WordPress, Webflow and landing page forms, posts straight into a single enquiry list and your CRM, not only into an inbox.
- Classify: a model reads the enquiry and records what they want, where they are, how urgent it sounds and whether it is spam, a supplier or a genuine prospect.
- Assign: routing rules pick a named owner based on service, area or rota, and notify them on their phone through Teams, Slack, SMS or WhatsApp via Twilio.
- Acknowledge usefully: the customer gets a prompt reply that answers the basics you can answer safely, such as whether you cover their area, what happens next and a link to book a call in someone's calendar.
- Draft the first proper reply: the owner opens the enquiry and finds a draft that addresses the customer's actual question, which they edit and send.
- Escalate: if nobody has touched the enquiry after a period you set, it moves to a second person or a manager.
Everything is visible on one screen: which enquiries are waiting, who owns them and how long they have been there.
What your team notices
Enquiries stop falling between people. Each has a name against it from the moment it arrives. The person replying starts from a draft that already reflects what the customer asked, so the first proper answer is more specific as well as faster. Managers can see, without asking around, whether anything has been left.
Customers notice too. A prompt reply that shows someone has read their message is one of the simplest ways to look more organised than the competition.
Over a few weeks you also start to see patterns you could not see before: which services generate the most enquiries, which times of day they arrive, and which enquiries tend to wait longest. That usually points at a practical fix, such as moving someone's lunch break or adding a second person to the rota on Mondays, that no amount of software would have suggested on its own.
Is this your inbox?
- Web enquiries go to a shared inbox that several people watch.
- Customers sometimes chase before you have replied.
- You are not sure how long enquiries wait on average.
- The first reply is usually a request for a call rather than an answer.
- You pay for ads that generate enquiries but have no view of how quickly they are answered.