Lesson 7 of 10 · 8 min

Connect the client's existing tools: calendar and CRM sync, field service software such as Jobber or Housecall Pro

Connect the tools the client already uses, such as calendar and CRM sync, Jobber or Housecall Pro.

Read the lesson

Goal: Decide which tool owns each kind of record, connect what ServiceAgent supports, and bridge the rest without double entry.

You need: A list of the client's current tools. Settings access. The build sheet from lesson 2.

Why this matters

Most clients already use something. A field service app for jobs. A CRM for estimates. A Google Calendar for the owner. They will not throw these away on day 1, and you should not ask them to.

The risk is two systems that both think they own the schedule. Two schedules always drift apart. A tech goes to the wrong house because the office updated one place and not the other.

So this lesson is about decisions first and connections second. Every record type gets one home. Other tools read from it or send to it.

One home for each record

Ask one question for each record type: "Where does the truth live?" Write the answer on the build sheet.

The schedule is the hard one. If the AI books jobs, the schedule must live in ServiceAgent. If the client insists on keeping the schedule elsewhere, the AI can only capture leads. Make that trade-off plain to the owner.

Fig 1

One home for each record

Lives in ServiceAgent
  • Contacts: calls, texts and forms update them
  • Appointments: the AI books here
  • Deals and estimates: follow-up runs here
Stays in the client's tool
  • Job costing, parts, payroll
  • Accounting: there is no QuickBooks integration today
Every record type gets exactly one home. Other tools read from it or send to it.

What connects today

Open Settings → Connections & developer tools → Integrations. The catalog shows:

  • CRM and sales: Zoho CRM, HubSpot, Pipedrive.
  • Automation bridges: Zapier, Make.com.
  • Scheduling: Calendly, Acuity Scheduling.
  • Other: Telegram, Asana, Shopify, and tools through MCP.

Field service tools sit behind the Show beta integrations box. Jobber, ServiceM8, JobNimbus and ServiceTitan are in beta. Beta means test it hard before the client relies on it.

Fig 2

What the Integrations catalog shows

Built for shared workspaces

BrowseZoho CRM, HubSpot, Pipedrive, Zapier, Make.com, Telegram, Calendly, Acuity Scheduling, Asana, Shopify, MCP tools
Show beta integrationsJobber, ServiceM8, JobNimbus, ServiceTitan
ActiveThe connections you made
HealthThe status of each connection
Beta tools need hard tests. Housecall Pro, QuickBooks and Outlook have no card here.

Google Calendar is not in this list. Each team member connects it on their own (lesson 3). An Outlook connection is not available today.

Some tools a client may use have no card here. Housecall Pro and QuickBooks are examples.

For those, look for a bridge through Zapier or Make.com. If no bridge fits, use a regular CSV export and import.

Fig 3

Connect a tool, or bridge it

  1. One tool the client uses
  2. Does it have a card in Integrations?YesConnect it with the client's admin account; run the sync testEnds hereNoLook for a Zapier or Make.com bridge
  3. Does a bridge fit?YesBuild it in the client's own Zapier or Make.comNoUse a regular CSV export and import
  4. Run the sync test both ways
Below Franchise, bridges replace the Webhook Trigger.

The Franchise line

API keys, outbound webhooks and the Webhook Trigger are Franchise features. A client below Franchise does not use the Webhook Trigger. The builder may still show it on a lower plan. Do not rely on it.

For a client on Core or Growth, send outside forms in through Zapier or Make.com. Or replace the outside form with the ServiceAgent booking page or chat widget.

Build it in ServiceAgent

  1. List every tool the client uses. Write what each one holds today.
  2. Fill the "one home" table with the owner. Get a written yes.
  3. Go to Settings → Connections & developer tools → Integrations.
  4. Open the Browse tab. Find each tool that has a card.
  5. For a field service tool, tick Show beta integrations.
  6. Connect one tool at a time. Sign in with the client's admin account for that tool, not yours.
  7. After each connection, open the Health tab. Check its status.
  8. For tools with no card, plan a Zapier or Make.com bridge. Build it in the client's own Zapier or Make.com account.
  9. Check it works. Run the sync test below for each connection.
  10. Write each connection on the build sheet: tool, direction, what syncs, date tested.

The sync test

Every connection gets the same test. Change one thing on each side, then look for it on the other side.

  1. Create a test contact in ServiceAgent. Look for it in the other tool.
  2. Create a different test contact in the other tool. Look for it in ServiceAgent, after a re-sync.
  3. Edit a phone number on one side. Check the other side.
  4. Count both systems' contacts. Write both numbers down.
  5. Delete the test records on both sides.
Fig 4

The sync test

  1. ServiceAgentCreate test contact A
  2. Other toolContact A appears
  3. Other toolCreate test contact B
  4. ServiceAgentContact B appears after re-sync
  5. ServiceAgentEdit a phone, count both sides, delete the tests
Change one thing on each side, then look for it on the other side.

The integrations page says contacts are imported once and updated on re-sync. So a change may not appear at once. Note how long it takes. Tell the office.

If a direction does not sync, write it down. Then decide with the owner who enters that data, and where.

Running cut-over day

Cut-over day is the day the old way stops. Pick a quiet day, such as a Tuesday in a slow month. Avoid Mondays and storm weeks.

