When a potential customer gets in touch, they are often contacting more than one provider at the same time. The first genuinely useful reply tends to shape the rest of the conversation. Yet in many businesses, enquiries sit in shared inboxes, wait for someone to assign them, or get a reply only when a busy person finds a moment.
This playbook explains how to design an enquiry response system so that speed and consistency stop depending on who happens to be available.
What speed-to-lead means
Speed-to-lead is the time between an enquiry arriving and the first meaningful response. Meaningful is the key word. An automatic acknowledgement is helpful, but it is not a response. A meaningful response answers the question, qualifies the need or books the next step.
Why enquiries wait
- Enquiries arrive in several places: web forms, ad lead forms, chat, email, phone and messaging apps.
- Nobody is clearly responsible for each one.
- Details must be copied into the CRM before anyone can act.
- Priority depends on whoever reads the enquiry first.
- Out-of-hours enquiries have no process at all.
- Follow-up depends on memory.
The five parts of an enquiry response system
1. Capture
Connect every channel to one intake flow so each enquiry becomes a record automatically, with its source, campaign and consent attached. Deduplicate against existing contacts so returning customers are recognised.
2. Enrich and qualify
Add context automatically: company details for B2B, location or product interest for consumer businesses, order history for existing customers. Then assess fit and intent. Simple rules handle structured fields well; AI is useful for reading free-text messages and summarising what the person actually needs. Keep the criteria visible so your team can challenge them.
3. Route
Assign an owner immediately using clear rules: territory, product line, language, deal size, specialism, working hours or round-robin. Every enquiry should have exactly one owner within moments of arriving.
4. Respond
Trigger the first response automatically where it adds value, for example a booking link, relevant information or a question that moves things forward, and alert the owner at the same time. For high-value or sensitive enquiries, draft the response for a person to review rather than sending it automatically.
5. Follow up and measure
If there is no reply, follow up on a sensible schedule that stops as soon as the person responds or books. Escalate enquiries that have not been touched within your target time. Track everything so you can see where the system slows down.
How the design differs by business model
B2B: fewer, higher-value enquiries. Invest in enrichment, qualification and routing to the right specialist, and make meeting booking effortless.
B2C: higher volumes and faster decisions. Prioritise instant, helpful first responses, booking or application flows, reminders and clear escalation for complex cases.
D2C: many enquiries are pre-purchase product questions or order questions. AI-assisted answers grounded in your product and policy content, with a route to a person, usually matter most.
Metrics to track
- Median time to first meaningful response, overall and by source, owner and hour of day.
- Share of enquiries answered within your target time.
- Enquiries without an owner, and how long they stayed that way.
- Contact rate: the share of enquiries that became a real conversation.
- Conversion to the next stage, compared across response-time bands.
Measure a baseline before changing anything, so improvements are visible and credible.
Common mistakes
- Automating the acknowledgement and calling the job done.
- Sending every enquiry the same sequence regardless of intent.
- Routing rules that nobody maintains when the team changes.
- Follow-ups that keep sending after someone replies.
- No plan for evenings, weekends and holidays.
A 30-day starting plan
- Week 1: list every enquiry channel, measure current response times and map who does what.
- Week 2: connect capture to one system, add source tracking and set up routing with clear ownership.
- Week 3: build the first-response and follow-up flows, with human review where it matters.
- Week 4: launch, monitor daily, fix exceptions and report the before-and-after.
Enquiry response is one of the most common places we start. See our lead capture and routing and follow-up automation use cases, or book a strategy session to review your own process.