How to Follow Up on Business Enquiries: A Practical System and Message Templates
Give every genuine enquiry a named owner, a clear next action and a due date. Make the first reply useful, follow what the customer actually said, and switch off old reminders the moment the conversation changes.
This works in a small CRM or in a carefully kept worksheet. It fixes a common problem: a request is sitting somewhere in email, but nobody can say who acts next.
The messages below are templates to adapt to a real request. They do not authorise messages to a purchased contact list, and they do not create permission for unrelated promotions.
Keep acknowledgement, qualification and follow-up separate
Give every message one clear purpose.
Acknowledgement confirms receipt and sets an honest expectation. It can reduce uncertainty, but it does not show that anyone has assessed the job.
Qualification asks for what you need to decide the next step. Keep it proportionate to the service and to how far the conversation has got.
Follow-up resolves something pending: a question that needs an answer, a quotation waiting for a decision or an agreed deadline coming up.
If a single automatic message tries to do all three while promoting other services, the customer cannot tell what you need from them.
Keep the minimum working record
| Field | A useful entry |
|---|---|
| Request received | Real date, time and channel |
| Customer or contact | Only the details needed to handle the request |
| Need | The stated job, in the customer's own context |
| Location | Enough area information for this stage |
| Owner | One person responsible for the next action |
| Stage | A defined status that reflects work actually done |
| Next action | A concrete task, such as confirm access or send a revised quote |
| Due date and time | The agreed time to act, with timezone |
| Waiting on | The customer, a colleague, a supplier or nobody |
| Permission and stop state | Channel expectations, objections and delivery problems |
Keep internal notes apart from messages the customer will see. A private assessment should never become the text of an automatic reply just because both fields sit next to the same contact.
If you need help designing the record itself, use the simple CRM workflow. This guide concentrates on the communication decisions around it.
Make the first human reply move things forward
A useful reply acknowledges the actual job, asks the smallest necessary question and says what happens after the answer.
For a fictional appliance repairer:
Thanks for the details about the washing machine. Please send the model number and your suburb so we can check it is within our repair scope. We will then explain the assessment arrangement and any call-out charge before booking.
It does not guess at a diagnosis, and it does not promise availability. It also explains why each detail is needed.
"Thanks, we'll be in touch" leaves both sides waiting. A long questionnaire creates work before you have even established the request is in your service area.
Promise only what the team can deliver
Decide what happens during staffed hours, outside them and during planned closures. An acknowledgement can state a review window only when someone is responsible for meeting it.
For example:
Your enquiry has been received. We review requests during our published office hours and will respond by the time shown in your confirmation. This message does not confirm a booking.
If the confirmation makes a promise, it must contain a real, achievable time. Never leave a placeholder in the live system, and do not let an automatic message promise "tomorrow" during a public holiday closure.
Use the customer's urgency to route the enquiry properly. If you cannot provide emergency response, say so plainly. An automatic acknowledgement should never imply that help is on the way.
Choose the cadence from the pending decision
No single sequence suits every trade, sales cycle or country. Start from what the customer expects and what you are waiting for.
| Situation | Sensible next action | Condition before another message |
|---|---|---|
| You owe an answer | Finish the answer, or explain what is blocking it | A real update, not another acknowledgement |
| The customer owes a basic detail | One short reminder after a reasonable interval | The detail is still needed and they have not replied |
| A quote has an agreed decision date | Follow up around that date | The quote is still valid and the request is still open |
| Work is scheduled | Send relevant service information or a reminder | The booking and recipient details are still right |
| The customer asks you to stop | Stop the affected messages | No automatic re-enrolment from an import or stage change |
| Delivery fails or the recipient is wrong | Review and fix the contact problem | A verified correction, not repeated blind sending |
An internal reminder and a message to the customer are different actions. You can remind the owner to check a quote without emailing the customer again.
A restrained example sequence
For a non-urgent, fictional furniture restoration enquiry, the workshop might adopt this operating policy:
- Acknowledge receipt and state the review window.
- Send a human reply asking for the photographs and approximate dimensions needed for assessment.
- If the customer does not reply, send one reminder after the interval you chose.
- If there is still no reply, send a brief closing note, or simply close the internal task, according to your agreed communication policy.
- Reopen the request if the customer returns later, after checking availability and whether any quote has expired.
The intervals are a business decision. Base them on how urgent the service is, what the customer expects, local working days, the recipient's timezone and the permission rules for that kind of message.
Do not present an arbitrary multi-message sequence as a research-proven conversion formula.
Templates for common pending actions
Missing information
We can continue the assessment once we have the item dimensions and collection area. If you still need help, reply with those details. If your plans have changed, let us know and we will close the request.
Ask only for what you need. A town is enough to check coverage, so do not ask for a full home address.
A quotation awaiting a decision
Following up on the quotation for the work we discussed. Is there anything in the scope or timing you would like clarified? The quotation's stated validity and availability conditions still apply, and we can confirm the next step when you are ready.
Do not imply a slot is being held unless it is. If the quote has expired, say what needs to be checked again.
A genuine internal delay
We are still checking the material availability for your request. The next update is due on the agreed date. We have not confirmed the work, and we are not treating this as an instruction to proceed.
Change the last sentence if the real situation is different. Messages must match the true state of the job.
Closing a quiet request
We have not received the information we need to continue, so we are closing this enquiry for now. You are welcome to reply if you want to revisit it, and we will check current scope, pricing and availability then.
Closing should clear your work queue without pretending a sale was won or that the customer rejected the service.
Stop old automation when new information arrives
A reply can change the next action at once. The customer may have sent the missing detail, chosen another supplier, asked for a later date or opted out.
Before a scheduled message goes out, the system or the responsible person should check that:
- The request is still open.
- No new reply has made the message obsolete.
- The recipient and channel are still appropriate.
- The quote, date and any facts it mentions are still valid.
- The message has not already been sent, and its delivery outcome is not uncertain.
A queued reminder should never keep saying "we haven't heard from you" after a reply. Treat an uncertain email delivery as something to reconcile. A missing notification is not a good enough reason to send the same message again.
These checks matter most when several staff members can reply from different inboxes.
Keep service messages and marketing permission apart
A customer who asks for a quotation gives you a specific reason to reply. It does not give you permission to send every future offer, or to share their details with other suppliers.
The purpose and content of a later message matter. A quote chaser, or an administrative message with a promotion added, may be treated differently from a purely administrative one under the applicable rules. For the UK, the ICO explains that adding promotion to an otherwise administrative message can turn it into direct marketing. That UK distinction is not a complete worldwide rule. ICO guidance
Before you automate a sequence, establish the relevant jurisdiction for the business and the recipient, the channel and the basis for permission. Make objections easy to act on, and keep the stop state through imports, duplicate merges and staff changes.
Review the queue at the end of each working day
Look for unanswered genuine requests, overdue tasks, leads with no next action and messages awaiting a delivery decision. Each should have a named person and an outcome: act, reschedule with a reason or close deliberately.
Measure response time with a defined start and stop. Separate automatic acknowledgements from the first useful human reply. Record how business hours were handled so a weekend enquiry does not look the same as one left unanswered during a staffed shift.
The result is a dependable service process. Customers know what happens next, staff can see what they owe, and automation supports a live conversation instead of carrying on after it has moved on.