← All posts
Home ServicesJuly 10, 2026 · 8 min read

Declined card, dropped customer: fixing failed recurring billing in pest control

A single failed charge in a recurring pest control plan rarely stays a single charge. Here is what that failure actually costs you and the exact steps to stop the bleeding before the customer quietly disappears.

by Corex AI Team

The charge fails, and you probably don't find out for days

Here's how it usually goes. A customer signed up for your quarterly plan eight months ago. Auto-pay is on. You forget about them, because that's the whole point of recurring billing. Then the card on file gets declined, your software fires off a generic "payment failed" email, and the customer either ignores it, means to fix it later, or simply assumes you'll figure it out. You don't. Nobody calls anybody. The next scheduled service comes around, your tech shows up, does the work, and you still haven't collected. By the time someone on your team notices the account is in arrears, you're out two service visits and the customer has mentally moved on to a competitor who offered a deal last week.

This is not a rare edge case. Industry data consistently shows that 5 to 10 percent of recurring card transactions fail in any given month. For a pest control company running 200 active plan customers at $50 per month, that's 10 to 20 failed charges every single month. At $50 a pop, you're looking at $500 to $1,000 in revenue that simply didn't land, before you even count the cost of service already delivered.

What a declined card actually costs you

Most operators look at a failed charge and see a $50 problem. The real number is bigger, and it compounds.

  • The service cost: If your tech already treated the property, you've spent roughly $15 to $25 in labor and materials for a job you haven't been paid for.
  • The follow-up cost: Someone on your team has to identify the failure, contact the customer, and chase the updated card info. That's 15 to 30 minutes of admin time per incident, conservatively.
  • The churn cost: If the customer doesn't update their card, they quietly churn. A recurring pest control customer is worth $200 to $600 per year depending on your plan structure. Losing one to a billing glitch, not to a service problem, is the most avoidable revenue leak in this business.
  • The reacquisition cost: Getting that customer back, or replacing them, costs you marketing dollars and sales time. Figure $75 to $150 in customer acquisition cost at minimum for most local pest control operators.

Add it up for a single churned customer: $25 in delivered service plus $30 in admin time plus $150 in reacquisition cost. That's $205 in real losses from one $50 failed charge. Scale that across 10 to 20 failures a month and you're eroding thousands in annual margin, quietly, in the background.

Why the standard "retry it tomorrow" approach falls short

Most field service software will automatically retry a failed charge once or twice. That's better than nothing, but it misses the core issue. A card that declined because it hit its limit will probably decline again tomorrow. A card that was reported lost and replaced will never succeed again no matter how many times you retry it. The retry-and-hope approach recovers maybe 20 to 30 percent of failed charges. The rest require human action, specifically getting the customer to update their payment method.

The problem is timing and tone. Generic "your payment failed" emails have open rates under 30 percent and conversion rates that are even worse, because they feel impersonal and a little accusatory. Customers don't read them carefully. They don't feel urgency. And if your follow-up process is someone on your team manually combing through an aging report every Friday afternoon, you're already two or three days behind.

The mechanic of a real fix

A working dunning process, which is the industry term for recovering failed payments, has four moving parts.

  1. Immediate detection: The moment a charge fails, the system knows. Not when someone pulls a report, not when the tech shows up at the door. Immediately.
  2. Smart retry logic: Not just "retry tomorrow." Retry on a schedule based on the likely failure reason. Card over limit? Wait four days. Card replaced? Skip retries and go straight to the customer. Some payment processors pass back decline codes that let you make this call automatically.
  3. Sequenced outreach: A short, human-sounding text or email that goes out within hours, not days. Followed by a second touch 48 hours later. Followed by a phone call on day five if nothing has been resolved. Each message should have a direct link for the customer to update their card, not instructions to call your office during business hours.
  4. Service hold logic: If a payment has been unresolved for more than 7 to 10 days, you need a flag on the account so your tech doesn't show up and do unpaid work. This isn't punishing the customer. It's protecting your business while you work to resolve the billing issue.

That four-step mechanic, done consistently, can recover 60 to 80 percent of failed charges that the simple retry approach misses. The math on that recovery rate is significant. If you're losing $1,000 a month to failed charges and you recover 70 percent of them, that's $700 back in your pocket every month, or roughly $8,400 a year, from a process that runs mostly on automation.

How to set this up in your business

