How to Collect Payments From Pest Control Customers

The easiest payment to collect is the one nobody has to chase. Pest control is sold as recurring service, so the moment a customer signs up for a quarterly or monthly plan is the moment to settle how they will pay for every visit after it. Owners who leave that question for the first invoice end up with an office that spends its afternoons asking for money that could have been charged automatically.

Make autopay the default for service plans. Capture a card or bank account in the signup flow, whether the sale happens at the door, on the phone, or online, and state in the service agreement when charges run: after each completed service, on a fixed monthly date, or once a year up front. A customer who knows when they will be charged is far less likely to dispute the charge.

Some customers will refuse autopay, and that is fine. Record their preferred payment method and contact channel at signup so the invoice and any later reminder reach them the way they asked, instead of whichever way the office happens to try first.

Every extra step between a customer and a payment costs you days. Match the payment method to the kind of work and the kind of customer, and make each option available from the same customer record so payments post without office cleanup.

Card processing has a cost, and bank transfers are usually cheaper for large commercial balances. If you want to pass fees to customers through a surcharge or convenience fee, check your card network rules and the law in each state where you operate first, and disclose the fee before the customer pays.

Termite treatments, bed bug jobs, wildlife exclusion, and other one-time work carry larger balances and no recurring relationship to lean on. When those invoices go unpaid, there is no next visit to bring them up and no plan to pause. Settle payment terms before the work starts.

• Put the price, the deposit if you take one, and when the balance is due in the written estimate the customer approves.
• Take the deposit or a card authorization when the job is booked, not when the crew arrives.
• Have the technician collect the balance, or confirm the card on file will be charged, before leaving the property.
• Send the receipt and any warranty or follow-up visit details the same day, so the customer connects payment with finished work.

Technicians need a simple way to take payment and a clear rule about when to ask. A script as short as “I can take care of today’s balance now, or you can pay from the link we just texted you” turns collection into part of the visit instead of a separate conversation weeks later.

For customers who are not on autopay, the invoice is the first collection attempt. Send it the day the service is completed, by the channel the customer chose, with a link that opens straight to the balance and a way to pay. A paper statement that arrives a week later and asks the customer to call the office is a reminder you will have to send again.

Write the invoice so a customer can tell what they are paying for: the service date and address, what was done in plain language, the plan the charge belongs to, any earlier balance, the due date, and the branch phone number for questions. A confusing invoice gives a customer a reason to wait, even when the amount is right.

• Check what pest control invoicing software should do, billing models, invoice content, online payment, and weekly numbers

Autopay customers still fall behind when a card expires, is replaced, or is declined. Those customers are not avoiding you; they usually do not know anything went wrong. Left alone, a failed charge turns into a 30-day balance, then a 60-day balance, on a customer who would have paid in seconds if someone had asked.

1. Review failed charges every business day, not at month end.
2. Tell the customer the same day, with a secure link to update the card or pay the balance.
3. Retry the charge on a written schedule after the card is updated, so nobody is charged twice.
4. Give one person ownership of the failed-charge list and a target for clearing it within a week.

Treat this queue separately from true collections. A customer with an expired card needs a quick, friendly note, not the same message as a customer who has ignored three reminders.

Many unpaid invoices are not disputes at all. They are forgotten, buried in an inbox, or waiting on whoever handles the household bills. A short, predictable sequence handles those, and it works only if it runs every week, including in peak season when the office is busiest.

1. On the service date, send the invoice with a payment link.
2. A few days after the due date, send a short reminder that names your company, states the balance, and links to pay.
3. Around 30 days past due, send a second reminder and, if the balance is still open, place a brief courtesy call during normal local hours.
4. Around 45 to 60 days past due, have a trained employee call to find out what is in the way and offer a payment arrangement if it helps.
5. Around 90 days past due, make a written decision: arrangement, service hold, write-off, or outside collection.

Treat those intervals as a starting point and set your own in writing, along with a minimum balance worth a reminder and a cap on attempts. Leave out customers on autopay, customers with an agreed payment date, accounts in dispute, and anyone who asked not to be contacted. Stop every reminder the moment a payment posts.

• Build a weekly accounts receivable workflow, aging queues, reminders, handoffs, and owner review
• Use the payment reminder software checklist, how to evaluate reminder automation

Some customers want to pay and cannot pay everything at once. A written payment arrangement, recorded on the account with dates and amounts, usually recovers more than repeated reminders, and it keeps a customer you would otherwise lose. Once an arrangement is in place, routine reminders should stop until a payment is missed.

The harder question is whether to keep servicing an account that is behind. Pick a rule before you need it, for example pausing scheduled service once a balance passes a set age or amount, and apply it the same way at every branch. Tell customers about the rule in the service agreement, and let the office lift a hold the day the account is brought current.

Not every balance is worth more effort. A small balance on a customer who moved away can cost more in staff time than it will ever return. Set a threshold below which old balances are written off, and review the list monthly so the aging report reflects money you can still collect.

For larger balances that stay unpaid after your own process has run its course, a third-party collection agency or small claims court are the usual last steps. Agencies are typically paid a share of what they recover, and placing an account with one usually ends the customer relationship, so reserve it for accounts you have already decided not to keep. Collection agencies, credit reporting, and small claims limits are governed by federal and state rules, so get advice before you start.

The more of your book that pays by autopay, on the invoice link, or after the first reminder, the fewer accounts ever reach this step. That is why the earlier sections matter more than the last one.

A handful of numbers, reviewed weekly by branch, shows whether payment collection is improving or just keeping the office busy.

Good Ops does not process payments or replace your billing. It works with FieldRoutes, formerly PestRoutes, and leaves invoices, autopay, and the customer portal in FieldRoutes as the system of record. Good Ops handles the follow-up step: the balances that are still open after the due date.

Good Ops AI Collections reads your FieldRoutes book each weekday morning for enabled branches and finds customers at least 30 days past due who meet each branch’s rules. It skips customers on autopay, customers with phone reminders turned off, accounts with a payment hold date, and customers who opted out. Eligible customers get a neutral text with their secure FieldRoutes portal link, then a courtesy call if the balance is still open. Customers pay in the portal, never on the call, and Good Ops does not take card numbers.

The Good Ops Mobile App gives your customers a branded app where they can pay balances, reschedule service, and get answers to routine questions. AI Collections costs $400 per branch per month billed annually, or $500 month to month. The Mobile App costs $200 per branch per month billed annually, or $250 month to month. You can buy either one or both.

• Evaluate Good Ops AI collections software for pest control, fit, limits, pricing, and production activity
• See how automated collection calls work for pest control, text, courtesy call, voicemail, payment, and handoff
• See your own past-due queue in a walkthrough, mapped to one of your FieldRoutes branches