Lesson 5 of 8 · 12 min

Your first build: answer, book and confirm one call

Build your first flow: the AI answers a call and books the job, and a workflow texts a confirmation.

Read the lesson

Goal: Build and test one complete flow: the AI answers a call, books the job and confirms it.

You need: Your practice account. A 500-credit pack ($20) for the one real test call. Lessons 3 and 4.

Why this matters

Reading about ServiceAgent is not the same as building with it. This lesson gives you one small, complete win. A caller asks for a job. The AI answers, finds a free time, books it and confirms it. That one flow touches Catch, Book and Run.

This same flow is the heart of the Never Miss a Job package. Once you can build it in your practice account, you can build it for a client. Later courses add depth to each step. Here, you learn the shape of the whole thing.

You also learn the habit that matters most: test, read the transcript, fix the cause, test again.

What you will build

The flow has five parts:

  1. Business basics. Hours and one service, so the AI knows what it can book.
  2. The voice agent. A greeting and instructions in plain words.
  3. Knowledge. Three short answers the AI can give.
  4. Actions. Permission to look up callers and book appointments.
  5. Confirmation. The built-in email confirmation, plus a text confirmation from a workflow.
Fig 1

One call, answered, booked and confirmed

  1. CallerCalls and asks for a drain clearing
  2. AI voice agentGreets as a virtual assistant, checks the calendar, books
  3. ServiceAgentJob lands in Jobs; email confirmation goes out
  4. WorkflowAppointment Scheduled fires Send SMS
  5. CallerGets the text confirmation
One call touches Catch, Book and Run. The text needs a workflow; the email is built in.

Two plan facts shape this build. First, Launch includes no monthly credits. Practice conversations and browser calls are free. A real phone call uses 15 credits a minute, so buy the 500-credit pack before that step. Second, Launch runs manual workflows only. You can build and simulate the text confirmation on Launch. It only sends by itself on Core or higher.

Texting customers in the US also needs carrier approval first, in SMS registration & consent. The Setup Sprint covers it. For practice, you simulate the text instead of sending it.

Build it in ServiceAgent

Use a practice copy of Northside Plumbing. Make up the details, and label them "practice".

Part A: business basics

  1. Open Settings → Brand & Locations → Business hours. Set Monday to Friday, 8 am to 5 pm.
  2. Open Settings → Service Catalog → Services. Click Create Service.
  3. Enter the name "Drain clearing", a duration of 60 minutes and a practice price. Add a category and a one-line description.
  4. Open Booking rules. In Calendar Configurations, set Minimum Notice (hours) to 2. Set Buffer Between Appointments (minutes) to 15 for drive time.

Part B: the voice agent

  1. Open Voice Agents and create a new agent. You can start from Use template if one fits.
  2. On the Basics tab, set Agent name and Language to English (US).
  3. Write the Initial greeting. Say it is an AI assistant. For example: "Thanks for calling Northside Plumbing. I'm the virtual assistant. How can I help?"
  4. Write the voice instructions in plain words. Tell the agent its job: answer questions, book drain clearings, and take a message for anything else.
  5. Open Call handling & business hours. Set the agent to answer at all hours for this practice build.

Part C: knowledge

  1. Open the Knowledge tab. Under Quick answers, click Add FAQ.
  2. Add three answers: your service area, your hours, and how prices are given. For prices, write: "The technician confirms the price on site before any work starts."

Part D: actions

  1. Open the Actions tab. Under Allowed actions, switch on Recognize returning callers and Save the caller as a new lead.
  2. Switch on Schedule, so the agent can check availability and book live.
  3. Click Publish. The agent now uses these settings on live calls.
Fig 2

Let the agent look up callers and book

Allowed actions

Recognize returning callersOn
Save the caller as a new leadOn
ScheduleOn: check availability and book live
Publish
Switch on these actions, then publish. Nothing reaches live calls before Publish.

Part E: confirmation

  1. The agent sends a booking confirmation by email by itself. Check that your test contact has an email address.
  2. For a text, open Workflows → Create → Build from scratch.
  3. Set Trigger Type to Event Trigger and pick Appointment Scheduled.
  4. Click Add step and pick Send SMS. Write a message under 160 characters. Add the appointment date and time fields.
  5. Click Test. This runs a free simulation with sample data. It sends nothing.
  6. Click Save draft. On a Core or higher account with texting approved, you would click Publish.
Fig 3

The text confirmation from the workflow

  1. noteAppointment Scheduled: Thursday, 10:00 am
  2. Northside Plumbing (practice) · 9:14 amNorthside Plumbing: your drain clearing is booked for Thu at 10:00 am. Reply here with any questions.
  3. Customer · 9:20 amThanks. Side gate is open.
Keep it under 160 plain characters, so it stays 1 segment.

Part F: test in three steps

  1. On Test & publish, use Practice conversation. Ask for a weekday slot inside business hours first. Type as a caller who wants a drain cleared on Thursday. This is free and changes no records.
  2. Use Talk in browser. Speak the same request out loud. This is also free and changes no records.
  3. When both pass, use Call my phone once. This is a real call. It uses credits and creates real records. If it asks for a number, use Manage or buy numbers on the same tab. Numbers bill monthly in dollars, not credits.
  4. Check it works. Open Jobs and find the new appointment. Open Contacts, open the caller, and read the Activity tab. Read the call transcript from start to end.
Fig 4

Three ways to test

Practice conversation
  • Free
  • You type as the caller
  • Changes no records
Talk in browser
  • Free
  • You speak as the caller
  • Changes no records
Call my phone
  • 15 credits a minute, rounded up
  • A real call
  • Creates or updates real records
