Run an automatic sequence for each quarterly visit: a rebooking invitation by text and email about three weeks before it is due, up to two nudges to anyone who has not answered, and a confirmation two days before the technician arrives. Each message asks for one reply or one tap, and every text carries STOP wording.
Most field service apps only remind customers about a visit that is already in the diary. That covers the last message and leaves the hardest job, getting a date agreed in the first place, to the office phone. The sequence below handles both ends, and the office phones only the customers still silent after both nudges. AI does the drafting (tone, length, variants for new customers and missed visits); the timing, the reply rules and the opt-out lines stay yours, because they depend on your app and your customers.
Pre-booked slot or customer-picked day: choose before you draft
There are two ways to run a quarterly programme, and the messages differ.
In the first, the next visit already sits in the diary as a pencilled date, usually because the customer's street falls on a set day of the round (the logic behind route planning for quarterly pest customers). The first message asks the customer to keep that date or move it. Your app's built-in visit reminders can often handle this, depending on your plan.
In the second, no date exists yet. The first message invites the customer to choose one, through a booking link or a reply, and something has to fire on the due date to send it. That suits new customers, homes with awkward access, and firms whose routes are loose enough to shift a visit a week either way.
| Design | First message asks | Date exists already? | Fits best |
|---|---|---|---|
| Standing slot | Keep this date, or move it | Yes, pencilled in | Customers on a fixed round, long-standing accounts |
| Customer-picked day | Choose a day from the open slots | No | New customers, awkward access, flexible routes |
Before drafting anything, find out two things about your app: how far ahead a reminder can be set, and whether a text can carry a link. Jobber's help pages show why this matters. They use a reminder set one day before the visit as their example, allow two scheduled reminders per visit, put a 160-character counter on text templates (a longer message still sends, possibly split into several texts) and rule out emojis and any URL you type into those templates. Jobber adds its own Client Hub link to reminders by default, where the customer can tap Confirm Appointment, and a text customer can also confirm by replying Yes or C. The same two questions apply in GorillaDesk, Housecall Pro or a pest-specific system: look in the reminder or notification settings for the earliest send time and the text limit before you write a word. If your app behaves like Jobber, the three-week invitation needs a different mechanism from the two-day confirmation, such as a batch message sent every Monday to everyone due in three weeks. The Jobber for pest control tutorial covers that app's limits in more depth.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowA 380-customer book: the sequence, the hours and the text bill
Take a three-technician pest control firm with 380 customers on quarterly programmes. The figures are illustrative, so swap in your own. That is 1,520 visits a year, and today each one starts with a phone call from the office. At about four minutes a customer, counting voicemail and call-backs, that is 6,080 minutes, or roughly 101 hours a year spent asking whether someone is free in three weeks.
The replacement is six touches, and only one of them is a person.
| Day | Channel | Goes to | Job of the message | Stops when |
|---|---|---|---|---|
| -21 | Email and text | Everyone due | Invitation: keep the slot or pick a day | Customer replies or books |
| -14 | Text | No answer yet | Nudge with the same two options | Customer replies or books |
| -7 | Text and email | No answer yet | Say the office will phone on a named day | Customer replies or books |
| -5 | Office task | No answer yet | Phone call, the only human step | Visit booked or plan paused |
| -2 | Text | Everyone booked | Confirm the window and give preparation steps | Reply 2 moves the visit |
| +1 | Everyone visited | Service summary and next visit date | Sent once |
Every row after the first goes only to customers who have not answered, so the volume falls away quickly. The stop conditions matter as much as the wording: a customer who confirms on day -21 must never receive the day -14 nudge, and most apps make you set that rule deliberately rather than assuming it.
The hours first. Every ten percentage points of customers who rebook from a message instead of a call saves 152 calls a year, about ten hours of office time. The table shows three outcomes. None is a forecast; your pilot (below) shows which row you are in.
| Share who rebook without a call | Calls still made | Office hours on calls | Hours freed a year |
|---|---|---|---|
| 20% | 1,216 | 81 | 20 |
| 50% | 760 | 51 | 51 |
| 75% | 380 | 25 | 76 |
Then the texts. Each visit uses two to four of them: two if the customer answers the first message and later confirms, four if they need both nudges. Across 1,520 visits that is 3,040 to 6,080 texts a year. Apps and providers price texts differently, so use your own rate card; at an assumed 3 to 10 cents a text the range is about $91 to $608 a year. Emails cost nothing extra in most apps. Price the saved hours at what office time really costs you and set the two numbers side by side before you decide how far to automate.
Templates to paste, with the character count of each
These are filled in, not blank. Square brackets mark the fields your app merges in. The texts follow six rules, each learned from someone else's mistake:
- Business name first, because a text from an unfamiliar sender often gets deleted unread.
- One action per message.
- Digits as replies. Nobody types a word correctly on a phone in the driveway; "1" and "2" survive.
- The STOP line on every text.
- Straight punctuation only, with no emojis (the reason is in the failures section below).
- No promises such as "pest-free" or "guaranteed".
EMAIL, day -21 (invitation)
Subject: Your quarterly pest visit: keep your slot or pick a day
Hi [first name],
Your quarterly pest control visit is due around [date]. To keep your usual slot, reply "keep" to this email. To choose a different day, pick one here: [link]
The visit takes about [duration]. You don't need to be in if we can reach [access areas]. If anything has changed (new pets, a new problem, a different gate code), tell us in your reply.
[your name]
[business], [phone]
Prefer not to get these by email? Reply "no emails" and we'll stop.
EMAIL, day +1 (summary)
Subject: Your pest visit summary and next date
Hi [first name],
Thanks for having us today. Here is what we found and treated: [two-line summary]. Please watch for: [one line]. Your next visit is pencilled in for [next date], and we'll text you three weeks before. If that date won't work, reply with a better one now and we'll move it.
[your name]
[business], [phone]
TEXT, day -21, reply version (130 characters)
[business]: your quarterly pest visit is due around [date]. Reply 1 to keep your usual slot or 2 to pick another. STOP to opt out.
TEXT, day -21, link version (100 characters)
[business]: your quarterly pest visit is due around [date]. Pick a day here: [link] STOP to opt out.
TEXT, day -14 (134 characters)
[business]: we haven't heard back about your pest visit due around [date]. Reply 1 to keep your slot or 2 to move it. STOP to opt out.
TEXT, day -7 (136 characters)
[business]: last message before we phone you on [day] about your pest visit. Reply 1 to keep your slot or 2 to move it. STOP to opt out.
TEXT, day -2 (135 characters)
[business]: your pest visit is booked for [date], [window]. Please clear under sinks and skirting. Reply 2 to move it. STOP to opt out.
The counts include the placeholders as typed. Real values are longer or shorter: a 22-character business name in place of "[business]" (10 characters) adds 12, so leave a 15-character margin under the limit.
The invitation avoids the word "reminder" on purpose. A reminder invites a shrug; an invitation to keep a slot asks for a decision. The email adds what the text has no room for: how long the visit takes, which areas the technician needs, and a prompt to mention new pets or a new problem. That last line earns its place, because a customer who writes "we've seen ants in the kitchen" has just handed you an extra job.
The two nudges use the same two options, so the customer never has to learn a new reply. The day -7 message does something different: it names the day the office will phone. A deadline with a human behind it makes the low-effort reply the easier choice, and it is honest, because the call really happens at day -5.
The confirmation at day -2 is the only message with preparation steps, since confirmations are the messages people read. Set it to go at a fixed time in late morning, and give a window, not a time you cannot keep. The summary email on day +1 does the quiet work of the whole sequence: it puts the next date in front of the customer before they have time to forget the visit happened. If your technicians already write up each visit, the tutorial on AI-written pest control service reports shows how to feed that summary line.
Prompt that drafts the set, and what to fix in its first answer
Give the AI the whole sequence in one request so the messages agree with each other. This prompt works in ChatGPT or Claude, on a free or paid plan, and no customer data goes in, only placeholders.
You are drafting customer messages for [business], a pest control company with three technicians. We run quarterly programmes for homes. Write one sequence for a customer whose next visit is due in 21 days.
Messages needed:
1. Day -21 email (invitation), under 110 words.
2. Day -21 text, under 140 characters including the business name and the opt-out line.
3. Day -14 text for customers who have not replied, under 140 characters.
4. Day -7 text saying the office will phone on [day], under 140 characters.
5. Day -2 text confirming the booking and asking them to clear under sinks, under 140 characters.
6. Day +1 email thanking them and giving the next visit date.
Rules:
- Plain and friendly. No exclamation marks, no emojis, straight quotes only.
- Start every text with the business name.
- One action per message. Replies are 1 (keep) or 2 (move). Never use the word CANCEL.
- Every text ends with "STOP to opt out."
- Do not promise results ("pest-free", "guaranteed") or say anything is safe for pets or children.
- Use only these merge fields: [first name], [business], [date], [window], [day], [link], [your name], [phone].
Show each message with its character count.
The first answer from a prompt like this is usually close, and wrong in predictable ways. This is an illustrative first draft of the day -21 text, from a looser version of the prompt:
Hi [first name]! Hope you’re well. It’s almost time for your quarterly pest control service, so we’d love to get you booked in. Let us know what day works and we’ll keep your home pest-free all year round! Reply CANCEL to stop messages.
It runs to 236 characters and fails in five ways:
- Length. 236 characters is two text segments at best. Many providers bill per segment, and in a tool with a 160-character template limit the second half may arrive as a separate message.
- Curly apostrophes. The typographic apostrophes in "you're", "It's", "we'd" and "we'll" are not in the standard text character set. One of them switches the entire message to a wider encoding that fits only 70 characters in a single segment (67 per segment when a longer message is split). Twilio's documentation gives those figures. This draft would go out as four segments instead of two.
- A promise. "Pest-free all year round" is a guarantee you did not write and cannot keep.
- No business name. The customer sees an unknown number and a chatty greeting.
- CANCEL. It is the most dangerous word in the message, and the failures section below explains why.
After the fixes the same text is the 130-character day -21 reply version above: name first, one decision, two digits, STOP line. Nothing was lost except warmth, which you can put back in the email, where there is room for it.
Reply handling: six replies and what happens to each
A sequence that sends well and handles replies badly is worse than none, because customers learn that answering goes nowhere. Decide in advance what each kind of reply does.
| Reply | Meaning | What should happen |
|---|---|---|
| 1 (or Yes / C, the words Jobber's visit reminders accept) | Keep the slot | Mark confirmed, stop the nudges, keep the day -2 confirmation |
| 2 or "move" | Wants another day | Task to the office with the customer's message, or an automatic booking link by email |
| Free text with a date | "Thursday afternoon is better" | Office reads it, picks a real slot and replies; AI can draft the reply |
| Free text asking to skip | "No problems lately, skip this one" | Phone call from a person the same day |
| STOP, END, QUIT and similar | No more texts | Provider blocks further texts; record it; switch the customer to email and calls |
| Silence | Unknown | Next touch in the sequence; call task at day -5 |
Digit replies only act automatically if your app or texting service is set up to recognise them. Otherwise they land in the shared text inbox for a person to action, which still takes seconds rather than a phone call. If you use Jobber's own visit reminder for the day -2 message, ask for YES rather than 1, because Yes and C are the replies it documents as confirmations.
The skip request deserves its own rule. A customer who says there have been no problems and asks to skip a visit is deciding whether to cancel the programme. That is my reading, not a measured figure, but a five-minute call costs little beside a lost year of quarterly visits, so it should never be answered by an automatic text.
Free-text replies are where AI earns its keep. It reads the message, sorts it, and drafts a response for a person to approve. Paste replies in with the customer's name removed:
Classify each customer reply to a pest control visit invitation into exactly one of: CONFIRM, MOVE_WITH_DATE, MOVE_NO_DATE, SKIP_REQUEST, NEW_PROBLEM, OPT_OUT, WHO_IS_THIS, OTHER. If a reply fits two labels, give both. For MOVE_WITH_DATE, extract the date or day they asked for. Then write a draft reply of under 140 characters for a person to approve. Never promise a time we have not offered.
Replies:
1. Thurs pm better for me
2. Please skip this time, we've had no problems
3. Can you do the 14th? Also seeing ants in the kitchen
4. STOP
5. Who is this?
6. yes
An illustrative output, and what a person would do with each line:
| Reply | AI label | What the person does |
|---|---|---|
| Thurs pm better for me | MOVE_WITH_DATE (Thursday, afternoon) | Check the Thursday round, offer a real window, send the draft once edited |
| Please skip this time, we've had no problems | SKIP_REQUEST | Phone call; explain what the quarterly visit prevents without frightening them |
| Can you do the 14th? Also seeing ants in the kitchen | NEW_PROBLEM and MOVE_WITH_DATE | Book the 14th if it fits, flag the ants to the technician, consider an earlier visit |
| STOP | OPT_OUT | Nothing to send; confirm the customer is marked no-texts |
| Who is this? | WHO_IS_THIS | Reply with the business name and the reason for the text; then check the first message names the business |
| yes | CONFIRM | None; the app should have marked it already |
Notice that the AI handles the sorting, not the decisions. It never moves a date, never answers a skip request and never promises a slot. Reply 3 shows why a label can be two things at once: the customer asked for a date and reported a new problem, and a rule that stopped at the first label would have missed the ants.
The CANCEL trap and four other quiet failures
CANCEL is an opt-out word. Texting providers act on standard keywords automatically. Twilio's documentation lists STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, REVOKE, OPTOUT and QUIT as default opt-outs on long-code and toll-free numbers, and says later messages from that number to the customer are then blocked. Only a single-word reply triggers it: "please cancel" does not, a bare "CANCEL" does. Your provider's list may differ, but the pattern is common. So a customer who replies CANCEL to cancel this visit has, as far as the system is concerned, cancelled every text that number will ever send them, and unless your app flags the opt-out, nobody in the office notices. That is why the templates offer "1" and "2" and why the AI prompt forbids the word. If you want a word reply, test it first by texting your own number from a spare phone.
One curly apostrophe triples the bill. A 135-character text in the standard character set is one segment. Add a single typographic apostrophe, which word processors and AI tools insert freely, and the whole message switches to the wider encoding, where 67 characters fit per segment once it is split. The same 135 characters now cost three segments. Paste every template into a plain-text editor once and retype any apostrophe you did not type yourself. Some providers can swap curly quotes for straight ones automatically (Twilio calls its optional setting Smart Encoding), but do not assume your app has it switched on.
A rescheduled visit can leave ghost reminders. Jobber's help pages say it cancels the reminders tied to the old schedule and creates new ones from the updated time. Not every app does. Move a test visit in yours and check the schedule: a customer who has agreed to Thursday and then receives a nudge for the old Monday date will assume you have lost the booking.
Anytime visits and early texts. Visits booked as "anytime" have no start time to measure a reminder from. In Jobber, text reminders need a set time of day for that reason. Pick a time yourself, such as 10 a.m., instead of accepting whatever the app defaults to.
Landlines. Jobber's help pages note that only mobile numbers can receive texts, and the same is true of most apps, so a customer whose only number is a landline silently drops out of every text step. Add a filter for numbers that failed or bounced, and make sure those customers get the email sequence and the day -5 call.
Opt-out lines, consent records and sending hours
Four small habits keep a reminder programme on the right side of both customers and carriers. None of this is legal advice. Texting rules differ by place, so ask a solicitor or your texting provider's compliance team what applies to you.
Opt-out wording. "STOP to opt out." is 16 characters, short enough for every text. Longer forms ("Reply STOP to unsubscribe from reminders") belong in the email footer, where there is room. Whatever you choose, the app must really honour it: send yourself a test text, reply STOP, then try to send another.
A record of consent. Know when and how each customer agreed to receive texts and emails. The cleanest place is the service agreement, as a ticked line for each channel. The tutorial on drafting a pest control service agreement with AI covers where that clause sits and what a solicitor should check. Keep the date next to the customer's record.
Sending hours. Send between about 9 a.m. and 6 p.m. in the customer's own time zone, never at night, and never at a time the app picked for you. Some places set legal quiet hours; every customer has preferences.
Registration. In some countries, carriers want a business to register its texting number or sender name before sending in volume, and the wait can run from a day or two to several weeks depending on the provider. Ask yours before the first send, not after the first message vanishes.
When someone does opt out of texts, the rest of the relationship continues. Mark the customer as no-texts in the app (Jobber has a per-client "Receives text messages" switch for exactly this), keep them in the email sequence unless they opted out of that too, and let the day -5 call do the work the texts cannot.
Checking it works: a two-week pilot on the next 40 due
Do not switch the sequence on for all 380 customers at once. Pick the next 40 whose visits fall about three weeks out, add five staff phones as test customers, and run the whole thing for two weeks.
- Before day one, send each template to a staff phone and check the character count, the merge fields (no "[first name]" left showing) and the STOP line.
- Move a visit on a test customer and confirm the old reminders disappear.
- Reply to every message type from a staff phone: 1, 2, a free-text date, a skip request, STOP. Confirm each does what the reply table above says.
- Track five numbers across the 40 real customers.
| Number | Where to read it | What a poor reading usually points to |
|---|---|---|
| Confirmed or booked after the first message | App schedule or reply log | Weak invitation, wrong time of day, or a link that does not work on phones |
| Still needing a call at day -5 | Task list | Add the link version of the text, or send the invitation a week earlier |
| STOP replies | Provider log | Unknown sender name, odd send time, or too many nudges; read the replies |
| Texts that failed to deliver | Provider log | Landlines and old numbers; clean the list |
| Replies the AI sorted wrongly | A person checking all of them | Tighten the labels in the prompt |
There is no industry benchmark worth holding your results against, so compare the pilot with your own phone-only quarter. If more than three in ten customers still need the day -5 call, I would add the link version of the text or move the first message a week earlier, then run another 40. Treat a rising STOP count as a message problem rather than a customer problem, and read the replies themselves: they usually say what was wrong.
Variants for a new customer, a missed visit and a winter pause
Once the main sequence works, the variants are quick to draft. Give the AI the working templates and ask for each variation in the same voice.
- New customer. The first visit is booked straight away, so the sequence is just the day -2 confirmation with more preparation detail and a line saying what the technician will do. Draft: "[business]: your first pest visit is booked for [date], [window]. Please clear under sinks and skirting. Reply 2 to move it. STOP to opt out." (141 characters; with a long business name, trim "and skirting".)
- Winter pause. If some customers pause visits in the colder months, send a pause offer instead of the invitation: "[business]: want to pause your pest visits over winter? Reply 1 to pause until [month] or 2 to keep them. STOP to opt out." Then set a reminder to reopen the plan, or the pause becomes a quiet cancellation.
- Missed visit. When the technician could not get in, send the text the same afternoon: "[business]: we couldn't get in for your pest visit today. Reply 1 for the next free slot or 2 to choose a day. STOP to opt out." Missed visits go cold fast, and this is the message most worth sending the same day.
- Commercial site. Send to the site contact and a second person, ask for access arrangements and a time window, and attach the report to the day +1 email so it can go straight into the customer's own records.
If you would rather map this against your actual app and customer list with someone, that is what my AI implementation consultation covers.
Questions owners ask before switching reminders on
How far ahead should a quarterly pest control reminder go out?
About three weeks before the visit is due for the first message, which leaves room for two nudges and a phone call before the date. A confirmation two days before the visit is a separate message with a different job: prepare the customer, not book them. Shorter notice works for customers on a fixed round, but it leaves the office no time to chase.
Should the reminders be texts, emails or both?
Both, with different jobs. Texts get read quickly but are short and may not carry a link in your app. Emails can hold the booking link, the access questions and the service summary. Send the invitation by both, the nudges by text only, and the visit summary by email. Customers without a mobile number get the same sequence by email and a call at the last step.
Can I send these from my own phone instead of an app?
For ten customers, yes. At several hundred a year it breaks down: nobody records consent, STOP replies are missed, and one person's phone holds the whole conversation history. Use the texting built into your field service app, or a business texting service connected to it, so replies and opt-outs are logged against the customer.
What if a customer replies with a question about the treatment?
A person answers it. Reply handling can sort messages and draft a response, but anything about chemicals, pets, children or health goes to a technician or the office manager, who knows what was used. Set the app so any reply that is not 1, 2 or STOP creates a task rather than an automatic answer.
Further reads
- Gutter Cleaning Software: Reminders, Routes and Recurring Bookings With AI — The same recurring-visit pattern for another trade, with route and booking set-up.
- AI Service Plan Reminders for Heating and Cooling Customers — Service-plan reminders from heating and cooling, where renewals matter as much as visits.
- How to Reduce No-Shows With AI Reminders and Automatic Rebooking — The confirm-or-move pattern applied to appointments in general.
- How Dental Practices Use AI for Recalls and Appointment Reminders — Recall schedules in a dental practice, the closest non-trade model for quarterly visits.
- AI Receptionist Pricing for Pest Control: What 100 and 300 Calls Cost — What it costs to answer the calls that still come in after the messages go out.
- AI for Pest Control Companies: What a Monthly Toolkit Costs — Where reminders fit in a full monthly AI toolkit for a pest control firm.
- How to Price Pest Control Services With an AI-Built Rate Sheet — Set the quarterly plan price before you invite customers to rebook it.
- Pest Control Estimate Software: What AI Adds and What It Costs — What AI adds to pest control estimates in GorillaDesk, Jobber and Housecall Pro, what each costs a month, and a break-even sum for a small firm.
- Pest Control Lead Generation Tools Compared: Cost per Booked Job — A worked month comparing seven pest control lead sources on cost per booked job, plus what call tracking and AI text-back add and cost.
- Alarm Maintenance Contracts: Renewal Letters and Reminders With AI — Renewal letters built from locked, lawyer-approved clauses plus AI-filled lines, with a reminder timeline, price-change wording and opt-outs.
- Commercial Pest Control Leads: Prospect Warehouses and Offices With AI — A hand-built prospect list by premises type, survey-offer emails, a follow-up cadence and a claims check, with AI doing the sorting and drafting.
- Gutter Cleaning Marketing: Eight Spring and Autumn Campaigns With AI — A Leaf Week calendar of eight campaigns, with AI prompts, sample copy and a tracking sheet so you know which gutter cleaning marketing booked jobs.
- Local Services Ads for Pest Control: Bad Leads and the Google Ads Move — Which pest control leads Google may credit, how to write feedback from call summaries, and what to export before Local Services Ads move into Google Ads.
- Mosquito Control Business: Quotes and Season Plans With AI — A yard-size quote table, season plan pricing and the messages around it, with AI drafting the replies, reminders and review requests from your own numbers.
- Pest Control Company Content Marketing: A Seasonal AI Calendar — Twelve months of pest control posts, emails and service-page updates built around ant, wasp, rodent and bed bug seasons, with AI prompts.
- Pest Control Proposal Template: Draft Commercial Bids With ChatGPT — Turn site survey notes into a commercial pest control bid: scope, visit frequency, reporting and exclusions drafted with ChatGPT, then checked.
- How Can AI Help My Pest Control Business? Three Jobs to Start With — Three jobs to hand to AI first in a pest control business, missed calls, quotes and service summaries, with payback sums and a clear list of what stays manual.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Jobber help articles (assessment and visit reminders, emails and text messages settings, recurring jobs); Twilio documentation (SMS character encoding, default opt-out keywords).