Sample: Customer Follow-Up Reminder Run for a Studio
This worked example shows one customer follow-up reminder run for a design studio. It covers the open threads that went in, the schedule that came back, and the judgement a human reviewer applied so the studio followed up without nagging the wrong people.
What was sent in
The studio shared fifteen open customer threads:
- Several quotes sent but not yet answered.
- Two clients who had asked to be contacted next month.
- One client who had already paid.
- One thread that ended on a complaint.
The ask was simple to say and easy to get wrong: follow up politely, do not nag, and do not message the people who should be left alone.
What came back
The service returned a follow-up schedule, one row per thread, with:
- A suggested send date spaced sensibly, not all at once.
- A short draft for each follow-up, written to match a polite tone.
- A cap of one reminder per thread unless the client replies.
The drafts stayed as drafts. Nothing was queued to send until the studio approved it.
What the reviewer caught
This is a service where the wrong send is worse than a missed one, so the review pass is about exclusions as much as drafts:
- The already-paid client was removed from the run entirely.
- The complaint thread was pulled out for a person to handle, not a templated nudge.
- The two clients who asked for next month were scheduled for next month, not chased now.
Every excluded thread was listed with its reason, so nothing was dropped silently.
The deliverable
The studio approved a tidy schedule: polite drafts for the threads that genuinely needed a nudge, sensible dates, and a clear note of who was left alone and why. No awkward “we’ve already paid?” replies, no follow-up landing on a complaint.
Follow-up runs vary in volume and cadence, and the exclusion rules are agreed at intake.