How to automate inbound enquiry follow up without losing track of the conversation

Write down the process that happens today

Take a small, representative set of recent enquiries and follow each one from arrival to its current outcome. Include straightforward requests, poor fit enquiries, duplicates and a request that required an unusual decision. Use authorised access and remove unnecessary personal information from any material shared for scoping.

Record when the enquiry arrived, when someone first worked on it, who owned it, what information was missing and where the next step was stored. Separate hands on work from waiting. Ten minutes spent assembling a reply and two days spent waiting for an owner are different problems.

If nobody owns a request, establish that responsibility before automating it. Otherwise the workflow can produce a draft that sits in another unattended queue.

Define the minimum record

Keep the record small enough to maintain and complete enough to act on. A useful starting set is:

• The source and arrival time
• A link or reference to the original conversation
• The request and information still needed
• The assigned owner
• The next action and due date
• Review status and the most recent contact
• The final outcome, when known

Choose one authoritative place for the next action. Avoid making the inbox, a spreadsheet and a CRM compete for the same status. If multiple tools need a record, define which one is authoritative and how discrepancies are resolved.

Start with a draft that helps the buyer move forward

A useful first reply acknowledges the request and asks the minimum questions needed for the next step. Give the drafting process approved service descriptions, qualification criteria and examples of appropriate tone.

For example, a consultancy website enquiry requesting a price and six week completion date needs scope information before a promise. A suitable draft asks for the existing website, required changes and content readiness. It leaves the price and timing decision to the sales owner.

The draft should make missing information visible. Ask the reviewer to check factual accuracy, relevance and whether the proposed next step fits the conversation. Track substantial rewrites so recurring problems can be corrected in the workflow.

Make the review boundary explicit

For an initial pilot, a straightforward boundary is to prepare customer messages for approval. Agree who reviews them and how quickly that person can usually respond. A backup owner is helpful when the primary owner is unavailable.

Decide which requests must always be escalated: discounts, unusual contract terms, delivery promises, complaints, sensitive information and uncertainty about the right customer or conversation. Keep the approval record alongside the action it authorised.

External sending should follow the agreed permissions. Adding automatic sending later is a separate scope decision with its own tests and controls.

Test the cases that break a tidy demo

Before using the workflow on live enquiries, test more than the happy path. At a minimum, cover these cases:

• The same enquiry arrives twice through different sources
• The prospect replies while a follow up is awaiting approval
• The prospect asks not to be contacted again
• A forwarded email contains quoted material from another conversation
• The named owner is away or the approval is overdue
• The record update fails after a draft has been prepared
• The enquiry asks for a price or promise outside approved information

Agree the expected result for each case. For example, a new reply should trigger a fresh review of an unsent follow up. An unsuccessful record update should produce a visible exception rather than a false success message. Repeating a failed step should not create duplicate records or duplicate messages.

Choose measures that expose the real bottleneck

Measure the time needed to organise and draft each eligible enquiry, the share of drafts needing substantial revision, the share with an owner and due next action, and the number of overdue or failed steps. Keep waiting time separate from preparation time.

Use a defined pilot period and compare similar enquiry types with the baseline. If the volume is low, say so. A handful of enquiries can reveal implementation problems but cannot establish a dependable change in sales conversion.

Know what the pilot should produce

By the end, you should have a working scope, an exception log, a record of approvals and a short account of the value observed. The decision is whether to improve the same workflow, expand it or stop because the cost and effort are not justified.

Being AI starts with inbound enquiry triage and first follow up as a scoped managed workflow. To explore it, share your enquiry sources, current tools and the step that most often gets stuck.