Step 1: Audit your current failure rate

Pull an aging report from your billing software right now. Filter for accounts with an outstanding balance tied to a recurring plan, not one-time jobs. Count them. Calculate the dollar total. Most operators are genuinely surprised by this number. If you don't have a clean way to pull this report, that's itself a problem worth fixing.

Step 2: Set up automated detection and immediate outreach

Your billing platform should support webhooks or at minimum email alerts when a charge fails. If you're running a system like Corex for pest control, failed payment detection and automated customer outreach is built into the recurring billing workflow, so you're not manually watching for failures. If you're on a generic tool, check whether it supports Zapier integrations that can trigger an SMS through a service like Twilio the moment a charge fails.

Step 3: Write two or three human-sounding message templates

Don't let your payment processor's default message be your customer's first touchpoint. Write something short and plain. Something like: "Hey, we tried to run your payment for your pest plan today and the card on file didn't go through. It happens, no big deal. Here's a quick link to update it: [link]. Let us know if you have any questions." That tone converts better than a formal "Dear valued customer, your payment of $50.00 has been declined" notice every single time.

Step 4: Build a five-day escalation sequence

Day one: automated text with the update link. Day three: follow-up email. Day five: personal call from your office. If you hit day five with no response, flag the account for service hold and have a real conversation with the customer about whether they want to continue the plan. Some will update their card immediately once a human calls. Others have already mentally cancelled and just haven't told you. Both outcomes are better than delivering another free service visit.

Step 5: Lock down card-on-file capture at signup

The best time to prevent a failed charge is before it happens. At plan signup, collect card info through a tokenized payment form, not a paper form or a verbal number over the phone. Require a valid card as part of enrollment, not as an optional step. Consider using a card updater service, most major processors offer one, which automatically updates card numbers and expiration dates when a customer gets a new card from their bank. This alone can cut your failure rate by 20 to 30 percent.

Step 6: Review your module settings and reporting cadence

Once the process is running, build a weekly review into your routine. Check your billing module's dashboard for the number of failed charges, recovery rate, and average days to resolution. If your recovery rate drops below 60 percent for two consecutive weeks, something in your outreach sequence has broken. Fix it before it compounds. And if you want to compare what this process looks like against other platforms before committing, see how Corex stacks up against Jobber on recurring billing specifically.

One honest caveat

If you're running fewer than 50 recurring plan customers, this level of automation is probably overkill. A simple spreadsheet check twice a week and a personal text message works fine at that scale. The ROI on building out a full dunning sequence only really shows up once you're above 100 active recurring accounts. Below that, just make sure someone is checking the aging report consistently and making personal calls. That alone beats most automated systems at small scale.

Frequently asked questions

How long should I wait before putting an account on service hold?

Seven to ten days after the first failed charge is a reasonable window. You want to give the customer time to respond to automated outreach, but you don't want your tech showing up and delivering a third unpaid service visit. Communicate the hold clearly when you set it, and make it easy for the customer to reinstate service the moment they update their card.

Should I charge a failed payment fee?

Some operators do, typically $5 to $15. It can reduce repeat failures from the same customer, but it can also trigger cancellations. If your plan customers are mostly long-term residential accounts, the relationship usually isn't worth the friction. If you're dealing with commercial accounts that repeatedly have failed payments, a fee is easier to justify and defend.

What if the customer just never updates their card?

After five to seven business days of outreach with no response, call them directly. Some will say "oh sorry, I meant to cancel" and that's fine, at least you stop delivering free services. Others will update immediately. The ones who don't respond to three automated messages and a phone call are effectively already churned. Cut the account loose cleanly, send a final notice, and move on. Chasing a ghost costs real admin time.

Does card-on-file updater work with all processors?

The major ones, including Stripe, Square, and most ISO-based merchant accounts, offer some form of automatic card updating through card network programs run by Visa and Mastercard. It's not always turned on by default. Log into your processor's dashboard and look for "account updater" or "card updater" in the settings. If you can't find it, call your rep. It's usually free or very low cost and it's one of the highest-ROI settings you can enable for any recurring billing business.

// Modules mentioned
💸
AI Invoice Chaser
$99/mo

Want this running in your business?

Book a 30-minute call and we’ll show you exactly what Corex would fix first. Or start your free trial right now, no call needed.

Book a free discovery →Start your free trial →Solutions for pest-control