Connecting FieldRoutes to Smarter Launch keeps your two systems in step, so your team doesn't have to key the same information into both.

Once connected, the integration works in both directions. Smarter Launch imports your offices, team members, and customers from FieldRoutes so you can build proposals against real customer records. It also pushes back to FieldRoutes — creating new customers, attaching signed proposals and documents to the customer's profile, adding notes, and raising tasks and alerts for your office staff.

Most of this is optional and off by default. You choose which pieces to turn on from your integration settings, so you can start with a read-only import and enable the push features as you go.

This article covers what the integration does, how to configure it, and how to troubleshoot the issues we see most often.

If reporting is enabled, FieldRoutes data feeds two Smarter Launch reports: Hourly Rate and Employee Commission.

This distinction is the single most common source of confusion, so it's worth being precise.

On a schedule, Smarter Launch imports only customers who have an appointment scheduled in the next two days.

This is deliberate. It keeps your day-to-day working set current without pulling your entire customer base through the API — which would exhaust your FieldRoutes API allowance on most accounts.

This means the scheduled import will not bring over your whole customer list, and that's expected. A customer with no upcoming appointment will not appear this way. To get any other customer, use the search below.

To pull in a specific customer — regardless of whether they have an appointment — search FieldRoutes directly from Smarter Launch and import them on the spot.

You can search by:

Searches are scoped to the office(s) tied to your Company Location, and return up to 100 matches. Pick the customer and Smarter Launch imports that record immediately, with their contacts and addresses.

If a customer isn't in Smarter Launch, search for them — don't wait for the scheduled import to find them.

You can also press Sync Now on an already-imported customer to refresh that single record from FieldRoutes on demand.

Understanding the shape of the sync makes most problems easier to diagnose.

If you are looking at FieldRoutes API traffic that runs continuously around the clock, or at a steady requests-per-second rate, that pattern does not match how Smarter Launch works. See Why is something using all of my API requests? below.

All of these live in your FieldRoutes integration settings in Smarter Launch. Everything except the credentials is optional and off by default.

If you're unsure which to enable, a good starting point is credentials plus customer search, then add document push once proposals are flowing.

Smarter Launch can create tasks and alerts on a FieldRoutes customer account — useful for telling your office team that a proposal was accepted, or flagging an account that needs attention.

These are typically driven by automations — for example, raising an alert when a proposal is accepted so someone schedules the first service. Talk to our support team if you'd like help setting one up.

Your FieldRoutes account will automatically integrate with Smarter Launch as long as you have only one Company Location defined within Smarter Launch and one office within FieldRoutes.

If your FieldRoutes account has multiple locations, any office you want to integrate into Smarter Launch must match the Company Location name exactly.

For example, if one of your offices is named "Smarter Launch Pest Control," your Company Location name in Smarter Launch must be the same.

If you have multiple locations in Smarter Launch or multiple offices in FieldRoutes, Smarter Launch cannot determine how to map them unless the names match.

FieldRoutes issues API credentials at the account level, and many companies use the same key for every tool they have connected — Smarter Launch, a marketing platform, a reporting or BI tool, a dialer, a custom script, and so on.

This matters because your API quota is shared across all of them. Every tool draws from the same daily allowance. It also means FieldRoutes' usage reporting shows the combined total for the key, not a per-vendor breakdown — so when usage spikes, the reports alone cannot tell you which tool caused it.

Where possible, we recommend issuing a separate API key per vendor. It costs nothing, and it means quota problems are immediately attributable to one tool instead of requiring an investigation. It also means one misbehaving integration cannot exhaust the allowance that your other integrations — including Smarter Launch — depend on.

There are several possible reasons, listed from most to least common:

Use customer search — search by name, address, phone, email, or FieldRoutes customer ID and import them directly. This works for any customer, whether or not they have an upcoming appointment.

This is one of the most common issues we help with, and it is worth saying plainly: in our experience, the cause is usually another tool sharing the same API key — not because other vendors are careless, but simply because a shared key pools everyone's usage into one number, and the tool that spikes is rarely the tool that gets noticed first.

FieldRoutes accounts have a daily read limit that varies by access level — commonly 50 reads per day on Standard and around 3,000 on Premium. A single busy integration polling on a short loop can consume that in minutes, and every other tool on the key then starts failing.

Because Smarter Launch stops before exhausting your quota, a sudden inability to import often means something else already spent it.

How to identify the source:

A real example. A customer's usage went from roughly 200 requests per day to over 20,000 overnight and stayed there, exhausting their daily read limit. The initial hypothesis was that Smarter Launch had begun fetching customers one record at a time. We reviewed our integration and deployment history and confirmed it wasn't us: we fetch in batches of 500 and sync on a schedule measured in hours, so producing that volume was not architecturally possible, and nothing on our side had changed on that date. The traffic was continuous at about 2 requests per second — a shape our scheduled sync never produces. Requesting the source IPs from FieldRoutes was what identified the actual tool. If you are in this situation, start with step 1 — it resolves these cases fastest.

By default, once per day. The frequency is configurable in your integration settings, with a minimum interval of every 2 hours. You can also restrict syncing to your business hours.

If your FieldRoutes account is on a Standard API access level (a low daily read limit), Smarter Launch automatically spaces out larger imports to avoid exhausting your quota in a single run. This means a large first-time import may take longer to complete — this is expected, and the import will continue on its own.

Customer search and Sync Now are on demand and run immediately — you don't need to wait for the schedule.

Check that the relevant setting is enabled — document push is off by default, and there are separate settings for attaching when a proposal is sent versus when it is accepted. Also confirm the customer exists in FieldRoutes: if they were created in Smarter Launch and never pushed, there's no profile to attach to.

Yes. Contact FieldRoutes to ask about a higher API access level. If you are on Standard and importing a large customer base, this is often worthwhile.

Before upgrading, it is worth checking whether the quota is actually being consumed by an unexpected tool — see Why is something using all of my API requests? above. Upgrading solves a genuine capacity problem, but it will not fix a runaway integration; it only raises the ceiling it eventually hits.

If you are unsure whether the problem is on the Smarter Launch side, reach out to our support team. We can check our sync logs for your account, confirm whether our imports are running or being blocked, provide our egress IP addresses so FieldRoutes can identify our traffic, and review our deployment history against any date where your usage changed.