The Go-Live Checklist
Go through the Go-Live Checklist step by step before you switch on.
Read the lesson
Goal: Run one checklist and five real test calls, then switch the client on only when every check passes.
You need: Lessons 1 to 8 done. The client's carrier access. The Go-Live Checklist Blueprint. About 300 credits for test calls.
Why this matters
Go-live is the moment real customers meet your build. Every gap you missed now costs a real job, a real complaint or a real refund. And the owner's first impression of the AI forms in the first week. A bad first week is hard to undo.
The checklist turns go-live from a feeling into a decision. Either every check passes, or you hold. There is no "close enough". The owner may push to go live with one known problem. That one problem will be the story they tell their friends.
The go-live rule
If one check fails, you do not go live. You fix the cause, test that check again, then switch on.
Holding for a day is cheap. Going live broken is expensive. Say this rule to the owner at kickoff, not on go-live day. Then it is a shared rule, not your excuse.
The go-live rule
- Run checks 1 to 15 in order
- Did every check pass?YesSwitch on carrier forwarding (check 16)NoHold go-live: fix the cause, then test that check againEnds here
- One more real call to the client's number confirms forwarding
The Go-Live Checklist
Run it in this order. Each line has a pass condition. Write the date and your initials next to each one.
Setup:
- Organization, branding, hours and closures set (lesson 1).
- Every bookable person shows in
Assigned To(lesson 1). - Services have real durations and approved prices (lesson 4).
Booking Rulesset: Minimum Notice, Maximum Advance, Buffer Between Appointments (lesson 2).- Two-way calendar test passed for every member (lesson 3).
Agent:
- 20-question test passed at 20 of 20 (lesson 5).
- The client's emergency wording is in, word for word, and
Transfer to your teamhas the right number. - Agent published with
Publish.
Data and tools:
- Import checked: counts match, 10 random contacts correct (lesson 6).
- Each connection passed the sync test (lesson 7).
Messages and money:
- SMS registration approved and a STOP test passed (lesson 8).
- Every workflow passed the builder
Testand is published. Drafts send nothing. - Payments activated, if the package uses them. Activation gives 2,000 bonus credits once.
Auto-reload Creditsset:Billing→Payment settings→Auto-reload Credits. It needs a saved card.
Live calls:
- Five real test calls passed (below).
- Carrier forwarding switched on, then one more call to confirm.
The checklist in five groups
- 1SetupChecks 1 to 5
- 2AgentChecks 6 to 8
- 3Data and toolsChecks 9 and 10
- 4Messages and moneyChecks 11 to 14
- 5Live callsChecks 15 and 16
Plan the day
Go-live day needs three people at the same time: you, the owner, and whoever controls the phone carrier account. Book a two-hour window. Pick a quiet weekday morning, not a Friday afternoon. A Friday go-live leaves nobody watching the first weekend.
Send the owner the plan the day before. It lists the window and the five test calls. It also names the one thing you need from them. That is the carrier login, or a person who can change forwarding. Ask them to keep their phone close, because test call 3 transfers to their team number.
Go-live day
- Day beforeSend the plan, the window and the carrier ask
- Window opensWalk checks 1 to 14 with the owner
- NextFive real test calls; read each transcript
- All passCarrier forwarding on, then one more call
- Same dayGo-live note to the owner
- Next morningAnalytics, Calls: calls are recorded
The five real test calls
Browser tests are free and prove the answers. Real calls prove the phone path too. Make the five calls to the AI number before forwarding is on. Use a phone that is not the office line. Check 16 then proves forwarding with one call to the client's real number.
| Call | What you ask | Pass when |
|---|---|---|
| 1. Business hours booking | A top service, tomorrow | Correct service, real slot, confirmation arrives |
| 2. After hours | Same request at night | Booked or captured as the owner chose |
| 3. Emergency | A case from the owner's list | Owner's safety line, then transfer |
| 4. Price question | A price the owner did not approve | No price given, visit offered |
| 5. Out of area | A town outside the area | Politely declined, no booking |
The built-in booking confirmation goes by email. A confirmation text needs a workflow. Check whichever the client chose.
Use a test name that the office will recognize, such as "Test Caller". Delete or cancel the test bookings after each call. Note the times so the office does not call your fake customer.
Build it in ServiceAgent
- Print or copy the checklist into the client's build sheet.
- Walk through checks 1 to 14 in the app. Mark each pass with date and initials.
- Fix any failed check before you move on.
- Make the five real test calls. Record the result of each.
- Read each test call's transcript in
Voice Agents. - If all five pass, switch on carrier forwarding with the client.
- Make one more call to confirm forwarding works.
- Check
Analytics→Callsthe next morning. Confirm calls are recorded. - Send the owner a short go-live note: what is live and how to reach you.
Worked example: Green Acre Lawn and Landscape
Green Acre has 5 crews on Growth. It is go-live day. Checks 1 to 14 pass.
Real test calls, about 4 minutes each:
- Credits: 5 x 4 x 15 = 300 credits.
Results: calls 1, 2, 3 and 5 pass. Call 4 fails. You asked for a price on a full yard redesign. The agent said "around two thousand". The owner never approved that.
The owner says, "Close enough. Go live, fix it next week." You hold.
The cause: an old brochure in Knowledge sources mentioned a starting price. You remove it. You add a Quick answers entry. It says design work is priced after a free site visit. You retest the price question in Talk in browser, then make one more real call.
Green Acre's failed price call
- Old brochure in Knowledge sources
- Agent says around two thousand
- Call 4 fails
- Brochure removed
- Quick answer: design work is priced after a free site visit
- Browser retest and one real call pass
Extra cost: 1 call x 4 minutes x 15 = 60 credits. Total test cost: 360 credits. At the 500-credit Safe Pack price of $20, that is about $14.40 of credits. Go-live moves by 2 hours, not by a week of wrong prices.
Green Acre's test cost
Common mistakes
- Going live with one known failure. Fix: hold, fix the cause, retest.
- Forgetting to publish workflows. Every workflow is a draft until
Publish. Fix: checkMy Workflowsswitches. - No auto-reload. Credits hit zero on a busy day. Fix: set
Auto-reload Creditswith a saved card. - Leaving test bookings on the calendar. A crew drives to a fake job. Fix: cancel each one right away.
- Forwarding before the tests. Fix: forward last.
Do this now
Copy the 16-line checklist into your build kit. Add a column for date and initials. Run it on your practice account, including at least two real test calls. Record the credits used.
Practice the conversation
- Operator Today we run 16 checks and five real calls. If they all pass, we switch on.
- Owner And if one fails?
- Operator We fix it and test again. Usually that takes an hour or two.
- Owner I'd rather just go live.
- Operator One wrong price on a real call costs more than two hours.
- Owner What did fail?
- Operator It quoted a price you never approved. I found the old brochure that caused it.
- Owner That brochure is three years old.
- Operator It's gone now. One more call, then we switch your phones over.
Quick check
- On go-live day, 4 of 5 test calls pass. The out-of-area caller got booked. The owner says go live and fix it later. What do you do?
- Go live; the office can cancel out-of-area jobs
- Go live, since 80% passed
- Hold go-live, fix the service area, and retest that call
- Publish the voice line but turn off the booking page
- You plan 5 real test calls of 4 minutes and 1 retest of 4 minutes. How many credits?
- 300
- 360
- 240
- 420
- All workflows passed `Test`, but no texts go out after go-live. What is the likely cause?
- The workflows are still drafts and were never published
- `Test` sends real texts, so they already went
- Quiet hours are off
- Core blocks all texts
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.