From enquiry to next action
A free practical white paper for small service businesses. Reduce repeated admin by making ownership, handovers and the next action clear.
Downloads
Illustration — fictional test data
Who is replying, and what happens next?
Demonstration — hypothetical enquiry handoff; not a customer result.
This annotated sequence shows illustrative record states for a two-person service business. It is not a screenshot of a deployed system or evidence of a real enquiry, reply or commercial result.
1. A website enquiry arrives
Example Studio — fictional · DEMO-ENQ-001
“Could you quote for refreshing our five-page website?”
Received: 9 November 2026, 09:15. Source: an existing website enquiry form.
What matters: keep the original request together in one supported customer system. An acknowledgement confirms receipt; it does not promise a quotation or delivery date.
2. One person owns the reply
Owner: Alex — fictional. Status: Awaiting action.
Next action: ask which five pages need updating and arrange a short scoping call. Due: 9 November 2026, 15:00.
The owner notification says: “New enquiry DEMO-ENQ-001 needs your reply.”
What matters: a named owner and dated action make responsibility clear while a colleague is busy.
3. A reminder prompts the next step
Example rule: at the agreed due time, remind Alex if the enquiry still awaits action.
The outstanding-enquiry view includes DEMO-ENQ-001. The reminder asks Alex to review it and complete or update the next action. After a real response, the owner records its outcome and the next agreed step.
What matters: the reminder prompts the owner. It does not send a sales follow-up or imply that the prospect has replied.
Suggested acknowledgement
“Thanks for your enquiry. We have received your request and will review it before getting back to you.”
Illustrative wording only: your business approves the actual message and response expectations.
How this relates to Enquiries & Follow-ups
The starter covers one standard form with up to ten fields, one supported connection to an existing customer system, one approved acknowledgement, one owner notification, one reminder rule and a simple view of enquiries awaiting action. Five agreed test scenarios, one revision and a 30-minute handover are included. Compatibility and reminder behaviour are agreed and tested for the chosen system.
See the Enquiries & Follow-ups scope and next step. Custom APIs, a new website, historic-data migration, SMS/WhatsApp and bulk campaigns need a separate scope.
Published for the November 2026 campaign. This example demonstrates a process, not measured savings or proof that a particular live intake route works.