How should a small team respond to new enquiries?
A useful enquiry response answers the customer’s immediate question and makes the next step clear. Give each request an owner, check missing information and promise a response time the team can actually meet. Measure unanswered requests, corrected promises and progress alongside speed so a fast acknowledgement does not conceal a stalled enquiry.
Keep these in mind
- Define response time from customer enquiry to a meaningful first reply.
- Use explicit ownership and backup cover.
- Treat historical lead-response research as context, not a guaranteed conversion formula.
Define a useful response
A useful first reply confirms what the customer needs and explains what will happen next. For a custom order, it might ask for dimensions and promise a quote by a specific time. An immediate receipt message can set expectations, but it has not answered the customer’s buying question.
A 2011 HBR article examined online lead response. It cannot establish a universal five-minute sales rule for WhatsApp businesses.
Avoid repeating a dramatic conversion percentage without checking the original study’s population, time period and outcome. A qualified conversation, a booking and a completed sale are different results.
Record the right start and finish
Use the time the enquiry arrived as the start if you want to measure the customer’s experience. Also record assignment time if a separate team routes requests. Otherwise, a long unassigned queue can vanish from the response metric.
Definitions vary by tool. HubSpot’s sales analytics documentation describes its lead-response measure from assignment to a qualifying interaction. Check your system’s definition before comparing its report with your promise to customers.
Separate working hours from elapsed hours. A Saturday evening enquiry answered Monday morning can be quick under a working-hours target and slow in the customer’s experience. Display both where that distinction matters.
An illustrative response agreement
A small design studio can agree different handling for new project enquiries, existing-client changes and urgent delivery issues. The following targets are examples for one team, not research benchmarks.
| Request | Accountable person | First useful action |
|---|---|---|
| New project enquiry | Sales owner, with named backup | Check fit and request missing brief details. |
| Existing-client change | Current project owner | Confirm effect on scope and timing. |
| Urgent delivery problem | Operations lead | Assess immediate risk and contact the customer. |
| Outside opening hours | Next opening shift | Review queue and give an honest reply time. |
Make the handoff hard to miss
Store the customer, request, arrival time, owner and next action together. If a colleague forwards an enquiry, they should not assume that forwarding transfers responsibility. The receiving person confirms ownership.
Keep an unanswered view that everyone covering the queue can see.
A manager can inspect the oldest open requests each day. Ask whether each request is waiting for the business, waiting for the customer or no longer active. An unresolved item should not become invisible merely because someone sent a message.
- Choose a meaningful first-reply definition and opening-hours policy.
- Assign one owner and a backup for each enquiry source.
- Check missing information before promising price or availability.
- Record the next action and a date even when the customer has not replied.
- Review the oldest unanswered enquiries and the reasons for delay.
Measure quality beside speed
Track enquiries receiving no useful response, replies requiring correction and suitable requests moving to a next step. A fast but wrong delivery promise can create more work than a slower accurate answer.
If volume is low, review individual cases rather than drawing conclusions from a percentage based on three enquiries. Keep spam, duplicate requests and unsuitable projects separate, with reasons visible.
Keep enquiry receipt, qualification and confirmation as separate steps. Name who checks the request and who sends the next reply. If the owner is absent, the backup needs the customer's original question and promised response time.
Review missed handoffs before adding another notification that everyone may learn to ignore.
Common questions
What is a useful first response to an enquiry?
Acknowledge the actual request, answer what can be answered accurately and name the next step. If details are missing, ask a focused question and give a realistic response expectation.
How should we measure enquiry response quality?
Track requests receiving no useful reply, corrections to promises and progress to an appropriate next step. Separate duplicates and unsuitable requests. A quick acknowledgement is not a resolved buying question.
Sources & further reading
Primary references for the facts and frameworks discussed. Worked examples and recommendations are Daltn’s own analysis.
- The Short Life of Online Sales Leads, Harvard Business Review ↗
Historical context for lead response; no five-minute or guaranteed uplift claim is made.
- Create sales reports in the sales analytics suite, HubSpot ↗
Documents the tool-specific lead response definition.
Published by the team building Daltn. Comparisons are first-party analysis, not independent reviews. Our editorial approach.