FieldRoutes: Connect Your Account

This guide walks you through connecting your FieldRoutes (formerly PestRoutes) office to AutoRev so your AI receptionist can look up returning customers, schedule appointments, and push call summaries into FieldRoutes.

Estimated time: ~10 minutes once FieldRoutes support replies (1-3 business days for the credentials).

Why connect FieldRoutes

• The AI receptionist recognizes returning customers by their phone number — pulls their name, address, and account from FieldRoutes so it can greet them by name and skip re-asking their address.
• New leads get created as Customers in FieldRoutes with a Subscription in lead status, plus an Appointment scheduled on the closest matching route — your office team confirms the slot by callback the same way they do today.
• Every call gets a Note attached to the customer record with the AI's call summary, so the next person who picks up that customer is fully briefed.

Step 1: Request API access from FieldRoutes

FieldRoutes does not let you self-serve API credentials in the dashboard — you have to request them by email.

1. Email support@fieldroutes.com from the email address on your FieldRoutes account.

2. Subject: API access for AutoRev AI

3. Body (copy-paste, swap in your office name):

   Hi FieldRoutes support, please enable API access for the {YOUR OFFICE NAME} office. I'd like to integrate with AutoRev AI (an inbound voice receptionist). Please send back:

   1. Subdomain
   2. Office ID
   3. Authentication Key
   4. Authentication Token

   Thanks!

4. FieldRoutes typically responds within 1-3 business days with all four values.

Step 2: Identify your default service ID

While you wait for the credentials, find the serviceID for the standard service the AI should book when a new caller has a routine pest issue.

1. Log into FieldRoutes.
2. Go to Admin → Preferences → Service Setup.
3. Find your "General Pest Service" (or equivalent — whatever your default quarterly/monthly service is).
4. Note the integer ID in the leftmost column. Common values are 1, 2, 1903, etc. — they vary per office.

Save this number — you'll paste it in during the AutoRev connect step.

Step 3: Connect inside AutoRev

Once FieldRoutes support replies:

1. Log into AutoRev at app.autorev.ai.

2. Go to Settings → Integrations in the left sidebar.

3. Find the FieldRoutes card and paste in:

   Field	Value
   Subdomain	the subdomain FieldRoutes gave you (e.g. mikespest if your login URL is mikespest.pestroutes.com)
   Office ID	the integer Office ID from FieldRoutes (usually 1)
   Authentication Key	the Authentication Key string
   Authentication Token	the Authentication Token string
   Default service ID	the serviceID you noted in Step 2

4. Click Connect FieldRoutes.

AutoRev will probe FieldRoutes to confirm the credentials work. If everything's right, you'll see:

FieldRoutes (Your Office Name): X,XXX customers visible

If you see an error, double-check the four credentials — they're case-sensitive, and there's no whitespace.

Step 4: Test with a real call

Once connected:

1. Pull a real returning customer's phone number from FieldRoutes (any active customer will do).
2. Call your AutoRev phone number from that customer's phone.
3. The AI should greet you by name and reference the account's address.

If the AI says "Got it, what's your name?" instead of greeting you by name, the lookup didn't fire — check Settings → Calls for the call record and the recorded reason.

What the AI does in FieldRoutes after each call

• Returning caller, new appointment. The AI books an Appointment on the closest route to the caller's address. Subscription stays in lead status until your office confirms the slot.
• New caller, new appointment. The AI creates a new Customer record, opens a Subscription in lead status, and schedules an Appointment.
• Every call. Pushes a Note onto the customer record containing the call summary and outcome (booked / interested / unresolved / etc.).

What the AI deliberately does NOT do

• Cancel or reschedule existing appointments. The AI books new ones only — your office handles changes.
• Charge payments. AutoRev never touches FieldRoutes' billing.
• Modify routes, technicians, or pricing. The AI reads your route configuration; it doesn't edit it.

Tuning behavior

Three knobs live in the AutoRev side of the integration (we set sensible defaults on connect; ask support to tune them):

• Lead time. Minimum minutes between "now" and the earliest slot the AI can offer. Default 120 (2 hours).
• Route radius. Maximum distance in miles between the caller's address and a candidate route. Default 30 miles.
• Lookahead. How many days out the AI will search for slots. Default 7 days.

Troubleshooting

Symptom	Likely cause	Fix
"Could not connect to FieldRoutes" on connect	One of the four credentials is wrong / has a typo	Re-paste each field. Subdomain is lowercase letters/numbers only. Office ID is a positive integer.
AI says "got it, what's your name?" for a known customer	Phone number on the customer's FieldRoutes record doesn't match what the caller used	Check phone1/phone2/additionalContact on the customer record. AI searches all three.
AI offers a slot but nothing appears in FieldRoutes	Default service ID not set	Go back to Settings → Integrations → FieldRoutes, disconnect + reconnect with the service ID.
AI can't find any open slots	The route the caller's address falls in has no apiCanSchedule=1 open spots in the next 7 days	In FieldRoutes → Routes, enable apiCanSchedule on the relevant routes, or raise the lookahead.
Booking lands on the wrong route	The closest route doesn't accept API scheduling	In FieldRoutes → Routes → Settings, make sure the route's apiCanSchedule flag is on.

Reconnecting / rotating credentials

If you rotate your Authentication Token in FieldRoutes (or someone leaves the team and you want fresh creds), come back to Settings → Integrations → FieldRoutes, click Disconnect, then connect again with the new values.