The Quiet Customer Check: how to win back lapsed pest control customers in FieldRoutes

This is the guide from the Cortex video on the Quiet Customer Check. It has the same three steps as the video, in the same order, and then the detail you need to run them: the date rules, the messages, what to hold back and how to tell it is working.

1. The date check. Compare each customer's last completed service with their plan and flag the ones who are past it.
2. The drafted note. A short message that names their service and offers two times, read and approved by your office manager.
3. The API access email. One email to FieldRoutes support, because your plan has to include API access before anything outside FieldRoutes can read those dates.

You can run step 1 and step 2 by hand this week with an export and a spreadsheet. Step 3 is what lets an agent do it every morning instead.

Why lapsed customers slip through

Nothing tells you a customer has gone quiet. FieldRoutes can send job events to another system through trigger rules, and an automation agency that builds on FieldRoutes, Rex Automaton, lists those events as a job being scheduled, rescheduled, completed or canceled. Every one of them is something that happened. A quarterly customer who simply never books again creates no event at all, so the only way to see them is to look at dates.

That is why this check is built on dates and not on alerts. It also means you can start without any software change.

Who this is for and what you need first

This is for pest control and lawn companies on FieldRoutes with recurring plans: quarterly pest, monthly mosquito in season, annual termite inspections, lawn rounds. It works for one office or several, as long as each office is checked on its own.

Before you start, have these ready:

• A list of your active plan types and how often each one should be serviced.
• An export of customers with their plan type, last completed service date and contact details.
• The consent record for each customer: who agreed to texts, who agreed to email, and who agreed to neither.
• One person who owns the list each week. In most offices that is the office manager.

Step 1, the date check

For each plan type, write down the gap you expect between services and add a grace period, so a customer who is a few days late is not treated as lost. The numbers below are a starting point we suggest, not an industry standard. Change them to match how your routes really run.

Plan type	Expected gap	Grace	Flag when the last service is older than
Quarterly pest	90 days	10 days	100 days
Bi-monthly pest	60 days	10 days	70 days
Monthly mosquito (in season)	30 days	7 days	37 days
Annual termite inspection	365 days	30 days	395 days
Lawn round	your round length	7 days	round length plus 7 days

Sort the flagged list by how far past the line each customer is. Someone at 101 days is a scheduling slip; someone at 200 days may have switched providers, and the note to them should be different.

Then remove anyone who should not get a message this week:

• An open complaint, a damage claim or a refund in progress. A person calls them.
• An overdue invoice. Collect first or let the office decide.
• A cancelled plan with a recorded reason, such as moving away.
• Anyone without consent for the channel you would use.

Rex Automaton gives the same advice for review requests in the same FieldRoutes post: do not send one after an incomplete job, an overdue invoice, an open complaint or a refund, and keep opt-in consent per channel. A win-back note deserves the same care.

Step 2, the drafted note

The note has three jobs. It says who you are, it names the service they had, and it offers a specific time so the reply can be one word. Keep it short enough to read on a lock screen.

Three messages to copy and edit. The names and times are examples.

Just past the line (a scheduling slip):

Hi Mrs. Okonkwo, it's Greenline. Your quarterly pest service is due. We have Tuesday at 10 or Thursday at 2, want one?

Well past the line:

Hi Dan, it's Greenline Pest & Lawn. It's been a while since your last quarterly service, and we'd be glad to get you back on the route. Reply with a day that works and we'll hold a time.

Seasonal plan, before the season starts:

Hi Maria, it's Greenline. Mosquito season is close and your yard treatments start again soon. Want us to put you back on the schedule? Reply YES and we'll text you the first date.

Your office manager reads each draft before it goes. They check the name, the service, the times offered and whether anything in the account says to call instead. Start with a person approving every note; we explain why in human-in-the-loop AI. If FieldRoutes already sends reminders for you, decide which system owns which message so nobody gets two texts in one day.

Step 3, the API access email

To run the date check every morning instead of from an export, software outside FieldRoutes has to read your customers and jobs. Podium's FieldRoutes setup page says your plan must include API access and that you email FieldRoutes support to request the credentials: a subdomain, an authentication key and an authentication token.

A message you can send:

Hi, we'd like to connect an outside tool to our FieldRoutes account to read customers, plans and completed jobs. Does our current plan include API access? If it does, please send the subdomain, authentication key and authentication token for our office. If it doesn't, which plan would we need?

FieldRoutes describes its API as a way to share data with any vendor of your choosing, and it lists the API next to routing and scheduling on its home page. Treat the token like a password. Keep a separate set of credentials for each office.

Rex Automaton reports documented defaults of 3,000 reads and 3,000 writes per office at 60 requests per minute in its FieldRoutes post. That is plenty for a morning check and too little to pull years of history in one go, so the first sync should run slowly. It is an agency's reading of the docs, so confirm it in your own account.

If you were hoping a no-code tool would cover this, check first. CallRail's support team told one customer in 2024 that it had no native FieldRoutes integration and suggested a custom build against the API.

What to watch out for

• Matching the wrong person. Match on address and phone, not just the surname. Neighbours share names.
• Duplicate events. Rex Automaton notes that a retried webhook can create a duplicate record. Give each event an ID and skip any ID you have already handled.
• Plans that changed. A customer who moved from quarterly to annual will look lapsed under the old rule. Read the current plan, not the first one.
• Recurring service decisions. Pausing, cancelling or repricing a plan stays with the office manager or owner.
• Safety complaints. A complaint about a chemical, a pet or a child goes to a person the same day.

How to tell it worked

Track four numbers every week, from your own records: how many customers were flagged, how many notes went out, how many replied and how many rebooked. After a month you will know which plan type drifts most and which message gets answered. If the flagged list is long and the rebooked number is small, the problem may be earlier, in how plans are sold or renewed, and that is worth a conversation of its own.

If you want the longer background on how agents connect to FieldRoutes, read how an AI agent for FieldRoutes works. For other ways to bring customers back, see customer reactivation. And if you would like someone to look at where this fits with the rest of your office, your free AI Operations Audit covers it in 30 minutes.