An enquiry follow-up process should help a person complete the conversation they started. It needs more than a series of reminders. Your team must know what the person asked, what information is missing, who is handling the next step and when further contact is no longer appropriate. Start with a small shared workflow before adding automation.
Capture the request and assign one owner
Record the date, contact route, requested service and the question that needs answering. Use a reference the team can find later, and keep private customer information inside the approved customer system. Assign one person to own the next action so two teammates do not send overlapping replies or assume someone else is responding.
Separate a new service enquiry from existing-customer support, supplier contact or an unrelated message. These conversations need different handling. If the request belongs elsewhere, record the handoff and confirm the receiving person has it. An automatic acknowledgment can confirm receipt, but it should not imply that someone has already assessed the request.
Make the first response useful
Answer the question you can answer, then ask only for the missing information needed to progress. Explain why the detail matters when it is not obvious. For a print estimate, size and quantity may be necessary; a long general questionnaire may not be. Keep the request easy to understand and avoid asking again for information already supplied.
State what happens after the person replies and give a response expectation your team can maintain. Do not promise a price, booking or result before the relevant assessment. If you need another colleague’s input, record that internal action instead of repeatedly telling the customer you are still checking without a clear owner.
Use statuses that show the next decision
A simple set might be New, Assigned, Waiting on us, Waiting on customer, Next step agreed and Closed. Add the next action, due date and owner to each open item. ‘Follow up’ alone is too vague; ‘ask whether the revised quantity is confirmed’ tells the next teammate what the conversation needs.
Review overdue items in the shared record rather than relying on individual inbox memory. When responsibility changes, update the owner and summarize what has already been agreed. Preserve the conversation history so a new person does not restart the sale or contradict the previous response.
Illustrative enquiry record
A fictional print shop receives a request for flyers without a quantity. Owner: the estimating teammate. Status: Waiting on customer. Next action: request quantity and required date. After the customer supplies both, the item moves to Waiting on us for assessment. If the customer says the project is canceled, close it and cancel any pending reminder.
Define follow-up timing and stop conditions
Agree on a modest follow-up plan suited to the conversation and the customer’s stated timing. The purpose of a reminder should be to help with a specific unresolved step, not to send an indefinite sequence of increasingly urgent messages. Record how many reminders are appropriate for this request and who decides whether to close it.
Stop or change the sequence when the person replies, declines, asks for no further contact, completes the next step or moves into a different conversation. Check the latest record before sending. Respect recorded contact preferences and suppression rules, and keep enquiry handling distinct from permission for unrelated marketing. Silence should not be interpreted as renewed interest.
Automate only after the manual workflow is clear
Test any automation with controlled cases: a new request, a reply before the reminder, a closed item, an owner change and a request for no further contact. Verify both the send condition and the cancellation condition. A timer that sends correctly but ignores a completed conversation can create an awkward customer experience.
Review a sample of closed enquiries for practical problems: duplicate replies, missing information, long internal waits or reminders sent after closure. Use these findings to adjust ownership and handoffs. Keep outcome labels accurate; an estimate sent is not a booking, and a booking is not necessarily completed or paid work.
- One owner and a clear next action.
- Customer information stays in the approved system.
- Replies answer the actual request.
- Reminders have a purpose and a limit.
- Reply, decline and completion events stop inappropriate follow-up.
Your next step
Map one enquiry from arrival to closure using the six statuses above. Add the owner, next action and stop condition before deciding which parts are safe to automate.