Test free first. Make one real call only when both free tests pass.

Read the transcript like an auditor

The booking showing up is not enough. Read every line of the transcript. Ask four questions:

  • Did the agent say it was an AI assistant in the greeting?
  • Did it name the right service and the right time?
  • Did it say anything about price that the owner did not approve?
  • Did it end the call politely, with a clear next step?

When something is wrong, fix the cause in the setup. Do not just note it. Then call again to prove the fix works. Keep each transcript you review in your build log. Over time, the log shows which fixes worked.

Fig 5

Read the transcript like an auditor

  1. Read every line of the transcript
  2. Did the greeting say it is an AI assistant?YesNext questionNoFix the Initial greeting
  3. Right service and right time?YesNext questionNoFix the service description or Quick answers
  4. Any price the owner did not approve?YesFix the voice instructions and Quick answersNoNext question
  5. Polite end with a clear next step?YesPassNoFix the voice instructions
  6. After any fix: Publish, then call again
Fix the cause in the setup, publish, then call again to prove the fix.

Worked example: the wrong service name

You run the build for practice Northside. On Call my phone, you ask for a drain clearing. The booking appears in Jobs. But the transcript shows the agent called it a "pipe repair" twice.

You trace the cause. Your Create Service description said "clears blocked drains and pipe repairs". The agent picked the wrong words from it.

You fix two things. You change the service description to "Clears blocked sink, tub and floor drains". You add a Quick answers entry: "Drain clearing is our service for blocked drains." You click Publish again. Then you repeat the browser test, and one more real call.

Fig 6

Fixing the wrong service name

Before
  • Description: clears blocked drains and pipe repairs
  • Agent says pipe repair twice
After
  • Description: clears blocked sink, tub and floor drains
  • Quick answer: drain clearing is our service for blocked drains
  • Publish, browser test, one real call
The agent copied words from the description. Fix the words it reads.

Now count the credits. The first real call lasted 2 minutes 10 seconds. Voice minutes round up, so it bills as 3 minutes. 3 × 15 = 45 credits. The second call bills 2 minutes: 30 credits. Practice conversations and browser calls cost nothing. The real calls used 45 + 30 = 75 credits. Your 500-credit pack has 425 left for more practice.

Fig 7ServiceAgent pricing

Credits for the practice build

Real call 1: 2 min 10 s, billed 3 min × 1545
+Real call 2: 2 min × 1530
+Practice conversations and browser calls0
Used of 500; 425 left75 credits
A full practice build uses a small part of one $20 pack.

On a client account, the live text workflow adds 3 credits per booking. That is 2 for a 1-segment text and 1 for the run.

From practice to a client account

The client build follows the same five parts. A few things change.

The phone line. The client keeps the number customers already know. The intended setup is carrier no-answer forwarding. The client's phone rings first. Calls nobody picks up forward to the AI number. Some clients send all calls to the AI instead. To move a number fully, porting goes through ServiceAgent support. It takes about 1 to 2 weeks, and the number stays active.

The words. On a client account, every price, policy and promise comes from the owner. Get them in writing. Emergency wording is written by each client, not by you or SAU.

The hours. Decide with the owner when the AI answers. Some owners want it after hours only at first. Others want it on every unanswered call.

The limit. The AI takes up to 10 calls at the same time. An 11th caller hears ringing with no pickup. For a small shop, that rarely matters. For a fleet on a storm day, you plan for it in the Catch course.

The text. On Core or higher, with texting approved, you publish the confirmation workflow. Remember that Core allows 10 active automations. Each workflow that is switched on counts as one.

The last test. Before go-live, make one real call to the client's real number. A real-number test uses credits like any call. That is fine, and the cost is small. It is the only test that proves forwarding works.

Common mistakes

  • Testing on real customers. Use Practice conversation and Talk in browser first. Save real calls for the final check.
  • Noting an error and going live. Fix the service name or the knowledge, then call again.
  • Leaving out the AI disclosure. There is no setting for it. Put it in the Initial greeting.
  • Writing prices into the agent. Use only prices the owner approves in writing. For now, say the tech confirms on site.
  • Forgetting Publish. Changes to the agent do not reach live calls until you publish.

Do this now

Complete the full build in your practice account. Save three things in one note. Keep the transcript of your best real call, the credits you used and one fix you made. You will use this build again in Experiment safely, lesson 7.

Practice the conversation

  1. Owner So the robot answers my phone? Customers will hate that.
  2. Operator It says up front that it's a virtual assistant. Then it books the job.
  3. Owner What if it books the wrong thing?
  4. Operator I test every service before go-live. I read every word of the test calls.
  5. Owner And after go-live?
  6. Operator I read the transcripts each week. If it gets something wrong, I fix the cause.
  7. Owner Does the customer get anything after booking?
  8. Operator An email confirmation right away. We can add a text confirmation too.
  9. Owner Can I hear it first?
  10. Operator Yes. Call this number now and try to book a drain cleaning.

Quick check

  1. You test your first build. You ask for a drain clearing, but the transcript shows the agent called it a pipe repair. What do you do?
    • Note the error and go live, because callers will understand
    • Delete the transcript and run the same test again
    • Fix the service name and the knowledge, then call again
    • Ask the owner to correct each caller on site
  2. A test call to your own phone lasts 4 minutes 20 seconds. How many credits does it use?
    • 60
    • 65
    • 75
    • 0, because it is a test
  3. Which test is free and changes no customer records?
    • `Talk in browser`
    • `Call my phone`
    • A call from your cell to the business line
    • A test with the text workflow published

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

Learn

Get certified

Community