FieldRoutes vs PestPac is less about routing and billing, which both do well, and more about which platform will give you clean answers to the two questions a pest control marketer needs: which lead source produced accounts that converted from initial service to a recurring plan, and which source produced accounts that cancelled. PestPac, from WorkWave, is the long-standing incumbent with the deepest configuration. FieldRoutes, now owned by ServiceTitan, is newer, cloud-first, and ships with a customer portal and sales tooling. This guide explains what each is, what the recurring model demands of your CRM, how lead source has to be captured, and the marketing-side checklist we run on either platform for pest control companies.
What each platform is.
A pest control operating system is the software that holds customer accounts, service agreements, routes, technician schedules and billing in one place, and both of these qualify. PestPac has been the default for larger and older operators for a long time. It is configurable to an unusual depth: service types, agreement structures, pricing rules, renewal logic, taxes by jurisdiction and reporting can all be shaped to a specific company's way of working. That depth is why multi-branch operators run on it, and it is also why implementations take longer and why a company usually needs someone who owns the configuration.
FieldRoutes was built cloud-first and grew with residential-focused operators. Its customer portal lets accounts see service history, pay invoices and request service; its sales tooling covers door-to-door and phone sales with lead tracking and commission reporting; and its interface is easier to learn for an office that turns over staff. ServiceTitan's ownership matters for the roadmap: expect deeper ties into the ServiceTitan ecosystem, including its marketing and payments layers, over time. Neither publishes stable pricing worth quoting, and both price by plan and scale, so we will not put numbers here.
The recurring plan economics your CRM must track.
Pest control is unusual among home services because the first job is often not the profitable one. An initial service at a promotional price is the cost of acquiring a recurring agreement, and the value of a lead is the sum of what the account pays over the months it stays. That changes what attribution means. A source that produces cheap initial services that never convert to a plan is a bad source, however good its cost per lead looks. A source that produces fewer, pricier initials that convert and stay for years is the one to fund.
So the CRM has to carry three things per account and make them reportable by lead source: whether the initial service converted to a recurring agreement, how long the agreement stayed active, and if it cancelled, why. Both platforms can hold all three. PestPac does it through its agreement and cancellation reason configuration, which you must set up deliberately. FieldRoutes does it through subscription status and a cancellation reason list, with reporting that is easier to reach out of the box. On either, the cancellation reason is the field most often left as a free-text box, and a free-text box cannot be reported on. Make it a required pick list: moved, price, service quality, competitor, seasonal, no longer needed.
Lead source must be a required field.
Every account in either system should carry a lead source, and the field should be required at account creation: not optional, not defaulted to Other. Where the lead arrived through a web form or a tracked phone number, the source should already be set before a person touches the record. Where the lead is a walk-in, a door knock or a call to the main line, the office asks and picks from the same list the web form uses.
Keep the list short and aligned to what you pay for: Google Ads, Local Services Ads, Organic search, Business Profile, Referral, Door to door, Direct mail, Yard sign, Repeat. If a source cannot be tied to a budget line or a rep, it should not be on the list. Both platforms let you add custom source values, PestPac through its lookup tables and FieldRoutes through its lead source settings. The value should also flow to the agreement, so that revenue reports by source include recurring revenue, not just the initial.
Web forms and call tracking.
Both platforms offer APIs or integration partners for web forms and call tracking, and both have changed what is available by plan over the years, so confirm current API access on your plan before you design around it. The pattern is the same regardless of who does the work.
For forms, the website form posts to an endpoint that creates a lead or a new customer with the source set from the landing page and UTM parameters, and the Google click id stored on the record. On FieldRoutes that is usually its API or a Zapier connection. On PestPac it is WorkWave's API, an integration partner, or a lead capture form that writes into the system. If neither is available on your plan, the fallback is a form that emails the office with the source in the subject line and a required source field in the CRM, which is worse but honest.
For calls, use a tracking number per campaign through CallRail or a similar tool, and forward all of them to the main line. The office sees the source on the call screen and picks it in the CRM. Where the call tracking tool integrates with the platform, the call record can be attached to the customer automatically. Never place a tracking number on the Google Business Profile as the primary line; use the verified main number there and treat profile calls as their own source.
The marketing-side checklist we run on either platform.
Reviews and seasonal campaigns in practice.
Reviews matter more in pest control than in most trades because the service is invisible when it works. The customer sees a technician, a treatment, and then nothing, which is the point, and a review request immediately after that first service captures the relief. Both platforms can send the request when the technician closes the stop. Point it to the Google Business Profile, not a third-party review site, and reply to every review from the profile.
Seasonal campaigns are where the pest vertical rewards a CRM that knows what each account has. A mosquito upsell to every existing quarterly account in April, a termite inspection offer to accounts without a termite agreement, a rodent exclusion campaign to accounts in the neighborhoods that had calls last winter. On FieldRoutes that segmentation is reachable from its marketing and customer features; on PestPac it is reachable through reporting and an export to your email tool. Either way, existing accounts are the cheapest leads you have. For the acquisition side, see our guide on getting pest control leads.
| Area | PestPac (WorkWave) | FieldRoutes (ServiceTitan) | What it means for marketing |
|---|---|---|---|
| Heritage and fit | Long-standing incumbent, multi-branch and complex operators | Newer, cloud-first, strong with residential growth operators | Both can run a marketing program; office capacity differs |
| Configuration depth | Very deep, needs an owner | Simpler, faster to learn | Deep config makes reporting flexible but slower to set up |
| Customer portal | Available, less central | Built in and central | Portal drives self-serve payments and service requests |
| Sales tooling | Through reporting and add-ons | Built-in lead tracking and commission reporting | FieldRoutes is stronger for door-to-door programs |
| Lead source handling | Custom lookup values, must be enforced | Lead source settings, must be enforced | Required field on both |
| Web form and call tracking | API and integration partners, confirm by plan | API, Zapier and partners, confirm by plan | Confirm current API access before designing |
| Recurring conversion reporting | Configurable agreement reporting | Subscription status reporting out of the box | Both can produce it; FieldRoutes reaches it faster |
| Best fit | Established operators with complex agreements and branches | Growing residential operators who want portal and sales tools | Choose by operation, then wire marketing the same way |
“In pest control the initial service is the price of the relationship. Judge every lead source by how many relationships it starts, not how many initials it sells.”
Mistakes that break pest control attribution.
- Lead source left optional, so a large share of accounts sit under blank or Other and the source report is unusable.
- Cancellation reason kept as a free-text box, which cannot be reported on and hides that a specific source produces accounts that leave over price.
- Reporting cost per initial instead of cost per recurring agreement, which rewards the cheapest, worst-converting channel.
- One Google Ads campaign for all pests year round, so seasonal demand for termites, mosquitoes and rodents is never measured or funded separately.
- Tracking numbers on the Business Profile primary line and on printed materials that get reassigned when the call tracking contract changes.
- Review requests pointed at a third-party site instead of the Google Business Profile that actually drives local ranking.
Is FieldRoutes owned by ServiceTitan?
Yes. FieldRoutes was acquired by ServiceTitan and operates as its pest control platform. For a buyer that means the roadmap will increasingly connect to the ServiceTitan ecosystem, including payments and marketing tooling, while the product keeps its pest-specific routing, recurring agreements and customer portal. PestPac remains part of WorkWave and is developed independently.
Which is better for a small pest control company, FieldRoutes or PestPac?
For a growing residential operator with one or two branches, FieldRoutes is usually faster to set up, easier for new office staff, and quicker to get lead source and recurring conversion reports out of. PestPac rewards an operator with complex agreements, many branches or specific pricing rules and someone who will own the configuration. Marketing works on both once lead source is required and the web form is wired.
Does PestPac or FieldRoutes have an API?
Both offer APIs or integration partners for web forms, call tracking and reporting, and both have changed what is included by plan. Confirm current API access on your plan with your account rep before designing an integration. Where direct API access is not included, Zapier connections, partner integrations or a structured email-to-lead fallback can still get source data into the record.
How should a pest control company track lead source?
Make lead source a required field at account creation, use a short list that matches your budget lines, and set it automatically from the web form and tracking number wherever possible. Carry the source to the agreement so recurring revenue reports by source, and record cancellation reasons from a pick list. Then report initial-to-recurring conversion and cancellations by source every month.