A pest-control call should leave the office with a booked visit, an updated appointment or a clear request for staff. That is the workflow we built for a US family-owned firm, connecting its AI receptionist to FieldRoutes through Retell and n8n.

Across roughly four months, the build handled 250+ inbound calls and booked dozens of service appointments. These historical call-log figures include early testing; a booking means the appointment action succeeded, not that the visit took place.

The useful work happens around the booking. The agent recognises existing customers, checks the service area and applies the firm's scheduling rules before offering a time. Here is how the flow works and what we learned while building it.

The call starts before the caller speaks

When a call arrives, the agent looks up the caller ID in FieldRoutes. If the number matches a customer, it preloads the customer ID, address, city and subscription. The caller does not have to recite any of it.

Then it asks one question: is this about an existing appointment or a new service?

For an existing appointment, the agent gets the customer's appointments. If none match, it asks for the phone number on the account and runs lookup_customer. Once it has the account, the caller can confirm, reschedule or cancel. A fourth request showed up in the logs: callers who had sold the house and wanted billing stopped. That request freezes the subscription in FieldRoutes.

This build matched accounts by phone number. Before adopting that approach, define the checks required to authorise a reschedule, cancellation or account pause: finding the record alone does not establish the caller's authority to change it.

New customers: the checks come before the questions

A new caller goes through the same order every time. The agent asks for the service type: pest, termite, or bee and wasp. Birds and wildlife are referred out. Then a city check, and a caller outside the service area is declined. Then a date. Sundays are closed.

Only then does check_availability run. It returns times that fit the service, not gaps in a calendar. Termite is 7–10am only, and one area starts at 9–11am. An empty Tuesday afternoon is not a termite slot.

Contact details come last. The agent asks for name, address, ZIP, phone and email one at a time, then calls book_appointment, which creates the customer record if the caller is new. The appointment it writes carries the route, technician notes and area. The caller gets one confirmation.

The order has a practical effect. A caller outside the area, or asking for a Sunday, hears that before they give an address and email.

Wording matters as much as the rules. An arrival window is not an arrival minute.

Illustrative example — not a client transcript.

Caller: Could you put me down for the first thing available tomorrow?

AI receptionist: I'll check the available windows for your service.

Caller: So the technician will arrive right at the start?

AI receptionist: It's an arrival window. I can confirm the window returned by the schedule, but I don't have an exact arrival time.

That distinction stops a scheduling assistant from making a dispatch promise.

The route from request to confirmation

Existing appointmentNew serviceEmergencyNoYesYesNoNoYesYesNoCall arrives:caller ID lookedup inFieldRoutes,account detailspreloadedWhat is the callabout?GetappointmentsService type:pest, termite,bee or waspBefore 6pm:transfer to aperson. After6pm: callbacknoteAppointmentmatched?Ask for thephone numberon the accountand runlookup_customerConfirm,reschedule orcancelAction returnedsuccess?Confirm whatactuallychangedTell the caller itis not done andpass it to theofficeInside theservice area andnot a Sunday?Decline, or referbirds and wildlifeoutcheck_availability for that serviceName, address,ZIP, phone,email, one at atimebook_appointmentBookingreturnedsuccess?Oneconfirmation
Flow 1: The route from request to confirmation. A numbered text explanation follows.
  1. Preload the caller from caller ID, then ask whether the call is about an existing appointment or a new service.
  2. For an existing customer, fetch appointments first. If none match, ask for the account phone number and run lookup_customer.
  3. For a new customer, check service type, city and date before check_availability, and collect contact details after it.
  4. Confirm only after the tool returns success. Human transfer runs Monday to Friday, 7am to 6pm.

The diagram shows the control points. The bottom branch, where the tool does not return success, is the one to test on purpose. A failed booking must leave a clear next step for the office, rather than a promise the system has not kept.

Lessons from the build

The right version, the wrong phone line. We published a new version of the agent. The phone number stayed bound to the old version, so callers reached the old tools. Publishing and routing are separate steps. We updated the phone binding and read it back to confirm which version answered the number.

A promise with no tool call. The agent told a caller it would stop their billing without calling any tool, so nothing changed in FieldRoutes. The tool URLs also pointed at an old host. We required the pause tool for that request and checked every tool URL. The confirmation must follow the completed account action.

The preload was not wired. Caller-ID preload was missing, so the appointment lookup received an empty customer ID. We wired the webhook and added lookup_customer. That failure has its own write-up.

A passing test run did not catch the missing caller-ID preload. That is why the real inbound path matters as much as a scripted test conversation.

What reaches the office

Bookings, appointment changes, cancellations and account requests reach the system the office already uses. A confirmed appointment carries the route, technician notes and service area. An unresolved request needs an owner and a clear next action.

That connection is the value of this build: the call can complete an administrative task inside FieldRoutes, with staff handling the exceptions.

What still belongs with the office

Emergencies before 6pm go to a person. After 6pm the agent leaves a callback note. Callers can be transferred to a person Monday to Friday, 7am to 6pm. After each call, an email goes to the office. Birds and wildlife calls are referred out. In this build, these cases belong to people.

The useful question for any reception build is whether the office gets a specific unresolved task, or has to replay the call to find out what the customer wanted.

Where this workflow fits

This approach suits a pest-control firm that wants routine booking and account requests connected to FieldRoutes, with an office team responsible for exceptions. A different scheduling platform needs its own integration and testing.

Bring your service areas, scheduling rules and FieldRoutes process to Custom Voice Agent. We'll map which calls can become completed office tasks.