Workflow automation
How do you automate follow-up after a website enquiry?
Our guide to workflows that pay off first gives first response a single line. This is the long version: the first reply, the channel, booking a time, when to stop, what POPIA expects, and a test you can run on yourself.
What should an automatic reply to a website enquiry say?
It should show you understood the enquiry, and say what happens next. "Thanks for your enquiry, we'll be in touch" does neither.
Speed to lead, the gap between the form and your first useful reply, is why you automate this at all. But speed only helps if the reply says something. Repeat what they asked about, answer the question they'll ask next, and ask for the one thing you need before you can quote or book.
Say you install security gates in Bloemfontein, and a form comes in at 21:40 on a Sunday from someone in Langenhoven Park. The reply that goes out a minute later might read:
Hi Thandi, thanks for asking about security gates for your home in Langenhoven Park. We do work in your area. So we can give you a rough price, could you reply with photos of the doors you want covered, and their rough widths? Nadia from our office will phone you on Monday morning to book a measuring visit.
Nobody on your side had to be awake to send it. Only promise a time you can keep, though: a reply that says Monday morning, followed by a call on Wednesday, does more harm than no promise.
Should the follow-up go by email, SMS or WhatsApp?
Use the channel the person chose, and ask on the form if you plan to use anything other than email.
Email is the default. Send it from your business account on your own domain, not the website's built-in mailer, and test that it reaches the inbox rather than spam. SMS reaches any cellphone, data or no data, and suits a short nudge with a time or a link. Put your business name first.
WhatsApp feels the most personal, and Meta adds its own rules on top of the law. Meta requires opt-in before a business messages someone on WhatsApp, and the opt-in must name your business and make clear the person is agreeing to hear from you. A website is one of the opt-in methods Meta lists, so a tick box on your form can do it.
Sending a form also doesn't open WhatsApp's customer service window, which starts when the customer messages you. Until then you can only send templates Meta has approved in advance, so every WhatsApp message in your sequence has to be written and approved before go-live. The simpler route is a "Chat to us on WhatsApp" button on the thank-you page, so the customer opens the window by messaging you. Our page on WhatsApp AI chatbots explains how the platform works.
A missed call is a different problem, covered in how to stop missing customer calls.
How do you get from enquiry to a booked time without phone tag?
Offer real times from your live calendar in the first or second message, and let the customer pick. Every round of "does Tuesday suit you?" is another chance for the enquiry to go cold.
The workflow needs access to your calendar and a rule for each kind of slot. Anyone can take a short call, but a measuring visit needs travel time and the right person.
Qualify lightly first, asking only what changes the next step: where the job is, what kind of job it is, and how soon they need it. The answers decide whose diary the booking goes into, or show that the honest reply is "we don't do that kind of work".
Once a time is chosen, the workflow writes it into the calendar, confirms the details and sends a reminder the day before. Quote requests work the same way, with a draft for a person to approve. Our page on automating quotes, invoices and bookings covers both.
How many follow-ups should you send, and when should they stop?
Send a few over about a week, then close the loop. When the sequence stops matters more than its length. If you follow up leads automatically, make the sequence end the moment the person replies, books, says no or asks you to stop.
A sensible starting pattern for a service business:
- The first reply, straight away.
- A short nudge the next working day if nothing has come back, with the booking link again.
- One more a few days later that adds something useful, such as the answer to a question customers often ask.
- A last message that closes the loop: you'll leave it there, and they can reply whenever they're ready.
Build the stop rules into the workflow, because nobody remembers to cancel a sequence by hand. A WhatsApp reply has to stop the emails, and whoever takes a phone call needs a quick way to mark the enquiry as handled. That's far easier when every channel writes to one customer record in your CRM.
This is different from a bulk SMS blast. A sequence goes to one person about one enquiry, while an offer sent to every old enquiry on your list is a marketing campaign with different rules.
Is a ready-made template enough, or do you need a custom workflow?
Use a ready-made template if your form builder or CRM has one and all you need is the first reply. It's quick, and it beats silence. (These are workflow templates, not WhatsApp's message templates.)
Templates strain once the follow-up has to make decisions: different questions for different services, a reply on one channel that must stop the others, a calendar to read, a record to update. Then you need a workflow built around your process.
Doing it by hand works while enquiries are few and someone is always at the desk. It fails quietly over weekends and whenever that person is on leave.
What does POPIA say about automated follow-up messages?
POPIA doesn't ban automated follow-up, but its direct marketing rules decide how far a sequence can go.
Under section 69 of POPIA, direct marketing by any form of electronic communication, SMS and email included, is prohibited unless the person has consented. The exception is an existing customer whose details you got in a sale. You may market your own similar products or services to them, provided they could object when you took their details and can object in every message. Every direct marketing message must identify the sender and give contact details for asking that the messages stop. The Information Regulator's guidance note on direct marketing treats phone calls as electronic communication too.
Answering the enquiry is one thing. Promoting your other services, or sending offers to people who enquired months ago, is what section 69 regulates. In practice:
- Keep the sequence about the enquiry the person made.
- Use a separate, unticked box for anything else you'd like to send later, worded to say what you'll send and on which channel. The Act defines consent as a voluntary, specific and informed expression of will, and the Regulator's guidance says silence cannot mean consent.
- Name your business in every message and offer an easy way to stop, such as replying STOP.
- Keep a list of everyone who has opted out or objected, and check it before every send. The guidance note says you must keep that kind of database.
Where a particular message falls is a question for your information officer or an attorney. Our POPIA guide for WhatsApp chatbots covers consent on WhatsApp in more detail.
What tends to go wrong, and how do you test it?
Most failures are dull. Phone numbers arrive with and without the +27, so clean them into one format before anything sends. People submit twice, or submit and then phone. Match them on email or cellphone number and keep one sequence per person.
Bots fill in forms too, and a spam check in front of the workflow stops you politely chasing people who don't exist. Hold the nudges for business hours as well. A reminder at 02:00 looks careless.
Then test it the way a customer would. Fill in your own form on your phone after hours, once with a typo in the email address. See what arrives, what doesn't, and who on your team finds out.
How does Cognexa set up follow-up after a website enquiry?
Follow-up is part of the admin our workflow automation takes on, along with the quote, the booking and the CRM record nobody updated. In practice that usually means wiring the website enquiry form, WhatsApp, the phone line and the shared inbox into the CRM you already pay for. Every message then logs against the right record, where the stop rules can see it. We build against documented interfaces, never screen-scraping, and every step is logged.
On WhatsApp we use the official WhatsApp Business Platform, with approved message templates set up as part of the build. The flows are designed around POPIA's principles of consent and minimality: customers opt in before marketing messages, and every conversation offers an opt-out. A person signs off what the automation does, and anything that needs judgement reaches your team with the full context. Where a call is the better follow-up, our AI voice agents handle outbound follow-up as well as inbound calls.
And if you get few enquiries and each one needs real judgement, we'll tell you that automation probably isn't worth paying for.
Where should you start this week?
Start with the words, not the software.
- Find out what happens now: how long a form waits before anyone sees it, and what the customer receives meanwhile.
- Write the first reply you wish had gone out, including the one question you always end up asking.
- Decide your stop rules, and who takes over when an enquiry needs a person.
Those notes are a brief anyone could build from. Once this workflow is running, pick the next from our list of small-business workflows worth automating.