By The Tool Trial Editorial Team
An inquiry arrives. Someone means to reply. Four days later nobody can say whether anyone did, and the person has already hired someone else.
The gap is rarely effort. It is that “follow up on that lead” is not a step — it is a wish. A workflow turns it into seven decisions, each with a named owner, a defined entry point, and an explicit place to stop.
This one runs by hand, on email and forms. It sends nothing on its own, and no step happens without a person choosing it.
This is practical editorial guidance, not legal advice, and it does not guarantee compliance with any law or rule.
What this workflow is — and what it is not
It is a decision sequence, not a script. Each stage tells you what must be true before you act, what you may do, and when to stop. It does not tell you what to write — that belongs to the follow-up email templates, a separate planned resource.
It is manual, and email-first. Email, web forms, and a phone call the person invited. No SMS and no automated calling, because consent, eligibility, and cost for those channels are unresolved and outside this article.
It automates nothing. No sequencer, no auto-reply, no scheduled sending. Every message a person receives was written and sent by a person who decided to send it.
It uses no AI. Whether and how AI may assist follow-up, under human approval, is a separate planned resource. No stage here delegates a decision to a model.
It promises nothing. No stage makes a booked call more likely, and no figure in this article is a measured result. Running the sequence correctly still ends in “closed — not booked” much of the time, and that is a legitimate outcome, not a failure of the process.
Before you start: what must already be decided
Four decisions belong to the business, not to the workflow. Make them once, write them down, and the seven stages become mechanical.
Who owns follow-up. One named person per inquiry. Not a team, not a rota nobody published.
Which contact channels you own and monitor. A business email you read, a form on your own site, a phone line you answer. Nothing else may be used.
Your cadence and your limit. How long you wait between contacts and how many you make before closing. These are your settings, not industry rules. No timing in this article is presented as optimal, because no such measurement exists here. Choose numbers you can actually sustain, write them down, and apply them consistently.
What “booked” requires. Define the evidence — a confirmed appointment, a written yes, a calendar entry the person accepted. Decide it in advance, before a hopeful conversation tempts you to record one early.
The seven stages
The stages below reference lead states — New, Verification needed, Ready for follow-up, Contacted, Awaiting reply, Follow-up due, Booked, Closed — not booked, and Do not contact. They match the Simple Lead Follow-Up Tracker for Small Businesses, a planned resource that is not yet published. You do not need that tracker to run this workflow — any table with those states works, and this article does not reproduce it.
1. Receive — capture the new inquiry
Entry condition: an inquiry arrives through any channel you monitor.
Required information: the date, the channel it came through, and roughly what was asked. Nothing more.
Human decision: none yet. Capture is not assessment.
Allowed action: create the record. Do not reply, do not research, do not judge.
Tracker update: new record, internal reference as the key, state New.
Exit condition: the inquiry exists as a record with a reference and a date.
Stop or escalate: if the message contains a threat, an allegation about a person, or anything plainly outside customer service, stop here and route it to an appropriate person.
2. Verify — confirm what arrived and whether you can handle it
Entry condition: a record in New that nobody has assessed.
Required information: what was actually asked, whether it is inside your service area, whether it is work you do, and which channel the person used and what they agreed to when they used it.
Human decision: can this be handled, and is there a channel you are permitted to reply on?
Allowed action: check your own records and the inquiry itself. Do not contact anyone to verify — contacting is stage 5.
Tracker update: Verification needed while a question is open; Ready for follow-up once area, scope, and permission are settled. Record the permission as observed, not as assumed. If you cannot tell, write Unknown.
Exit condition: every open question is answered, or the record is closed as out of area or out of scope.
Stop or escalate: stop if the request involves health, payment disputes, legal threats, minors, or anything you are unsure you may act on. A new inquiry is not blanket consent to contact someone however you like — if you cannot establish a permitted channel, the record does not proceed.
3. Assign — name who owns the next action
Entry condition: a record in Ready for follow-up with no owner.
Required information: who is available, and who is allowed to speak for the business on this kind of request.
Human decision: which named person owns the next action.
Allowed action: assign one person. Not a team, not “whoever gets to it.”
Tracker update: the assigned owner, plus the next action written as a verb and a due date.
Exit condition: the record has an owner, one action, and one date — all three.
Stop or escalate: if nobody available is authorized to handle this request, escalate rather than assigning it to whoever is free.
4. Choose — select an approved contact channel
Entry condition: an assigned record where contact has not yet been made.
Required information: the channel the person used, what they agreed to, and which of your channels you actually monitor.
Human decision: which single channel to use — or that none is available.
Allowed action: choose from channels you own and monitor. Replying on the channel they used is usually the defensible choice. Do not invent a channel, and do not switch to SMS or an automated call.
Tracker update: the approved channel. Leave it blank rather than guessing.
Exit condition: one channel is recorded and permitted.
Stop or escalate: if no channel is both available and permitted, the record stops. Escalate the question rather than proceeding on an assumption.
5. Follow up — make the first authorized contact
Entry condition: an assigned record with an approved channel and a due date that has arrived.
Required information: what they asked, what you can honestly answer, and what you are authorized to offer.
Human decision: what to say, and whether you are the person to say it.
Allowed action: one contact, written and sent by a person, on the approved channel. The wording is out of scope here — it belongs to the follow-up email templates, a separate planned resource.
Tracker update: state Contacted, then Awaiting reply with the next follow-up date. Record the last contact date.
Exit condition: the contact was made and the record shows when.
Stop or escalate: stop immediately if the reply would require confirming something you have not verified, or committing to something you cannot authorize.
6. Decide — continue, wait, stop, or close
Entry condition: the follow-up date has arrived, or a reply has come in.
Required information: what happened since the last contact, and how many approved contacts you have already made against the limit you set.
Human decision: one of four — make another approved contact, keep waiting, stop, or close.
Allowed action: move the date with a reason, make one further approved contact if you are under your limit, or close the record. Awaiting reply is not Booked. A warm reply is still Awaiting reply until something is actually confirmed.
Tracker update: Follow-up due when a date passes with no reply; Closed — not booked when you reach your limit, they decline, or it is out of scope. Do not contact the moment anyone asks you to stop.
Exit condition: the record moves to another stage, or it is closed with the outcome recorded.
Stop or escalate: a request to stop ends the workflow immediately, on every channel, and is permanent unless the person themselves says otherwise. Escalate anything that has turned into a complaint or a dispute.
7. Book and hand off — record a confirmed call and prepare the handoff
Entry condition: the person has confirmed a specific time.
Required information: the confirmation itself, the agreed time, and what the call is about.
Human decision: is this confirmed, or does it only feel confirmed? Mark Booked only when you have verifiable confirmation — an accepted invitation, a written yes, a scheduling entry they completed. “They sounded keen” is not confirmation.
Allowed action: record the booking and hand the record to whoever runs the call.
Tracker update: state Booked, the outcome recorded, and the record leaves the follow-up queue.
Exit condition: the person running the call has what they need: the reference, what was asked, what was already said, and the approved channel.
Stop or escalate: if the booking is uncertain, leave it in Awaiting reply. Booked is a state, not a result — it records that a call is scheduled, nothing about whether work follows.
Rules that apply at every stage
Collect only what the next action needs. No sensitive detail, no full conversation transcript, no information about third parties, and nothing copied into free-text notes because it seemed interesting.
A person decides at every stage. Nothing here moves a record forward on its own, and no step publishes, sends, or replies automatically.
Record states, not hopes. Every state describes where something is. None of them predicts, scores, or ranks.
Stop conditions outrank everything. A do-not-contact request, an unresolved permission question, or a case that belongs with someone else stops the sequence wherever it is.
Three synthetic examples
All three are fictional. No real business, customer, inquiry, or transaction is involved, and none is evidence of how this workflow performs.
Example 1 — a confirmed call. A fictional two-person landscaping business receives a web-form inquiry about a quote. Captured as New, verified as in-area with a form-provided email, assigned to the owner, replied to by email, and moved to Awaiting reply. The person replies proposing a time, the owner confirms it, and only then does the record become Booked — with the accepted time as the confirmation. The handoff carries the reference, the request, and what was already said.
Example 2 — waiting, then closed. A fictional appliance repair business receives an emailed question about a recurring service. Verified and answered once on the same channel, then Awaiting reply. The date passes; a second approved contact goes out under the limit the business set in advance. Nothing comes back. It closes as Closed — not booked with the outcome recorded. No third contact is attempted, because the limit was decided before this particular lead made it tempting.
Example 3 — a request to stop. A fictional cleaning business receives a reply asking not to be contacted again. The workflow ends there. The state becomes Do not contact, the follow-up date is removed, no closing message is sent, and the request is treated as permanent. No stage of this workflow overrides it.
Final takeaway
The value is not the seven stages. It is that each one names who decides, what must be true first, and where the sequence stops — so a lead that goes nowhere goes nowhere on purpose, and a call marked booked is one somebody actually confirmed.
Related resources, once they exist: the Simple Lead Follow-Up Tracker for Small Businesses; follow-up email templates; guidance on using AI for follow-up with human approval; the Google Review Reply Approval Checklist for Small Businesses; and our Contact, About, Methodology, and Editorial Policy 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 - Federal Communications Commission — Stop Unwanted Robocalls and Texts:
https://www.fcc.gov/consumers/guides/stop-unwanted-robocalls-and-texts
Both were opened and read on 2026-08-12, and both are cited only for the statements below.
What the FTC page supports: that CAN-SPAM covers commercial email generally — “The law makes no exception for business-to-business email” — and that “You must honor a recipient’s opt-out request within 10 business days.”
What the FCC page supports: that “FCC rules also require a caller to obtain your oral or written consent before making an autodialed or prerecorded call or text to your wireless number”, and that “You may opt out of any robocall or robotext at any time and in any reasonable manner, even if you previously gave consent for such calls.”
What neither page supports. Neither addresses lead follow-up workflows, stage design, ownership, cadence, or when to stop contacting someone — verified by searching both pages for that material and finding none. The seven stages, the lead states, the stop conditions, the cadence guidance, and every privacy safeguard here are editorial guidance developed by The Tool Trial, not requirements from either agency.
None of this is legal advice, and nothing here establishes that a given practice satisfies CAN-SPAM, the TCPA, or any other rule. Requirements depend on what you send, how you send it, and to whom; confirm the current official guidance before any commercial outreach.