Lead follow-up automation: what to connect, in what order

To automate lead follow-up, connect one path in a fixed order. Every enquiry lands in one place. A named person is told at once. The enquirer gets a first reply you've written. A reminder goes out if nobody acts. Get that working for one source before you add the next.

Our business automation work starts the same way: one automation first, and then the next one becomes obvious. Here are the five steps.

1. One place for every enquiryA sheet or a CRM, with the source on every row.
2. Tell a named personOne person per source, on a channel they actually read.
3. A first reply you've writtenA short acknowledgement that says what happens next.
4. A reminder when nobody actsIf a row is still new after the time you set, the named person is nudged.
5. A recordWho replied, when, and what came of it.

Where enquiries get lost today

A form emails a shared inbox nobody owns. A WhatsApp message sits on one person's phone while they travel. A call is noted on paper, to go into a sheet "later". Write down every place an enquiry can arrive, and answer three questions for each:

1. Who sees it first?
2. Where does it go next, and who moves it there?
3. How long does it usually wait for a first reply?

The fix is usually not a new tool. It is deciding where enquiries land and who is responsible, then letting the tools you already have do the copying.

Step 1: one place for every enquiry

Choose one list that holds every enquiry: a shared sheet or a CRM (customer relationship management tool, software for tracking each contact and what happened). Either works, as long as there is only one list and people agree it is the list.

Give each row the same few columns:

• Received: the date and time.
• Source: form, WhatsApp, email or phone.
• Contact: name, plus a phone number or email.
• Asked for: what they wrote, in their words.
• Owner: the named person for this row.
• Status: New, Replied, Waiting on them, or Closed.

A form can post straight into the list and email can be forwarded into it; whoever takes a phone call adds the row. Nothing counts as an enquiry until it is on the list. If the sheet starts holding more than enquiries, see when a spreadsheet is enough.

Step 2: tell a named person

A message to "the team" is a message to nobody. Name one person for each source, and a backup for the days they are away. Send the alert where that person will see it: a WhatsApp message, an email or a Slack channel.

The alert should say enough to act on and link to the row for the rest. Don't copy phone numbers and full messages into channels many people read, such as a group chat; a first name, the request and the link are often enough. When the person has replied, they change the status, which stops any reminder.

Step 3: a first reply you've written

The first reply is an acknowledgement, not a sales sequence: one message, written by you, sent once, saying you got the message and what happens next. Promise only what you can keep. If you say "someone will reply by tomorrow evening", set the reminder in step 4 to protect exactly that.

Step 4: a reminder when nobody acts

Automation earns its place here. If a row is still New after the time you set, the named person is reminded; a little later, the backup is told as well. The rule can be as simple as "still New by the end of the next working day". The reminder goes to your people, not the enquirer, and stops the moment the status changes.

Step 5: a record of what happened

Keep the history on the same row: when the enquiry arrived, when the first reply went out, who answered, and a short note on how it ended. A weekly glance then shows what is still New, which source is slowest and where enquiries stall.

Where a person stays in the loop

Automation moves the enquiry, tells people and sends the acknowledgement. A person answers anything that needs judgement: a quote, a question about availability, a complaint, a request you haven't seen before. Decide the rule in advance, for example: anything outside your standard types gets no automatic reply beyond the acknowledgement.

Before you connect anything

Three questions are easier to settle before the connections exist than after.

Use your own test details, never a customer's, and repeat the tests whenever a connection changes.

WhatsApp notifications and follow-ups: the official route only

WhatsApp can be part of the path, for notifications and follow-ups, through WhatsApp's own business tools. We don't run marketing broadcasts, and we don't use workarounds. Meta, which runs WhatsApp, sets three rules that matter here:

• A customer's message opens a window. When someone messages or calls your business, a 24-hour timer called a customer service window starts. While it is open you can send ordinary messages. When it closes, only pre-approved template messages can be sent.
• Templates need opt-in. Meta's documentation says you must obtain user opt-in before sending message templates.
• People must have agreed to hear from you. Under the WhatsApp Business Messaging Policy, you may contact someone only if they gave you their number or WhatsApp username and opted in to receive messages.

In practice, a first reply to someone who just messaged you fits inside the window. A follow-up days later needs an approved template and the person's agreement. Your own staff are recipients too, and need to opt in. An alert to someone who hasn't messaged or called the business in the last 24 hours goes out as an approved template. Check Meta's documentation again when you set this up, because platform rules change.

Next step: list your sources and who sees each one first. Tell us which source loses the most enquiries, and we'll say what we would connect first, and what we would leave alone.

Reviewed and edited by Online Scope before publishing. Something out of date? Tell us at info@onlinescope.in. How we write the Blog.