The day before, export a fresh copy of every list from the old tool. Import or sync the last changes. Count the records on both sides one more time.

On the morning of cut-over, tell every person in one short message. "From today, all bookings go in ServiceAgent. The old calendar is read only." If the old tool allows it, set staff to read-only access there. People go back to old habits under pressure. Read-only access stops that.

For the first week, check both systems once a day. Look for bookings made in the wrong place. Each one is a training moment, not a blame moment. Move it, and show the person where it belongs.

Keep the old tool's data for at least a year. The owner may need an old invoice or a job note. Do not cancel the old tool until the owner agrees.

Fig 5

Cut-over, from the day before to a year on

  1. Day beforeFresh export, last changes in, count both sides
  2. Cut-over morningOne message to everyone; old tool read only
  3. First weekCheck both systems daily; move strays kindly
  4. One yearKeep the old data; cancel only when the owner agrees
Pick a quiet Tuesday in a slow month. Avoid Mondays and storm weeks.

When the client keeps its own schedule

Some owners will not move the schedule. A roofer may run installs from a project tool that ServiceAgent does not replace. That is fine, if you are clear about what the AI can do.

Without the schedule, the voice agent cannot check real availability. In the agent's Scheduling behavior, pick Capture lead only. The agent takes the details, and a follow-up task goes to the office. The other options are Do not schedule and Book or schedule. The office then books in its own tool.

Tell the owner the cost of this choice in plain words. The caller does not get a time on the call. Some callers will still call the next company. You can revisit the decision after a month, with the answer-rate numbers in hand.

Size changes the plan

An owner-operator often has a phone, a notebook and a Google Calendar. There may be nothing to connect. Moving to ServiceAgent is the whole project.

A fleet usually has a field service tool with payroll and parts. Keep it for those. Move the schedule to ServiceAgent only if the AI will book. Agree one cut-over date. After that date, nobody books in the old tool.

A multi-location business may use different tools at different shops. Connect the shared tools once at the organization level. Then check each location's records reach the right location.

Worked example: Summit Roofing

Summit Roofing has 15 people on Growth. It uses Jobber for jobs and crews. It uses Google Calendar for estimate visits. It uses a spreadsheet for estimate follow-up.

The one-home decisions:

RecordHomeConnection
ContactsServiceAgentJobber beta sync, tested both ways
Estimate visitsServiceAgent calendarEstimators connect Google with Block Google busy times on
Estimate follow-upServiceAgent pipelineThe spreadsheet retires on cut-over day
Roofing jobs and crewsJobberServiceAgent does not book crews for roof installs
AccountingTheir accounting toolNo change

The sync test on Jobber: 10 test contacts made in ServiceAgent reached Jobber, 10 of 10. Of 10 made in Jobber, 9 reached ServiceAgent after re-sync. One had no phone number and was skipped. Result: 19 of 20, or 95%. You write a rule for the office: every Jobber customer needs a phone number. You test again: 20 of 20.

Fig 6Example numbers

Summit Roofing's Jobber sync test

10 of 10ServiceAgent to Jobber
9 of 10Jobber to ServiceAgent, first test
95%First result, 19 of 20
20 of 20After the phone-number rule
Test both directions, fix the cause, then test again.

Common mistakes

  • Two homes for the schedule. Fix: one schedule, one cut-over date.
  • Using your own login in the other tool. Fix: use the client's admin account. Then the link survives if you leave.
  • Trusting a beta link without a test. Fix: run the sync test both ways.
  • Planning on the Webhook Trigger below Franchise. Fix: use Zapier or Make.com, or the booking page.
  • Promising a QuickBooks sync. Fix: say plainly it is not available today.

Do this now

Write a "one home" table for a real or practice client with at least 3 tools. For each tool, mark: has a card, beta, bridge needed, or CSV only. Then run the sync test on one connection in a practice account.

Practice the conversation

  1. Operator You use Jobber, a spreadsheet and Google Calendar. Let's pick one home for each thing.
  2. Owner I like Jobber. I don't want to lose it.
  3. Operator You won't. Jobber keeps crews, parts and job costing.
  4. Owner So what moves?
  5. Operator Estimate visits and follow-up. The AI books those, so they live here.
  6. Owner And the spreadsheet?
  7. Operator It retires on cut-over day. The pipeline replaces it.
  8. Owner Will the two systems talk?
  9. Operator The Jobber link is in beta. I tested it, and I'll show you the result.

Quick check

  1. A Growth client wants web forms from its old site to start a workflow. What do you use?
    • The `Webhook Trigger`, because it shows in the builder
    • Zapier or Make.com, or swap in the booking page or chat widget
    • A QuickBooks sync
    • Nothing; forms cannot reach ServiceAgent
  2. An HVAC fleet keeps a whiteboard schedule and the ServiceAgent calendar. Crews go to the wrong job. What is the fix?
    • Update the whiteboard first, then copy it
    • Give each dispatcher a whiteboard
    • Keep one schedule on the calendar and retire the whiteboard
    • Add every tool as a resource
  3. In a sync test, 18 of 20 test contacts arrive correctly. What do you do?
    • Find why 2 failed, fix the cause, and test again
    • Go live, since 90% is close enough
    • Delete the connection
    • Ask the office to retype missing contacts forever

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community