Template · Service business operations
Follow-up checklist and sample messages
An editable checklist, three optional message templates and a simple action log for reviewing existing enquiries and quotes before contacting a customer.
Written by Fireflax · 6 minute read
Reviewed by Codex — source and implementation review ·
A reusable review pack for your office.
Use the checklist before every draft, then adapt the message that matches the situation. These are separate options, not a required three-message sequence. The right next step may be a reply, a wait or a closed enquiry.
Drafts for a person to review
These templates are for existing enquiries and quotes. They do not send anything, connect an inbox or authorize outreach. Timing and permitted contact depend on your actual relationship, customer preferences and channel. No response rate or legal blanket permission is claimed.
Plain-text Markdown · version 1.0 · no email gate or software setup. Open it in your usual text editor. Everything in the pack is also explained below.
Before every message
- 01
Confirm the relationship
This concerns an existing request to your business. Check the actual contact preferences and appropriate channel; a template does not give permission to contact someone.
- 02
Look for a reason to stop
Check the current inbox, telephone notes and job or quote status. A reply goes back to the owner. An opt-out, closed opportunity or booked job stops this follow-up sequence.
- 03
Choose one owner and one next action
Record who is responsible. Use any date or arrangement agreed with the customer. If timing or the current status is unknown, hold the draft and investigate.
- 04
Replace only known details
Use verified context and one useful question. Remove unknown placeholders; do not invent a price, appointment, service detail, quote number or prior conversation.
- 05
Approve the final version
Recheck the recipient and latest status immediately before sending. A saved draft is not approval, and approval is not proof of delivery.
- 06
Record the outcome and stop point
After sending through your usual system, record the actual outcome and next review date, if any. Handle replies as a conversation. Do not restart a stopped sequence automatically.
Three messages to adapt
1. An unanswered enquiry
You already replied to a customer's request and need to check whether help is still wanted.
Optional email subject: Your enquiry about [requested work]
Hi [first name], I'm following up on your enquiry about [verified request]. Would you still like us to help, or should we close the enquiry for now? Thanks, [owner name] [business name]
Remove the specific job description if you cannot verify it. Resolve that uncertainty before contacting the customer.
2. Clarify a quote question
A quote has already been sent and there is one known detail to clarify. Respond to an existing reply directly when there is one.
Optional email subject: A question about [quote reference or work]
Hi [first name], About the quote for [verified work], could you confirm [one specific question]? This will help [owner name] check the next step before we make any changes. Thanks, [owner name] [business name]
Do not turn an uncertain scope, price or appointment into a promise. Omit a quote reference if none is available.
3. A courteous final check-in
A final contact is appropriate for the relationship and your agreed process, and none of the stop conditions applies.
Optional email subject: Closing the loop on [requested work]
Hi [first name], Just checking whether you still need help with [verified request]. If we don't hear back, we'll close this follow-up for now. You can contact us again if you would like to revisit it. Thanks, [owner name] [business name]
After this step, stop the sequence according to your recorded plan. Do not add pressure, false deadlines or repeated final messages.
A filled example, with the review attached
Fictional example: Robin asked Cedar Example Plumbing about a dripping kitchen tap. Alex checked the enquiry and telephone notes: no reply, booking or stop request was recorded. The actual appropriateness of contact would still need to be confirmed before sending in a real business.
Fictional draft · nothing sent
Hi Robin,
I'm following up on your enquiry about the dripping kitchen tap. Would you still like us to help, or should we close the enquiry for now?
Thanks,
Alex
Cedar Example Plumbing
If a new call note says Robin has booked elsewhere, Alex stops here. If Robin replies with a question, Alex handles that question and cancels the pending follow-up. The existence of a prepared draft never overrides newer information.
Keep a short log and a visible stop control.
Copy this record into the system you already use. Keep one entry per action so a second person can see what happened. Do not record a delivery until you have evidence from the sending system.
- Request and owner
- Record reference, responsible person and current status.
- Latest check
- Who checked replies, calls and contact preferences, and when.
- Draft and approval
- Chosen message, edits, reviewer and approval time—or held, with reason.
- Delivery outcome
- Not sent, sent with a reference, failed or unknown. Approval alone is not delivery.
- Next action
- A specific review date and owner, or no further follow-up.
- Stop status
- Active / paused / stopped, with reason and time. Cancel any pending reminders in the actual system.
Stop when someone replies, opts out, books the work or closes the opportunity, or when your agreed final step is complete. A failed or uncertain delivery needs investigation before retrying; it is not a reason to send the same message again blindly.
The sample uses rules and prepared templates in browser memory. Its three-day threshold is illustrative. Approval simulates an action; it does not deliver a message or test your own systems.
Sources and review notes
Drafted with Codex and checked against the linked sources on the review date. Examples are fictional; no customer results or live integration are claimed.
- The follow-up decision guide
Process and original short message example.
- Follow-up sample
Fictional stop conditions and simulated approval.