Lesson 4 of 7 · 9 min

Client onboarding SOP: kickoff to go-live in 7 days

Follow the onboarding plan from kickoff to go-live in 7 days.

Read the lesson

Goal: Take a signed client from kickoff to a tested, live system in 7 days. End with a clear go or no-go check.

You need: A signed proposal. The Setup Sprint course. The client's price list, hours and emergency wording.

Why this matters

The first week sets the tone for the whole relationship. A fast, calm install tells the owner they chose well. A slow, messy one makes them doubt every invoice after it.

Speed alone is not the goal. The goal is a system that works the first time a real customer calls. If you skip the tests, every gap in hours, prices or rules shows up in front of a real caller. That is why the 7 days end with a strict test day.

A fixed SOP also makes you faster. When every install follows the same days, you stop forgetting steps. Your tenth install takes half the time of your first.

The 7 days

Day 0: Kickoff (90 minutes). Run the Blueprint Workshop from the Setup Sprint course. Invite the owner and the person who books jobs today. Collect the owner's homework list:

  • Approved price list, in writing.
  • Emergency wording, in their own words.
  • Service area, hours and holidays.
  • Team list: who needs a login, who takes transfers.
  • Customer list export for import.
Fig 1

The owner's homework and when you use it

Homework itemWhat you do with itDay
Approved price listThe agent quotes only these prices2
Emergency wording, in their wordsPasted into the agent exactly3
Service area, hours and holidaysBusiness hours, closures, booking rules1 and 2
Team list and transfer numberLogins and Transfer to your team1 and 3
Customer list export20-row test, then the full import5
Missing homework is the main cause of a late go-live. Ask for it at kickoff.

Day 1: Provisioning. Create the organization. Set the users, business hours and holidays. Start the texting registration today, because carrier approval comes before any US texting.

Day 2: Services and knowledge. Add services with real durations. Set booking rules. Load the knowledge sources and quick answers.

Day 3: Voice agent. Build the agent. Add the emergency wording exactly as written. Set the transfer number.

Day 4: Workflows. Build the package workflows as drafts. Test each one with the builder's free Test.

Day 5: Data and calendars. Import customers with a 20-row test file first. Connect each team member's Google Calendar.

Day 6: Test day. Run every test script. Any failed test means no go-live until it is fixed and passes again.

Day 7: Go-live and handover. Forward the line and make a live check call. Then hand over to the owner in 30 minutes.

Fig 2

The 7-day install

  1. Day 0Kickoff and the owner's homework
  2. Day 1Provisioning; start texting registration
  3. Day 2Services, booking rules and knowledge
  4. Day 3Voice agent and their exact emergency words
  5. Day 4Workflows as drafts, each run through Test
  6. Day 5Customer import and Google Calendars
  7. Day 6Test day, then the go or no-go meeting
  8. Day 7Forwarding, live check call, 30-minute handover
Every install follows the same days. Day 6 decides go or no-go.

The go or no-go rules

Day 6 ends with a short meeting, even if it is only you. Read each rule aloud and answer yes or no.

  1. Every test script passed on its last run.
  2. The emergency wording matches the owner's text word for word.
  3. The prices the agent quotes match the approved list.
  4. The transfer number rings a real person who expects it.
  5. Each workflow ran a clean Test and is ready to Publish.
  6. Auto-reload Credits is on, so the agent never runs dry.

One "no" means no go-live. Fix the cause, retest that exact item and meet again. Tell the owner the new date the same day. Owners accept a one-day delay much better than a bad first call.

Fig 3

The day 6 go or no-go meeting

  1. Day 6: run every test script
  2. Fix each failure and retest that exact script
  3. Meeting: read each of the 6 rules aloud
  4. Is every rule a yes?YesGo live on day 7NoNo go-live. Fix, retest, and tell the owner the new date today
One no means no go-live. Owners accept a one-day delay better than a bad first call.

By size

Owner-operator. The install is lighter. There are fewer services, fewer users and a short customer list. You may finish in 4 or 5 days. Keep day 6 as a full test day anyway.

Fleet. The work grows with people. Twenty techs means twenty calendar connections and twenty logins to check. Book a 15-minute slot with each tech, or ask the office manager to help. Plan the import carefully, because fleets often have messy lists from older software.

Multi-location. Install one location first with this exact SOP. Then rebuild it in the next location from your notes. Each location still gets its own day 6 test, because hours, areas and staff differ.

The 30-minute handover

The handover on day 7 covers only what the owner and office will use each week. Show where calls and transcripts live in Conversations and Voice Agents. Show the new jobs on Jobs. Show how to reach you with a change. Leave everything else for the monthly review. A short handover builds confidence. A long tour builds confusion.

Build it in ServiceAgent

Day 1

  1. On the Organisations page (/multi-account), choose Add organisation.
  2. In Settings → Team & Access → Team members & invites, invite the owner. On Core, your login takes the second user seat.
  3. In Settings → Brand & Locations → Business hours, set hours. Add holidays in Closures & Holidays.
  4. Open SMS registration & consent and start registration. Use the generated consent wording on their website.

Day 2

  1. In Settings → Service Catalog → Services, use Create Service for each service: name, duration, price, category and description.
  2. In Booking rules, set Minimum Notice (hours), Maximum Advance (days) and Buffer Between Appointments (minutes).
  3. In Voice Agents → Knowledge, add Knowledge sources and use Add FAQ under Quick answers.

