By The Tool Trial Editorial Team
The third follow-up is the one people get wrong. The first is easy and the second is fine, and then the silence starts to feel personal — so the email gets longer, or pushier, or apologizes for existing.
What follows is twelve short emails for the moments a service business faces, from the first acknowledgment to the message you send when someone asks you to stop. Each is a draft: blanks you fill from what you know, checks to run first, and a stop condition.
Every one is sent by a person, by hand, after a person reads it. Nothing here automates, schedules, or sends anything.
This is practical editorial guidance, not legal advice, and it does not establish that any message complies with CAN-SPAM or any other rule.
How to use this library
Pick by situation, not by sequence. They are numbered for reference, not as a campaign.
Fill every blank from something you can point to. If you cannot, delete the sentence rather than guess. A sentence that does not fit is a claim you did not mean to make.
Timing is yours. Decide your own gap between messages and your own limit, write it down, and apply it consistently. No timing here is presented as optimal, because nothing has been measured.
Every template offers a way out. A line that lets someone end the conversation is what separates following up from pestering.
What these are, and what they are not
Drafts, never finished emails. A person fills the blanks, reads the result, and sends it.
Replies to people who contacted you. None is for a purchased list, a scraped address, or a cold campaign, and reusing an old inquiry as a marketing list is outside what this supports.
Email only. No SMS, messaging apps, or call scripts — those carry consent questions this article does not resolve.
No tracking. No pixels, no open tracking, no shortened links, no automation.
Untested. No reply rate, no booking rate, no improvement of any kind is claimed.
The twelve templates
The tracker states below come from the Simple Lead Follow-Up Tracker for Small Businesses, a planned resource not yet published; any table using them works. Deciding which email to send belongs to the follow-up workflow, also planned and unpublished. This library supplies the wording only.
T-01 — New inquiry acknowledgment
Purpose: confirm the inquiry arrived and that a person has it.
Use only when: a genuine inquiry came in and you have not replied yet.
Do not use when: you already replied, or the request is out of scope.
Suggested subject: Your [Service requested] inquiry
Placeholders required: [First name] · [Service requested] · [Human sender name] · [Business name] · [Official business contact]
Draft email:
Hi [First name], Thanks for reaching out about [Service requested]. I have your request and I’m looking at it now. I’ll come back to you with next steps. If you’d rather not hear from me, reply and say so and I’ll close it out. [Human sender name] [Business name] · [Official business contact]
Human verification before sending: the service description matches what they wrote; this channel is permitted.
Tracker status or update: New → Contacted, with the date.
Stop condition: do not send if the request needs escalation rather than routine follow-up.
T-02 — Request for missing information
Purpose: ask for the one or two facts you need to answer properly.
Use only when: you genuinely cannot proceed without them.
Do not use when: the answer is already in the inquiry, or you are asking to seem responsive.
Suggested subject: A couple of details about [Service requested]
Placeholders required: [First name] · [Service requested] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], Thanks again about [Service requested]. To give you a straight answer I need two things: the location, and roughly when you’d want it done. Whenever suits. If you’ve decided against it, just say and I’ll leave it there. [Human sender name] [Official business contact]
Human verification before sending: you are asking the minimum, and nothing sensitive.
Tracker status or update: Verification needed, with the question as the next action.
Stop condition: never ask for payment details, identification, or health information by email.
T-03 — Service-area or basic-fit confirmation
Purpose: confirm you cover the area or the type of work before going further.
Use only when: the fit is now confirmed from your own records.
Do not use when: you are still unsure — that is T-02.
Suggested subject: [Service requested] — we do cover your area
Placeholders required: [First name] · [Service requested] · [Verified service area] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], Good news — [Verified service area] is inside the area we cover, and [Service requested] is work we do. Happy to talk through what you need. If you’d prefer I stop here, say the word. [Human sender name] [Official business contact]
Human verification before sending: the area is confirmed, not assumed; no price implied.
Tracker status or update: Verification needed → Ready for follow-up.
Stop condition: if the area is only probable, do not send. Confirm first.
T-04 — Invitation to choose a call time
Purpose: move to a short call without pressure.
Use only when: you have times you can actually keep.
Do not use when: nothing is scheduled on your side, or you have not confirmed fit.
Suggested subject: A quick call about [Service requested]?
Placeholders required: [First name] · [Service requested] · [Approved scheduling option] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], Would a short call be easier than email for [Service requested]? [Approved scheduling option] works on my side. If a call isn’t useful, email is fine, and if you’d rather stop altogether just tell me. [Human sender name] [Official business contact]
Human verification before sending: the offered time is genuinely open; no scarcity is implied.
Tracker status or update: Awaiting reply, with a follow-up date.
Stop condition: never claim a slot is “the last one” unless that is literally true.
T-05 — First follow-up after no reply
Purpose: one gentle nudge after silence.
Use only when: your own waiting gap has passed and they have not replied.
Do not use when: they replied, or asked for time.
Suggested subject: Following up on [Service requested]
Placeholders required: [First name] · [Service requested] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], Just checking you got my note about [Service requested] — happy to answer anything, or to leave it if the timing is wrong. Either way, a one-line reply is plenty. [Human sender name] [Official business contact]
Human verification before sending: the earlier email really went out; you are within your own limit.
Tracker status or update: Follow-up due → Contacted, then Awaiting reply.
Stop condition: do not send if they already declined, however politely.
T-06 — Second follow-up with an easy close option
Purpose: make the last contact easy to end.
Use only when: this is the final message under the limit you set in advance.
Do not use when: you intend to keep going regardless.
Suggested subject: Closing this out unless you’d like to pick it up
Placeholders required: [First name] · [Service requested] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], I don’t want to keep landing in your inbox, so this is my last note about [Service requested]. If you’d like to pick it up later, just reply whenever — otherwise I’ll close the file and leave you be. [Human sender name] [Official business contact]
Human verification before sending: you mean it. If you send this and follow up anyway, the message was untrue.
Tracker status or update: Awaiting reply with the closing date recorded.
Stop condition: this is the last one. Nothing follows it except a reply from them.
T-07 — Booked-call confirmation
Purpose: confirm a time that is genuinely agreed.
Use only when: they confirmed a specific time.
Do not use when: a time was merely proposed. That is still Awaiting reply.
Suggested subject: Confirmed: our call about [Service requested]
Placeholders required: [First name] · [Service requested] · [Approved scheduling option] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], Confirming [Approved scheduling option] for a short call about [Service requested]. If that stops working, reply and we’ll move it — or drop it entirely, no problem. [Human sender name] [Official business contact]
Human verification before sending: the confirmation exists in writing or in an accepted invitation.
Tracker status or update: Booked, with the outcome recorded.
Stop condition: if the time is not actually confirmed, do not send this — send T-04 again.
T-08 — Request to reschedule a missed or changed call
Purpose: offer a new time without blame.
Use only when: the call did not happen, whatever the reason.
Do not use when: you would be implying fault.
Suggested subject: Rescheduling our call about [Service requested]
Placeholders required: [First name] · [Service requested] · [Approved scheduling option] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], Looks like we missed each other for [Service requested]. These things happen. [Approved scheduling option] is open if you’d like to try again — or tell me to close it and I will. [Human sender name] [Official business contact]
Human verification before sending: nothing assigns blame; the new time is real.
Tracker status or update: Booked → Awaiting reply with a new date.
Stop condition: one reschedule offer, then treat silence as a close.
T-09 — Follow-up after a completed call with an agreed next step
Purpose: put the agreed step in writing.
Use only when: the call happened and something specific was agreed.
Do not use when: nothing was agreed, or your memory is the only record.
Suggested subject: What we agreed on [Service requested]
Placeholders required: [First name] · [Service requested] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], Thanks for your time. To put it in writing: on [Service requested], the next step is the one we agreed on the call, and it’s mine to do. Correct me if I’ve got that wrong. If you’d rather not go ahead, that’s fine too. [Human sender name] [Official business contact]
Human verification before sending: the next step is what was actually agreed, with no price, scope, or date added afterwards.
Tracker status or update: record the agreed next step and its date.
Stop condition: if you are unsure what was agreed, ask instead of asserting.
T-10 — Unable to help or outside scope
Purpose: decline clearly and early.
Use only when: you have established you cannot help.
Do not use when: you are simply busy — say that instead.
Suggested subject: [Service requested] — not something we can take on
Placeholders required: [First name] · [Service requested] · [Human sender name] · [Business name]
Draft email:
Hi [First name], Thanks for asking about [Service requested]. It isn’t something we can take on, so I’d rather tell you now than leave you waiting. I hope you find the right fit. [Human sender name] [Business name]
Human verification before sending: you are not implying a reason you have not verified, and you are recommending nobody you have not checked.
Tracker status or update: Closed — not booked, with the reason.
Stop condition: do not add “but maybe later” unless it is true.
T-11 — Inquiry closure after no response
Purpose: close the file, on the record, courteously.
Use only when: you reached your limit and are actually closing.
Do not use when: it is a disguised extra follow-up.
Suggested subject: Closing your [Service requested] inquiry
Placeholders required: [First name] · [Service requested] · [Human sender name] · [Official business contact]
Draft email:
Hi [First name], I’m closing the file on [Service requested] since I haven’t heard back — no problem at all. If you want to pick it up later, [Official business contact] reaches me directly. [Human sender name]
Human verification before sending: your limit is reached and this genuinely ends it.
Tracker status or update: Closed — not booked, outcome recorded.
Stop condition: if you already sent T-06’s “last note”, consider sending nothing at all.
T-12 — Do-not-contact acknowledgment and permanent stop
Purpose: confirm the request has been actioned, once, and stop.
Use only when: someone asked not to be contacted and a brief confirmation is appropriate.
Do not use when: they asked for no further email at all. Then send nothing.
Suggested subject: Confirming: no further emails
Placeholders required: [First name] · [Human sender name] · [Business name]
Draft email:
Hi [First name], Understood — I’ve removed you from any follow-up and you won’t hear from me again. [Human sender name] [Business name]
Human verification before sending: the removal has already happened, not “will happen”. This is the only message that may follow the request, and it may be skipped.
Tracker status or update: Do not contact, permanent, follow-up date cleared.
Stop condition: nothing follows this, ever, on any channel — no survey, no offer, no re-permission email.
Common mistakes
Sending the sequence instead of choosing one. These are situations, not a campaign.
Manufacturing urgency. False scarcity and “last chance” language are the fastest way to be remembered badly.
Asserting what you cannot show. “As we discussed on the phone” when no call happened, or a price that appears only in your summary, turns a follow-up into a dispute.
Following up after saying you would not. T-06 promises silence. Breaking it is worse than never sending it.
Sending T-12 when silence was requested. If they asked for no further email, send none.
Three synthetic examples
All three are fictional. No real business, customer, inquiry, or transaction is involved, and none is evidence of how these emails perform.
Example 1 — an inquiry with enough information. A fictional gutter-cleaning business receives a web-form inquiry naming the service and the town. T-01 acknowledges it the same day. The area checks out, so T-03 confirms fit and T-04 offers a time the owner can keep. The reply proposes that time, the owner confirms, and only then does T-07 go out.
Example 2 — an inquiry missing a fact. A fictional appliance repair business receives an email naming the problem but not the location. T-01 goes out, then T-02 asks for the location and a rough timeframe — two things, not seven. No quote and no availability are offered meanwhile, because neither is known.
Example 3 — a request to stop. A fictional cleaning business receives a one-line reply asking not to be contacted again. Follow-up ends immediately, the record becomes Do not contact, and the date is cleared. T-12 is optional — one short acknowledgment, or nothing at all if the request was for no further email.
Final takeaway
A good follow-up email is mostly restraint: what you leave out, what you refuse to imply, and the sentence that lets someone end it without awkwardness. These drafts are short because short is easier to make true — and a person still reads every one before it goes.
Related resources, once they exist: the Simple Lead Follow-Up Tracker for Small Businesses; A Simple Lead Follow-Up Workflow: From New Inquiry to Booked Call; guidance on using AI for follow-up with human approval; the Google Review Reply Approval Checklist for Small Businesses; and our Contact, Editorial Policy, and Methodology pages — all planned, none published yet.
Sources
- Federal Trade Commission — CAN-SPAM Act: A Compliance Guide for Business:
https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
Checked on 2026-08-14.
A. What this source supports. That an opt-out must be honored — “You must honor a recipient’s opt-out request within 10 business days” — and that the mechanism “must be able to process opt-out requests for at least 30 days after you send your message.” That header information must not be false or misleading, and that “The subject line must accurately reflect the content of the message.” That a commercial message must carry a valid physical postal address and disclose that it is an advertisement. The page also distinguishes commercial content from transactional or relationship content, and says the primary purpose determines which rules apply.
Scope, stated plainly. Whether a reply to someone’s own inquiry is commercial or transactional depends on that message’s primary purpose. This article does not make that determination for you.
B. The Tool Trial editorial safeguards. The twelve templates, their wording, tone, and length; the subject suggestions; the placeholder set; the verification steps; the tracker states; the stop conditions; and the requirement that a person reads and sends every message. None of this comes from the FTC, which says nothing about follow-up templates, cadence, reply rates, or workflow design.
This article is not legal advice, and using these templates does not establish that any message complies with CAN-SPAM or any other rule. Confirm what applies to your business before sending commercial email.