Guide

How to automate client follow-ups without sounding like a robot

Follow-ups fail because they depend on someone remembering, not because they are hard to write. The fix is to let the system notice when one is due and draft it from the real conversation, while a person still decides what gets sent.

Updated · 4 min read

The follow-ups most small businesses miss

Follow-upWhat triggers itWhat it needs to say
Open quotesNo reply a few days after the quote was sentA reminder that answers the question they probably have
AppointmentsA visit or meeting tomorrowTime, address, what to prepare, how to reschedule
Overdue invoices7, 14 and 30 days past dueAmount, invoice number, how to pay, a firmer tone each time
Missing documentsA client hasn't sent what you asked forExactly which document, and the deadline it affects
After the jobWork completed or deliveredA check-in, and a review request if they have agreed to hear from you

Bookkeeping firms live on the "missing documents" row; contractors on open quotes and overdue invoices. The pattern is the same: the trigger already exists in a system, as a sent date, a due date or a status, and nobody is watching it.

Why "set and forget" sequences go wrong

Classic email sequences send the same text on a timer. They keep going after the client replied, they repeat a question that was already answered, and they chase an invoice the client is disputing. Clients notice, and it costs more goodwill than the follow-up earns.

The approach below avoids all three by watching the real state of each job and drafting from the real thread.

What to automate, what to assist, what to keep human

PartClassWhat it looks like
Noticing a follow-up is dueAutomateChecks the quote's sent date, the invoice's due date or the job status every day. Nobody has to remember.
Stopping when it no longer appliesAutomateA reply, a payment, a dispute flag or a cancelled job removes the follow-up before it is drafted.
Writing the messageAssistAI drafts from the actual thread and job details, in your tone, and answers what the client last asked.
SendingAssistDrafts wait in one list. A person reads, edits if needed, and approves the batch in a few minutes.
Negotiation, complaints, disputesHumanHanded to a person with the thread summarised. Never answered automatically.

Every message to a client waits for a named person's approval. That is what keeps follow-ups sounding like you. When the drafts are good, approving them is a quick daily routine rather than a task someone has to remember.

An example: quote follow-ups

  1. A quote is sent. The follow-up clock starts.
  2. On day 3 with no reply, a draft is written from the thread: if the client asked about start dates, the draft answers it.
  3. The office manager approves the day's drafts in one go.
  4. On day 10, a second, shorter draft. Large jobs are routed to the owner for a call instead.
  5. The moment the client replies or accepts, nothing more is drafted.

In our example workflow map, the office manager admits about half of quotes never get a follow-up. This is the step that fixes it, and the same pattern covers invoice reminders once invoices are in the system.

Rules to respect

In Canada, the Anti-Spam Legislation (CASL) governs commercial electronic messages. A message that only provides a quote the client asked for, or that facilitates, completes or confirms a transaction they agreed to, does not need their consent, but it must still identify you and include a way to unsubscribe. Messages such as review requests or promotions do need consent. Implied consent from a purchase lasts up to two years, and from an inquiry up to six months.

In the United States, the CAN-SPAM Act exempts transactional and relationship messages from most of its requirements, though they still cannot contain false or misleading routing information.

General information, not legal advice. Sources: CASL, section 6, the Government of Canada's CASL guidance on consent, and the FTC's CAN-SPAM guide.

How to start

  1. Pick one follow-up type, usually open quotes or overdue invoices.
  2. Count last month's: how many were due, and how many happened on time.
  3. Find where the trigger lives: the sent date in your quoting tool, the due date in your accounting system.
  4. Write down what a good follow-up says, from your best real examples. That becomes the brief for the drafts.

For choosing which workflow to automate first, see how to find what to automate, or let our AI automation assessment rank them for you.

Get started

Start with one workflow.

Book a free 20-minute build call. You'll leave with a clear view of what to automate first, and a proposal the same day.

Book a 20-min build call hello [at] intelligence33.com