Lesson 3 of 10 · 7 min

Connect calendars and phone numbers

Connect each team member's Google Calendar and set up the phone number the AI answers.

Read the lesson

Goal: Connect each team member's calendar, prove the sync both ways, and route the business phone to the AI safely.

You need: Team members invited (lesson 1). Each person's Google account. The client's carrier login or the carrier's support number.

Why this matters

A calendar that syncs one way is worse than no sync. The tech believes their dentist visit blocks the time. The AI believes the slot is open. A customer gets booked, and nobody shows up.

The phone is the front door of the business. Most service businesses miss 14% to 27% of their calls. When a call goes unanswered, the caller usually rings the next company. Routing the phone to the AI closes that leak. Routing it wrong closes the front door instead.

So this lesson has one rule for both parts. Prove it works before real customers touch it.

How calendar sync works here

Each team member connects their own Google Calendar. The connection lives with the person, not with the whole business. There is no company-wide calendar connection.

Two things can happen once a member connects:

  • Export. Jobs booked in ServiceAgent show up in the member's Google Calendar.
  • Blocking. With Block Google busy times on, busy events in Google block that time for bookings. Event titles stay private.

Blocking works on its own, even when export is paused. Check that the option is on for each member. Ask each member which calendar holds family plans. Connect that one, or blocking misses them.

An Outlook connection is not available today. If the client lives in Outlook, plan for it. The member can keep a Google Calendar for work. Or the office can use Block Time for that person's time off.

How the phone reaches the AI

The voice agent answers on a phone number that ServiceAgent provides. The client's own number reaches the agent by call forwarding from the carrier. Cell, landline and VoIP carriers all offer it.

The intended setup is no-answer forwarding. The office phone rings first. If nobody picks up, the carrier forwards the call to the AI number. Staff still answer when they can. The AI catches the rest.

Fig 1

No-answer forwarding

  1. Customer calls the business number
  2. Does someone in the office pick up?YesStaff take the callEnds hereNoCarrier forwards it to the AI number
  3. Voice agent answersBooks, captures or transfers by the owner's rules
  4. Every call is answered
Staff answer when they can, and the AI catches the rest.

Two other paths exist:

  • A new local number. You buy a number with the client's area code. Phone numbers are billed monthly in dollars, not credits.
  • Porting. The client moves the existing number into ServiceAgent. Porting goes through ServiceAgent support. It takes about 1 to 2 weeks, and the number stays active during the move.

Start with forwarding. It is fast, it is easy to undo, and the client keeps full control at the carrier. If the client later wants everything in one place, porting is a second step, not a first one. For a multi-location client, each location's main number forwards to its own AI number. Test each one on its own.

Fig 2

Three ways to route the phone

No-answer forwarding
  • Client keeps the number
  • Set at the carrier in minutes
  • Easy to undo
New local number
  • Search by the client's area code
  • Billed monthly in dollars
  • New number to print and publish
Porting
  • Through ServiceAgent support
  • About 1 to 2 weeks
  • Number stays active during the move
Start with forwarding. Porting is a second step, not a first one.

Build it in ServiceAgent

Calendars:

  1. Ask each member to sign in to ServiceAgent with their own login.
  2. Each member connects Google Calendar from their own availability settings.
  3. Open Team Member Availability for that member. Check that Block Google busy times is on.
  4. Repeat for every bookable member. Note who has not connected.

Phone number:

  1. Go to Settings → Phone numbers. Check the AI number assigned to the voice agent.
  2. If you need a new number, click Add Number. Search by area code. Pick Voice calls or SMS messages for its use.
  3. In the incoming route, check "Who answers incoming calls?" Pick AI assistant for the AI number.
  4. Do not forward the client's line yet. That happens on go-live day (lesson 9).
Fig 3

Buy a local number if you need one

Add Phone Number

Use this number forVoice calls or SMS messages
SearchSearch by digits or area code
Area CodeThe client's area code
Find Any Available Number
Phone numbers bill monthly in dollars, not credits.

