Independent work sample, built for one real business

Mission Pest Control: the moment a cancellation email lands, billing should see it too

Mission Pest Control's own public BBB complaint file shows the same shape repeated across several separate cases spanning late 2023 through late 2025: a customer emails or calls to cancel, the request is acknowledged in writing or logged with an account manager, and the account is billed again the following month anyway. This example shows a small tool that gives every cancellation request a timestamped receipt the moment it comes in, and automatically raises a billing hold until someone confirms the account is actually closed.

Mission Pest Control San Diego, CA, serving 6 SoCal cities Locally owned, 12+ years Runs FieldRoutes (mission.pestportals.com)

Independent work sample, not affiliated with or endorsed by Mission Pest Control. All customer names, service records, and event data inside the tool below are fictional and clearly for illustration only. The business description is drawn from the company's own published site (missionpestcontrol.com). The complaint pattern referenced here is drawn from Mission Pest Control's public BBB complaint file.

Of the complaints published on Mission Pest Control's BBB profile, several independently describe the same mechanism: a cancellation request goes in by email or phone, an account manager acknowledges it or promises to process it, and the card gets charged again the following billing cycle regardless. Dated examples include a customer cancelled by email in October 2025 whose card was still charged the next month; a customer who cancelled in December 2024 but kept being billed until May 2025 despite repeated promises from an account manager; and a customer who cancelled in September 2023 and was still being charged four months later, with calls to the account manager going to voicemail. Mission already runs a FieldRoutes customer portal (confirmed live at mission.pestportals.com), so the account infrastructure exists, what's missing is a receipt that a cancellation request was actually received and a hold that stops the next charge until someone confirms it. This tool is scoped narrowly to that acknowledgment gap, not the phone-based retention conversation itself, which may be a deliberate save step this pitch isn't targeting.

Log a cancellation request or completed visit

Recent events, newest first

Active billing holds

Every logged cancellation request automatically raises a hold here, exactly the step missing in the BBB complaints above: nothing in the current process stops the next charge until a person notices and manually intervenes.

Search the event log

Try Sample Customer A, Sample Customer B or Sample Customer C from the field log's sample events. This search directly answers the "we cancelled but kept getting charged" pattern: the receipt exists the moment the request is logged, instead of depending on a callback that a BBB complaint says never came.

How this gets built for real

This bridges the front office to FieldRoutes, it doesn't replace it. Mission already runs FieldRoutes for scheduling and account management; a real build would push one signal, a cancellation request was received, into the existing portal so billing sees it the same day.
The receipt is the whole point, not the retention step. This deliberately stays out of the phone-based save conversation an account manager may run, it only guarantees a written cancellation request gets an instant, logged acknowledgment.
Clearing a hold stays a deliberate billing decision. The tool raises the flag the instant a cancellation is logged; a person in billing still confirms and clears it, the same way the BBB complaints were ultimately resolved by a person, months later than they should have been.
Back to the general template: Equipment pickup-to-billing-hold tracker.