Day 3

  1. On Basics, write the Initial greeting with an AI disclosure. Add hours and after-hours rules to the instructions.
  2. Paste the owner's emergency wording exactly. Do not edit it.
  3. On Actions, turn on Schedule and Transfer to your team with their number.

Day 4

  1. In Workflows, build from Templates or Build with Emma. Every workflow stays a draft until Publish.
  2. Run Test on each. It uses sample data and sends nothing.

Day 5

  1. Import a 20-row CSV test in Contacts. Check the mapping, then import the rest. The limit is 10MB and 10,000 rows.
  2. Each team member connects Google Calendar and turns on Block Google busy times. Test both directions with one event.

Day 6

  1. In Test & publish, run at least 10 Talk in browser tests. Cover after hours, an emergency, an out-of-area caller, a price question and a reschedule.
  2. Fix every failure. Retest that exact script.
  3. Make 2 real calls with Call my phone. These use credits.
Fig 4

Day 6 tests in Test & publish

Test & publish

Talk in browserFree; no record changes. Run 10 or more
Practice conversationTyped test; no call
Call my phoneA real call that uses credits. Make 2
Publish
Do most tests in the browser for free. Save real calls for the final check.

Day 7

  1. Publish the agent and the workflows.
  2. The owner sets carrier no-answer forwarding to the agent's number. Porting takes 1 to 2 weeks through support, so do not wait for it.
  3. Call the business from an outside phone and let it ring out. Confirm the agent answers and books.
  4. Check it works. Confirm the test job is on Jobs, the contact exists and the confirmation arrived.

If texting is not approved by day 7, go live with voice and hold the text workflows. Switch them on the day approval arrives.

Worked example: Polar Air Services

Polar Air has about 20 techs on Growth. You install Business on Autopilot.

Your hours for the week are an example. Day 0 is a 1.5-hour kickoff. Day 1 sets up 20 users in 2 hours. Day 2 adds 14 services and the knowledge in 3 hours. Day 3 builds the voice agent in 3 hours. Day 4 builds 8 workflows in 4 hours. Day 5 imports 3,000 contacts and connects 20 calendars in 3 hours. Day 6 runs 14 tests and 3 fixes in 3.5 hours. Day 7 is go-live and handover in 2 hours. The hours add up to 22. That sits inside the 20 to 25 hours from lesson 2.

Fig 5Example numbers

Polar Air install hours by day

Day 0: kickoff1.5
Day 1: provisioning2
Day 2: services, knowledge3
Day 3: voice agent3
Day 4: 8 workflows4
Day 5: data, calendars3
Day 6: 14 tests, 3 fixes3.5
Day 7: go-live, handover2
22 hours in total for a 20-tech Business on Autopilot install. Test day is one of the longest.

On day 3, the owner asked to forward their main line right away. You said no. On day 6, the out-of-area test call booked a real slot in a town they do not serve. You fixed the service area and retested. A real customer never met that mistake.

Fig 6

The out-of-area test call

First test run
  • Caller from a town Polar Air does not serve
  • Agent books a real slot
  • A tech would drive out for nothing
After the fix
  • Service area corrected
  • Same test script run again
  • Agent says the town is outside the area
The day 6 test found the gap. A real customer never met it.

Common mistakes

  • Forwarding the line early. Real customers meet an untested agent. Fix: forward only after day 6 passes.
  • Starting texting registration late. Texts wait for approval. Fix: start it on day 1.
  • Rewriting the owner's emergency words. Fix: paste them exactly, and test them.
  • Importing the full list first. Fix: test 20 rows, then import the rest.
  • Going live with one failed test. Fix: one fail means no go-live until it passes.

Also call the transfer number yourself on day 6. An emergency must reach a person who picks up.

After each install, note what slowed you down. Add a line to your SOP so the next install avoids it.

Do this now

Copy the 7-day plan into your task tool or calendar as a template. Add the owner's homework list as a checklist for day 0. Time: 20 minutes.

Practice the conversation

  1. Owner It's day 3. Can we forward my line now? I want calls answered.
  2. Operator I want that too. Day 6 is test day.
  3. Owner Why wait?
  4. Operator Tests find gaps in hours, prices and rules. I want to find them, not your customers.
  5. Owner What kind of gaps?
  6. Operator Last week a test caller from outside the area got booked. We fixed it before go-live.
  7. Owner Okay. What do you need from me?
  8. Operator Your approved price list and your emergency wording, by tomorrow.
  9. Owner And day 7 we're live?
  10. Operator Yes, if every test passes. Then 30 minutes to show you how it works.

Quick check

  1. On day 3, the owner asks to forward their main line now. Tests are set for day 6. What do you say?
    • Wait until the day 6 tests pass, and test in the browser until then
    • Forward now, and fix problems as calls come in
    • Forward now, but only during business hours
    • Skip the day 6 tests, since the owner wants to go live
  2. On day 7, carrier approval for texting has not arrived. What do you do?
    • Delay the whole go-live until texting is approved
    • Go live with voice, and switch on text workflows when approval arrives
    • Send texts anyway, since approval is a formality
    • Move the client to Franchise
  3. An install takes 1.5, 2, 2.5, 3, 3, 2, 3 and 1.5 hours over days 0 to 7. At $75 an hour, what setup fee covers it?
    • $1,350
    • $1,388
    • $1,425
    • $1,500

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

Learn

Get certified

Community