# Route and callback reporting for pest control operators

Stops come from your routing app, callbacks from the office, revenue from billing. An AI agent assembles them into one route report each week. You decide how it reads; the next refresh keeps it that way.

## The numbers in this report

Your agent maps your own exports to these. Rename anything; the definitions stay the same underneath.

### Completed stops

By route, reconciled to the weekly total.

### Callback rate

Callbacks as a share of stops, broken out by pest type.

### Recurring-plan retention

Recurring-plan customers kept over the trailing 90 days.

### Revenue per route-hour

Which routes earn their windshield time.

A live pest-control report showing completed stops, callback rate and recurring-plan retention by route.

| Completed stops | 154 stops |
| Callback rate | 7.1% |
| Recurring-plan retention | 93.6% |
| Revenue per route-hour | $277 |
| Northgate | 32 |
| Riverside | 29 |
| Eastview | 28 |
| Westfield | 37 |
| Downtown | 28 |
| Ants | 2 |
| Rodents | 4 |
| Termites | 2 |
| Wasps | 1 |
| Mosquitoes | 2 |

## Set it up once. It refreshes every week.

Same product, same three steps, whatever your business measures.

## Bring the report you rebuild every week.

We’ll connect your agent, build the first report with you, and have it refreshing on its own.

We're talking with a handful of pest-control operators before opening this up more broadly. If that's you, we'd like to hear how your route reporting works today.