Check it works:

  1. Do the two-way calendar test below for each member.
  2. Test the agent with Talk in browser. It is free and does not change customer records.

The two-way calendar test

A connection screen that says "connected" proves nothing about direction. Test both directions.

  1. In the member's Google Calendar, add a test event tomorrow at 10:00 to 11:00. Mark it busy.
  2. In ServiceAgent, try to book that member at 10:00 tomorrow. The slot should be blocked.
  3. In ServiceAgent, book a test job for the member tomorrow at 2:00.
  4. Open the member's Google Calendar. The test job should appear.
  5. Delete both test items. Write the result on the build sheet with the date.

If step 2 fails, blocking is off or the wrong calendar is connected. If step 4 fails, export is off or paused.

Fig 4

The two-way calendar test

  1. Google CalendarAdd a busy test event, 10 to 11 am
  2. ServiceAgentTry to book 10 am: blocked
  3. ServiceAgentBook a test job at 2 pm
  4. Google CalendarTest job appears
  5. ServiceAgentDelete both; write the result and date
A connected screen proves nothing about direction. Test both ways for every member.

Worked example: Rivera Heating and Air

Rivera Heating and Air has 2 people on Core. The owner uses their cell as the business line. Their partner books from a Google Calendar.

Calendar: both connect Google. The owner's test event blocks the slot. The test job reaches their partner's calendar. Both pass.

Phone: the owner sets no-answer forwarding on their cell, through their carrier. The AI picks up when they are on a roof.

Testing cost, before go-live:

  • Browser tests in Talk in browser: 0 credits.
  • Final real-number tests: 5 calls of about 3 minutes.
  • Credits: 5 x 3 x 15 = 225 credits.
Fig 5ServiceAgent pricing

Rivera's real-number test cost

Test calls5
×Minutes each, rounded up3
×Credits a minute15
+Browser tests in Talk in browser0
Credits used225
Browser tests are free, so save real calls for the final check.

Voice minutes round up. A call of 2 minutes 10 seconds counts as 3 minutes, or 45 credits. So keep test calls short and planned. Do most testing in the browser.

Common mistakes

  • Trusting the connection screen. Fix: run the two-way test for every member.
  • Connecting a personal calendar with blocking off. The agent books over family plans. Fix: check Block Google busy times for each person.
  • Forwarding the line on day 1. Real callers meet an untested agent. Fix: forward on go-live day, after the checks pass.
  • Porting first. The client waits 2 weeks for nothing. Fix: forward now, port later if the client wants to.
  • Testing on the real number all week. Credits drain. Fix: test in the browser; save real calls for the final check.

Do this now

Run the two-way test on your own practice account with one Google Calendar. Record both results. Then write the forwarding steps for one carrier your clients use. Keep them in your build kit.

Practice the conversation

  1. Operator I need each of your techs to connect their Google Calendar.
  2. Owner They keep personal stuff in there. Will you see it?
  3. Operator No. Busy times block bookings, but titles and details stay private.
  4. Owner Good. And my phone number? I don't want to lose it.
  5. Operator You keep it. Your phone rings first. If nobody picks up, it forwards to the AI.
  6. Owner And if I hate it?
  7. Operator You turn off forwarding at your carrier. It takes a minute.
  8. Owner When do we switch it on?
  9. Operator On go-live day, after five test calls pass.

Quick check

  1. A tech's Google Calendar shows "connected". How do you prove the sync before go-live?
    • Trust the connection screen
    • Add a busy test event and book a test job, then check both directions
    • Wait for the first week of real bookings
    • Ask the tech to copy their plans into ServiceAgent
  2. An owner wants to keep their number and start this week. Which setup fits?
    • Port the number first, then go live in 2 weeks
    • Buy a new number and print new cards
    • No-answer forwarding from their carrier to the AI number
    • Forward every call to the AI before any tests
  3. You plan 4 real-number test calls of 2 minutes 10 seconds each. How many credits do they use?
    • 120
    • 130
    • 150
    • 180

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

Learn

Get certified

Community