How to automate client follow-up

Why follow-up dies

Ask any operator whether follow-up matters and you get an emphatic yes. Open the same operator's sent folder and you find inquiries that never got a second touch. The gap is not effort or belief. It is structural, and it has three parts:

• The system is a memory. The follow-up list lives in someone's head, reconstructed at red lights and between drops. Heads are terrible databases, and they fail hardest during the exact weeks when inquiries spike.
• The guilt spiral. After a week of silence, following up feels awkward. After two, it feels like an apology. So the oldest leads, the ones most in need of a nudge, are the least likely to get one.
• Nobody owns it. When follow-up belongs to whoever notices, it belongs to no one. Every unanswered quote has a moment where each person assumed someone else had already replied.

A real fix has to attack all three at once: a trigger that does not rely on memory, a prompt that arrives before the guilt does, and a named owner for every send.

Build the cadence on trigger events, not calendar blasts

A calendar blast asks what day it is. A trigger asks what just happened, or pointedly did not happen. That difference is why one reads as spam and the other reads as attentiveness.

The most useful concept here is quiet days: days with no reply and no activity from the client. A reply resets the clock. Counting quiet days instead of calendar days means you never nudge somebody who wrote back yesterday.

Two or three triggers run reliably beat ten triggers run occasionally. Start with the first row. It is where the money is.

Write follow-ups that get replies

The best follow-up you will ever send is three sentences long. Everything past that is you talking the client out of replying.

• Short. Three sentences is the ceiling. A follow-up is a tap on the shoulder, not a second pitch.
• Specific. Name their event and date. 'Just checking in' is noise; 'the quote for the October 10 reception' is a message about their actual thing.
• One ask. End with a single question they can answer from a phone in a checkout line. Two questions get zero answers.
• No apology, no manufactured urgency. Never open with sorry to bother you, and never invent scarcity. If real interest exists for their date, say so once, plainly, and leave it.

A worked example, four quiet days after a wedding quote: 'Hi Dana, the quote for the October 10 reception is still open on my end. Want me to hold that date, or adjust the package first? Happy to change the hours either way.' Three sentences, one question, easy to answer from a phone.

Automate the drafting, not the sending

Full automation is where follow-up goes to embarrass you. A system that sends on its own will eventually nudge the client who declined by phone yesterday, chase a deposit that arrived as a check this morning, or cheerfully follow up in the middle of a complaint thread. The context lives with you, not with the software.

The model worth trusting splits the job: software drafts, a human approves. The system watches the triggers, counts the quiet days, and writes the message from your template with the client's details filled in. Then it stops. The draft waits in a queue until a person reads it, edits or kills it, and approves the send. Reviewing a morning's drafts takes a couple of minutes; writing them from scratch is the task that has been on your list since Tuesday.

The split fixes each failure mode directly. Trigger logic never forgets and never feels awkward, which kills the memory problem and the guilt spiral. The approval queue has a name on it, which kills the ownership problem. And because a person touches every message, nothing tone-deaf leaves the building under your name.

• Keep sends inside business hours. A follow-up stamped 2:14 a.m. reads as automated because it is.
• Stop the sequence the instant the client replies through any channel.
• Cap it. Two or three touches, then convert to a phone-call task for a human. There is no polite eleventh email.
• Honor opt-outs per client, permanently.

A starter cadence you can run this week

How OpsVue handles this

OpsVue's automation model is the one this guide recommends, because we think it is the only honest one. Workflows carry outcome paths like 'no response after N quiet days,' 'payment overdue,' and 'declined,' and reminder, follow-up, and thank-you steps fire on real anchors: when the document went out, when the client viewed their link, when the event date passed.

When a trigger fires, OpsVue stages a draft, never a send. Client-facing messages are built from your Email Studio templates with the job's details filled in, and they land in the Approval inbox where a person reviews and approves each one. Nothing auto-sends to a client. That is a design position, not a missing feature.

The supporting rails match the rules above: send windows and quiet hours in your workspace timezone, per-client automation opt-outs, and a suppression list on outbound email. Triggers read real facts from the work record, where the quote and its versions, portal views, payments, tasks, and email history live together, so an acceptance or a reply changes the path instead of colliding with it.