How to Build an Enquiry Response Process From Scratch

Most service businesses do not have an enquiry response process. They have a person — usually the owner — who handles enquiries as they come in, using judgment built up over years of running the business. This works, in the sense that enquiries get answered. It fails in every other sense: it does not scale, it does not run consistently when that person is busy or unavailable, and it cannot be handed off without a long, informal apprenticeship.

If you have ever said "I just need to get someone to handle enquiries the way I handle them" and found it nearly impossible to explain what that means, the problem is that the process lives entirely in your head. This article is about getting it out.

In short: A working enquiry response process has five components: a channel inventory, a triage rule, a first-response standard, a follow-up sequence, and an escalation trigger. None of them are complicated individually. What makes them powerful is writing them down so the process runs the same way regardless of who — or what — is handling the enquiry.

Step 1: Map your channels

Before designing any process, you need a complete picture of where enquiries arrive. Most service businesses have more channels than they realise:

• Contact form on the website
• Email inbox (possibly multiple — one for the website, one for direct contacts)
• Instagram or Facebook DMs
• WhatsApp (business or personal)
• Phone (missed calls, voicemail)
• Google Business messages
• Referrals (which may arrive by any of the above)

The starting point is a list of every channel that currently receives enquiries, ranked by volume. This list immediately reveals two things: channels that are not being monitored consistently (and are therefore leaking enquiries), and channels that generate the most volume (and should therefore be the highest priority for the process you are building).

For businesses running a managed workflow, this channel map becomes the scope document: which channels the workflow monitors and which require a different handling approach.

Step 2: Define your triage rule

Not every enquiry needs the same response. Before designing a response, you need a rule for deciding what kind of enquiry you have received.

A simple triage rule has three categories:

Standard: an enquiry that matches your defined service area, falls within your normal pricing and service scope, and needs a straightforward response. This is the majority of enquiries for most businesses.

Sensitive or complex: an enquiry involving a complaint, an unusual situation (probate, bereavement, a clinical issue that needs assessment), a very high-value opportunity, or anything outside the standard flow. These require a person, regardless of what the standard process is.

Out of scope: an enquiry for something you do not offer. The correct response is a brief, polite decline — not an attempt to fit the enquiry into something you do, and not silence.

Write these three categories down with examples specific to your business. "Sensitive or complex" should have a named list of triggers — what specifically moves an enquiry into that category. This is the escalation definition that allows any system (human or workflow) to know when to hand off rather than continue.

Step 3: Set a first-response standard

The first-response standard is the commitment your process makes about what happens when an enquiry arrives. It has three parts:

Timing: how quickly does the first response go out? For most service businesses, within the hour during business hours is the benchmark — above this, enquiry-to-meeting conversion rates drop meaningfully. Out of hours, the standard is different: a response that acknowledges the enquiry and sets an expectation ("we'll pick this up first thing tomorrow morning") is significantly better than silence.

Content: what does the first response contain? At minimum: an acknowledgement that the enquiry has been received, an answer to the question asked (or a request for the information needed to answer it), and a clear next step. Write the first-response template now, for each of your common enquiry types. It does not need to be long — three short paragraphs is usually enough.

Channel: does the response go back through the same channel the enquiry arrived on, or is there a preferred channel you route to? For businesses that want to move conversations from Instagram DM to email, the first response should include an explicit invitation to do that.

The first-response standard is the part of the process most businesses can improve immediately, without any additional technology — it just requires writing the templates.

Step 4: Build the follow-up sequence

An enquiry that receives a first response but does not convert to a meeting or sale is not necessarily lost — it is often just waiting. A follow-up sequence is the structured process for what happens after the first response, when there has been no reply.

A working sequence for most service businesses:

• Day 1: first response sent (this is not a follow-up — it is the initial response)
• Day 2-3: if no reply, brief follow-up that adds something: an answer to a question the enquirer may have, a specific time offer, a relevant piece of information
• Day 7: if still no reply, a second follow-up that is shorter and more specific: "just checking this didn't get lost in your inbox — would it help to have a quick call?"
• Day 14: closing message: "We'll leave this with you for now — feel free to get in touch whenever you're ready"

After day 14, the enquiry moves to a low-frequency nurture sequence (monthly, or triggered by a relevant event) rather than active follow-up.

Write this sequence out explicitly. For each message: when does it go? Who sends it (or what sends it)? What does it say? A sequence that is documented can be handed off; one that exists only as intention cannot.

Step 5: Define the escalation triggers

The escalation trigger is the list of specific situations that require a person to take over, regardless of what the process would normally do.

Common triggers for service businesses:

• Any expression of dissatisfaction or complaint
• A request that includes clinical, legal, or financial advice
• A mention of urgency or a specific deadline that changes the standard timeline
• An enquiry from an existing client with a specific account issue
• A very high-value opportunity that warrants a more personalised response

Write these out. Give them to anyone — or any system — handling the first response. The escalation trigger is what transforms a generic enquiry-handling process into one that applies appropriate judgment.

Putting it together

Once you have the five components documented, you have a process — not a brilliant one to start with, but one that is consistent, handable-off, and improvable. The first version of the process reveals its gaps within a few weeks: enquiries it does not know how to categorise, follow-up timing that does not fit certain sectors, escalation triggers that were too narrow or too broad.

The process improves through iteration, not through perfection at the start. What matters is that you have written it down.

For businesses that want this process to run without requiring someone to manage the inbox manually, a managed workflow builds on exactly this structure — the five components become the knowledge base and the workflow rules. What goes in a knowledge base covers what that structured document looks like in practice.

Frequently asked questions

How long does it take to build this process from scratch?

If you have the business knowledge (which you do, by definition), the documentation part takes two to four hours for most businesses. The investment is in structured thinking about things you currently do by instinct. After the initial session, an hour of review and refinement gets it to a version that can be handed off.

Do I need software to run this process?

No. The process can run with documented templates, a shared email inbox, and a simple spreadsheet tracking outstanding enquiries. Software helps with scale and consistency — a CRM or managed workflow removes the memory requirement and ensures follow-up happens on time — but the process itself does not depend on any particular tool.

What if my business is too variable for a standard process?

Every enquiry-response process handles variability through the triage rule and escalation triggers, not by eliminating standardisation. The standard process handles the majority of enquiries that are genuinely similar; the escalation path handles the ones that are genuinely different. Businesses that think they cannot standardise enquiry handling usually have not yet distinguished between the majority of enquiries (which are similar) and the minority that are genuinely unusual.

How do I know if the process is working?

Track three numbers: response time to first reply, enquiry-to-meeting conversion rate, and meeting-to-sale conversion rate. The first tells you whether the process is fast enough. The second tells you whether it is converting. The third tells you whether the quality of enquiries is right. Most businesses that build a documented process for the first time see their enquiry-to-meeting rate improve within the first month, simply because follow-up that was previously missed starts happening consistently.