When should a pest control call outcome count as a booked job?
The short answer
Count a booked job when the scheduling system confirms a booking, not merely when an agent labels a call successful. Keep the call outcome, booking and completed service as separate events so follow up and revenue reporting do not confuse interest with work that was actually scheduled or delivered.
Key points
- A Five9 disposition describes the outcome of an interaction.
- A booking needs its own identifier and confirmed scheduling state.
- A second call about an existing appointment is not a new booking.
- Cancellation and rescheduling must update the existing appointment relationship.
Official references
Why the distinction matters
Five9 defines dispositions as labels or tags assigned to completed customer interactions. That is useful evidence about a call, but it is not by itself evidence of a confirmed appointment in FieldRoutes or another scheduling system. For example, an agent may record interest while a service address is still being checked. This is a workflow design example, not a documented client incident.
Agree on the authority for each event
- Phone system: call identifier, agent and interaction outcome.
- Scheduling system: confirmed appointment identifier, service location and current booking state.
- CRM: associations between the lead, call and appointment, plus the tasks your team needs.
- Operational or accounting system: the agreed evidence of completed service and revenue, which must not be inferred from a call label.
Ask the supplier to demonstrate these handoffs
- 01Record an interested caller without a confirmed appointment. Confirm follow up is created without counting a booking.
- 02Confirm an appointment and link its identifier to the originating call and lead.
- 03Log another call about the same appointment. Confirm the booking total does not increase.
- 04Reschedule and then cancel the appointment. Confirm reminders and booking reports use the latest approved state.
- 05Receive the booking update late. Confirm it attaches to the existing lead rather than creating a second customer or triggering duplicate messages.
Choose the connector by observable behavior
Ask whether the proposed connector exposes appointment identifiers, status changes and record associations for your account. A call log alone may be enough for sales coaching but not for booked job attribution. Require an exception queue for unmatched calls and bookings, with a named reviewer. Do not automatically merge people just because they share a phone number; households and businesses can share numbers.
From our team
How Proven ROI helps
Proven ROI's pest control case study describes connecting HubSpot, FieldRoutes and Five9. That supports the integration context, but the specific status mapping and acceptance scenarios must be agreed for each implementation. No result or conversion uplift is promised here.
Talk to a real personCommon follow up questions
- Can an agent's disposition trigger a sales task?
- Yes, if that is the agreed workflow. Keep the task separate from a confirmed booking count and stop or update it when the scheduling system supplies the next state.
- Should a cancelled appointment disappear from reports?
- Keep the history and report cancellations separately. Define whether a report measures bookings created, current active bookings or completed services so the totals remain interpretable.