Connect external systems so you can pull contacts and data into Tradework Labs.
Pull existing customers, their subscriptions, and recurring revenue data directly from FieldRoutes.
FieldRoutes refuses to book, move, or reassign a visit on a route whose Allow API scheduling setting is off, and most routes ship that way. The clean fix is to turn that setting on for the route in FieldRoutes, which also keeps FieldRoutes' own screens honest about what's bookable. If you'd rather not touch it, switch this on and we'll override the check on every booking, reschedule, and reassignment we send — each one is noted on the customer's timeline so there's an answer later to "how did this land on that route?".
When we create a customer in FieldRoutes for one of your leads, we can tag it with one of your own Customer Sources (Admin → Preferences → Customer References → Customer Sources), so you can tell at a glance in FieldRoutes which customers came from Tradework Labs. Leaving this unset changes nothing — we'll still create the customer, just without a source.
FieldRoutes answered, but this account has no Customer Sources set up yet. Add one in FieldRoutes under Admin → Preferences → Customer References, then reload this page.
FieldRoutes answered with no Customer Sources at all, so the one saved here () no longer exists over there. Choose “Don't stamp a source” to stop sending it, or add the source back in FieldRoutes under Admin → Preferences → Customer References.
We couldn't load your Customer Sources from FieldRoutes, so there's nothing to choose from right now — this isn't the same as your account having none.
Cutting over pulls this tenant's FieldRoutes book one final time, then makes our calendar the one that answers every booking, reschedule and slot lookup. FieldRoutes stays connected for customer history and stops being pulled. Reversible from here.
This tenant schedules on our calendar. The FieldRoutes book is no longer pulled, and nothing we book is written to FieldRoutes. Rolling back hands the calendar back to FieldRoutes; visits booked here in the meantime stay on the schedule but are not pushed across.
Not ready: no technicians are available for scheduling no available technician has working hours set, so our calendar could not offer a single time slot. Set that up on Technicians first.
FieldRoutes is not connected, so there is nothing to roll back to. Reconnect it above first.
Saved to this account's scheduling settings — the same field as on Technicians.
Saved as this account's scheduling timezone.
Pull contacts from a GoHighLevel location using a Private Integration Token. Contacts with matching phone numbers enrich existing records rather than creating duplicates.
Pull your RingCentral call log into the Calls dashboard, so missed calls and callbacks from your business line show up next to your AI-handled calls. Read-only — we never place or change calls.
Send and receive text messages with your contacts. Numbers are provisioned by Tradework Labs after your 10DLC registration is approved.
An AI assistant answers your inbound calls, captures the lead, and notifies your team. Voice numbers are provisioned by Tradework Labs.
Send emails to your contacts from your own domain (e.g. [email protected]) with DKIM authentication so your messages don't get flagged as spam.
Paste the values from your FieldRoutes account. Base URL looks like https://yourcompany.fieldroutes.com.
Generate a Private Integration Token in GoHighLevel under Settings → Private Integrations. The token should start with pit-. Find your Location ID in Settings → Business Profile.
Create an app in the RingCentral developer console with the JWT auth flow and the Read Call Log + Read Accounts scopes. Copy the Client ID and Client Secret from the app's Credentials tab, then mint a JWT credential scoped to that app.