What should happen in the first hour after an enquiry?
Acknowledge it, name an owner, and record where it came from. The first hour is a process, not a favour.
Within an hour, the person who enquired should know you received it, and someone named should own the next step. Anything slower is a coin toss against whoever else they contacted.
This is Convert, not a marketing extra. The advert, the page and the form have finished their job. The first hour is the process that decides whether that spend becomes a conversation.
The four things that should already have happened
- It arrived somewhere watched. Not a personal inbox that is closed on a job. A shared place, with a person whose job includes looking at it.
- The customer was told it arrived. Immediately. An automatic message is fine if it is honest about when a person will reply.
- A person is responsible. Named, not "the team". If they are out, the responsibility moves. It does not pause.
- The source was kept. Which page, which ad or which search, if you know it. An enquiry with no source cannot teach you what to do more of.
None of this requires a large system. It requires that those four things happen every time, including the one that arrives at 5pm.
What the customer should receive
A short confirmation: you have the enquiry, what happens next, and when. If you reply within one working day, say that. If the right person is on a site until Thursday, say that too. Uncertainty is what sends people to the next tab.
Do not send a newsletter. They asked for a conversation, not a subscription. A follow-up sequence can exist later for people who go quiet. The first message is a receipt and a promise, written like a person.
What the business should see
One list that shows the enquiry, when it arrived, who owns it, and whether anyone has replied. If the only copy is an email thread, you cannot manage it and you cannot see the leaks.
The useful fields are dull on purpose: name, what they want, how they found you, owner, status, next action, date. A CRM can hold that. So can a list, until the volume makes the list the bottleneck. The failure is having the fields in three places and the truth in none of them.
When you are ready for the system version, that is CRM and sales automation: the record created from the form, the owner notified, the chase-up not dependent on memory.
What to leave out
Leave out a twelve-step nurture sequence you will not maintain. Leave out a chatbot that collects the same details the form just collected and then emails them to the same unwatched inbox. Leave out scoring models until you have enough enquiries to score. At small volume, a same-day reply from someone who read the message beats a points system.
Also leave out blame. If enquiries die in the first hour, the process is missing, not the person's character. Fix the arrival, the acknowledgement, the owner and the record. Then see if you still have a speed problem. Often you do not.
The ways this fails in practice are in why enquiries disappear after the form.
Questions about this topic
Is an automatic reply enough?
It is enough to prove the enquiry arrived, and it is not enough to win the work. Send the automatic note immediately, then have a person reply on the same working day with something that shows the message was read. An auto-reply on its own, with no human behind it, is how inboxes get trusted and then ignored.
What should the first reply say?
That you have the details, the one or two questions you actually need, and a concrete next step: times for a call, or a note on what you would look at first. A long brochure attached to a short delay loses to a short, specific reply that arrives sooner.
Do we need a CRM to do this?
Not on day one. You need one list, an owner, and an acknowledgement. A CRM earns its place when retyping, missed follow-ups or not knowing the source are already costing you. Buying the software before the process exists gives you an empty database and the same inbox problem.
Losing enquiries after they arrive?
Convert is the work that makes sure enquiries are acknowledged, assigned and followed up, rather than sitting in a shared inbox.