How to automate enquiry follow-up and keep it personal

Give every enquiry an owner and a next step

A prospect explains what they need. Someone opens the email, forwards it and assumes a colleague will reply. Days later, the team cannot tell whether the conversation moved forward. To automate enquiry follow-up well, fix that handoff first.

Start with one channel, such as your website enquiry form. Create a shared record containing the original request, assigned owner, current status, last contact and next action. Keep the customer's wording available so the next person does not ask them to explain everything again.

An owner is a person, not a shared inbox. Agree who covers leave and who checks unassigned enquiries. Define a response target your team can actually support, taking account of working hours. A receipt acknowledgement and a considered answer are different events; record them separately.

Use a small set of clear statuses: new, with owner, waiting for customer, next step agreed and closed. Each open enquiry should have a next action and a date. A record without either belongs in an exception queue someone checks.

Build a short sequence with a clear finish

The following is a hypothetical pilot for incoming service enquiries, not an Amtec client result or a recommended schedule for every business. The customer has asked for help, the team has checked what communication is appropriate, and an owner approves the substantive response. Agree your intervals before switching anything on.

The sequence is conditional. It must read the current record before each action, rather than sending the next message simply because time has passed. A person who has already booked a conversation should never receive a reminder asking whether they are interested.

Write replies that help someone move forward

A useful follow-up refers to the actual request and makes the next step easier. Ask for one missing detail, explain a choice or answer an unresolved question. Repeating “just checking in” adds a message without adding help.

Use the template below as a starting point. Replace every bracket and check the interpretation against the original enquiry. If AI prepares the draft, keep unsupported prices, availability, delivery dates and commitments out of it. The owner should correct uncertainty before sending.

Use a monitored reply address and include your business contact details. Commercial messages also need the required unsubscribe facility. Do not imply that a named person has reviewed a message unless they have.

Put stop rules ahead of send rules

Test the stop rules before the happy path. A pause must cancel queued messages as well as change a label on the record. Make the current conversation visible to both the person handling the enquiry and the system preparing the next action.

For Australian businesses, permission belongs in the workflow. ACMA warns that an email enquiry does not automatically justify adding someone to a marketing list. Its marketing guidance requires consent, sender identification and a working unsubscribe process, with unsubscribe requests actioned within five working days. Classify the messages you intend to send and check the guidance before enabling them.

• Reply received: pause all enquiry nudges and hand back to the owner, including replies that need interpretation.
• Meeting booked, quote accepted or job started: cancel the enquiry sequence and hand over to the next workflow.
• Declined, withdrawn or unsubscribe received: stop the relevant messages and preserve the instruction across connected systems.
• Duplicate request or manual contact: reconcile the record before another message is prepared. Log calls and direct emails too.
• Failed delivery or uncertain send result: flag it for review instead of blindly repeating the message.
• Owner absent or connection unavailable: route to the agreed backup, with a visible way to pause the workflow and continue manually.

Measure useful conversations and recovered time

Run the first pilot with human approval and compare similar enquiries before and after. Define an eligible enquiry so duplicates, spam and unrelated requests do not distort the comparison. Keep source and request type visible: a different mix of prospects can change outcomes without any improvement in follow-up.

Review the measures below with the people doing the work. More replies are useful only if they help the customer and business reach a sensible next step. Include time spent checking drafts, fixing records and handling exceptions.