Lesson 7 of 8 · 6 min

Experiment safely: demo account and safe tests

Practice without risk in a demo account on the free Launch plan, with browser test calls and workflow test runs.

Read the lesson

Goal: Test every change without touching real customers, real money or real records.

You need: Your practice account and the build from lesson 5.

Why this matters

On a live account, one careless change reaches real people. A workflow with no filter can text 900 past customers in a minute. An agent with a wrong price can quote it to every caller that day. A paused agent can miss a whole weekend.

Owners forgive slow work. They rarely forgive a mistake their customers saw. So you build a habit: every change is tested before it goes live, and every live change is watched.

ServiceAgent gives you the tools for this. There is no separate test copy of a client account. Instead, you combine five layers of safety.

Five layers of safety

1. A practice account. Sign up on the free Launch plan for your own practice. Launch has no monthly credits. Buy a 500-credit pack for $20 when you need real AI calls or texts. Launch runs workflows by hand only. To test a switched-on automation, use a Core or higher account.

2. Free tests. Three tests cost nothing and change no records:

  • Practice conversation on the voice agent's Test & publish tab. You type as the caller.
  • Talk in browser on the same tab. You speak as the caller.
  • Test in the workflow builder. It runs a simulation with sample data and sends nothing.

Call my phone is different. It is a real call. It uses 15 credits a minute and can create or change real records.

Fig 1

Free tests and the one real call

Free, changes nothing
  • Practice conversation: you type
  • Talk in browser: you speak
  • Builder Test: a simulation with sample data
Real: uses credits or money
  • Call my phone: 15 credits a minute
  • Can create or change real records
  • A small real payment, then a refund
Run the free tests every time. Save the real call for the final check.

3. Drafts. Every new workflow starts as a draft. Nothing sends until you click Publish. Use Save draft while you work. The voice agent works the same way. Changes reach live calls only after Publish.

4. Switches. Each workflow in My Workflows has an on/off switch. Each voice agent card has Pause. If something goes wrong, switch it off first. Then find the cause.

Fig 2

When a live change goes wrong

  1. A live change misbehaves
  2. Is it a workflow?YesSwitch it off in My WorkflowsNoPause the voice agent card
  3. Find the causeView run history and Audit logs
  4. Fix it, run Test, then PublishAdd a Condition before each message
  5. Watch the next runs
Stop the harm first. Then find the cause, fix it and test again.

5. Filters and records. Add a Condition step before each message. It checks a value and skips contacts that should not get it. After a change, read the run in History → View run history. Each run retries up to 3 times. Audit logs under Settings → Connections & developer tools show who changed what.

Payments have no test mode. To test a payment link, pay a small real amount with your own card. Then refund it in Payments → Refunds.

Write test cases before you test

A test is only as good as the cases you try. Before you test a voice agent, write a short list of calls a real customer would make. Use at least these six:

  1. A simple booking for the main service.
  2. A price question.
  3. A caller outside the service area.
  4. An emergency, in the owner's own words.
  5. A request for a service the business does not offer.
  6. A caller who changes their mind halfway.

Run each case in Practice conversation first. Then run the hardest two in Talk in browser. Write pass or fail next to each one. A case fails if the agent says anything the owner did not approve.

Size changes the rollout

For an owner-operator, a careful single test is often enough. One phone line and one calendar leave few places to break.

For a fleet, tell the office before a change goes live. Staff should know what customers will receive. Make changes early in the week, not before a holiday weekend.

For a multi-location brand, roll out to one location first. Watch it for a week. Then copy the change to the next location. A mistake then reaches one site, not all of them.

Build it in ServiceAgent

Practice the safe rollout on the text workflow from lesson 5. Use a Core or higher account where you can.

  1. Open Workflows → My Workflows. Open your confirmation draft.
  2. Click Add step and pick Condition. Place it before Send SMS.
  3. Set the condition to skip your own test contacts. For example, read contact.email with Contains and your agency's email domain. Send the text only on the path where it does not match.
  4. Click Test. Read the simulated run. Check that the right path runs.
  5. Click Publish. The workflow is now live.
  6. Book one appointment for a test contact with your own phone number.
  7. Open Conversations and check the text arrived as written.
  8. Open the workflow History tab and click View run history. Check the run shows success.
  9. Check it works: run it for one week, and read the run history each day.
Fig 3

Safe rollout of a workflow

  1. 1Save draft
  2. 2Add a ConditionBefore each message
  3. 3TestFree simulation
  4. 4Publish
  5. 5One real testYour own phone
  6. 6View run historyCheck the run succeeded
  7. 7Watch for one week
Every change follows the same path, in the same order.

Worked example: Fresh Start Cleaning

Fresh Start Cleaning has 12 cleaners on Core. The owner wants a thank-you text when a clean is booked. A new Operator builds it fast. The trigger is Appointment Scheduled. The only step is Send SMS. They publish it without a test.

On day one, it texts 4 of their test contacts and 2 staff members who book internal visits. Staff are confused. The owner asks what happened.

The fix takes 10 minutes:

  1. They switch the workflow off in My Workflows.
  2. They add a Condition before Send SMS that skips staff and test contacts.
  3. They run Test with sample data and checks both paths.
  4. They publish again and book one real test.
Fig 4

Fresh Start's thank-you workflow

Before
  • Appointment Scheduled
  • Send SMS to everyone
  • Staff and test contacts get texts
After
  • Appointment Scheduled
  • Condition skips staff and test contacts
  • Send SMS to real customers only
One Condition step stops texts to staff and test contacts.

Now count the cost of the mistake. Six texts at 2 credits, plus 6 runs at 1 credit, used 18 credits. The credits were cheap. The owner's trust was not.

Fig 5ServiceAgent pricing

What the mistake cost in credits

6 texts × 2 credits12
+6 runs × 1 credit6
Credits used18
The credits were cheap. The owner's trust was not.

One more check matters on Core. The thank-you workflow is a new active automation. Core allows 10. If the account already runs 10, they must switch one off or move the client to Growth.

Common mistakes

  • Publishing before Test. The simulation is free. Run it every time.
  • Testing on real customers. Use your own phone and email as test contacts.
  • Fixing a live problem while it still runs. Switch it off first. Then fix it.
  • Forgetting the Core limit. Each switched-on workflow counts as 1 of 10.

Do this now

Write your personal safety checklist on one page. Include the five layers and the 9 rollout steps. Use it for every change you make in a client account this year.

Practice the conversation

  1. Owner Can you just switch it on today? I trust you.
  2. Operator Thanks. I'll still test it first. It takes a day.
  3. Owner Why the wait?
  4. Operator A mistake here reaches your customers, not me. I test with my own phone first.
  5. Owner What if something still goes wrong?
  6. Operator I switch it off in one click. Then I fix the cause and tell you what happened.
  7. Owner Fair enough.

Quick check

  1. A new workflow texted your test contacts and two staff members on day one. What did it miss?
    • A `Condition` before the first message, to skip the wrong contacts
    • A longer `Delay` before the text
    • A second trigger
    • An AI step before the text
  2. Which of these is a real call that uses credits?
    • `Practice conversation`
    • `Talk in browser`
    • `Call my phone`
    • The workflow builder `Test`
  3. A live workflow is sending the wrong text right now. What do you do first?
    • Edit the text while it keeps running
    • Switch it off in `My Workflows`
    • Delete the contacts who got it
    • Wait for the monthly review

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

Learn

Get certified

Community