Writing the call flow and brand voice
Write the call flow and the brand voice the AI uses on every call.
Read the lesson
Goal: Write the greeting, call flow and voice rules. The agent then sounds like the business and follows the call map.
You need: A call map (lesson 1) and a draft agent in Voice Agents. Book 20 minutes with the owner.
Why this matters
Callers judge a business in the first ten seconds. A stiff or confusing greeting makes them hang up. A rambling agent costs money too. Every voice minute uses 15 credits, rounded up.
The flow also decides what the agent does. A good flow turns the call map into clear steps. A bad flow leaves the agent to guess. Guessing agents book the wrong service or promise things the owner never approved.
Owners also worry the AI will sound robotic. The voice rules fix that. You capture how the owner talks, and you write it down.
Where each piece goes
The Basics tab holds most of this work.
| Field | What you put there |
|---|---|
Agent name | A first name callers hear, if the owner wants one |
Language | The main language for the line |
Initial greeting | The first words, including that this is a virtual assistant |
| Voice instructions | The call flow and voice rules, up to 32,000 characters |
Advanced instructions | Edge cases and rules that rarely apply |
Voice | The sound of the voice |
Call behavior | Noise reduction, reply pause and check-ins |
Call handling & business hours | What changes in and out of hours |
Short facts go in the Knowledge tab, not in the flow. Hours, service areas and approved prices belong in Quick answers or Knowledge sources. The flow says what to do. Knowledge says what is true.
Keep these apart. When a price changes, you update one quick answer. You do not rewrite the flow.
Where each piece goes
- Ask one question at a time
- Repeat the address back
- Escalate burst pipes
- Never say "I don't know"
- Business hours
- Service area towns
- Approved service call price
- Warranty terms
The call flow pattern
Every flow follows the same seven steps.
- Greet. Name the business, say this is a virtual assistant, and ask how to help.
- Find the reason. Listen, then match the caller to one call map row.
- Check for an emergency. Ask one safety question if the reason could be urgent.
- Collect details. Name, phone, service address and a short problem description.
- Act on the outcome. Book, escalate, answer, create a task, or end politely.
- Confirm. Read back the time, address and what happens next.
- Close. Thank the caller and end the call.
Write each step as short commands. "Ask for the service address. Repeat it back." Short commands are easier for the agent to follow and easier for you to fix.
The seven-step call flow
- 1. GreetBusiness name, virtual assistant, how can I help
- 2. Find the reasonMatch one call map row
- 3. Could it be an emergency?YesEmergency block: details, then transferNoGo on to step 4
- 4. Collect detailsName, phone, address, problem
- 5. Act on the outcomeBook, escalate, answer, task or end politely
- 6. ConfirmRead back time, address and next step
- 7. CloseThank the caller and end the call
Writing the brand voice
Ask the owner three questions:
- "How do you answer the phone?"
- "What do you never want a customer to hear?"
- "Describe how you talk to customers in three words."
Turn the answers into voice rules. Keep them concrete. "Warm" means little to an agent. "Use the caller's first name once. Say 'no problem' instead of 'certainly'." That is concrete.
Add rules about length. "Ask one question at a time. Keep answers under two sentences." These rules save credits and sound more human.
Turn vague words into rules
- Be warm
- Be professional
- Sound friendly
- Use the caller's first name once
- Say "no problem" instead of "certainly"
- Ask one question at a time
- Keep answers under two sentences
A sample block for one map row
Write one block of instructions for each row of the call map. Here is the block for Northside's biggest row, new repair requests.
When the caller needs a repair, such as a leak, a clog or no hot water:
- Ask what is happening, in one question.
- Ask if water is coming in right now. If yes, follow the emergency block.
- Ask for the caller's name, then the service address. Repeat the address back.
- Ask for the best phone number for the tech.
- Check the calendar and offer the two earliest times.
- Book the time the caller picks.
- Read back the day, time window and address.
- Tell the caller they will get a confirmation by email.
A repair call that follows the block
- Northside agentThanks for calling Northside Plumbing. This is Sam, Northside's virtual assistant. What can I help you with today?
- CallerMy kitchen sink is leaking under the cabinet.
- Northside agentIs water coming in right now?
- CallerNo, it's a slow drip into a bucket.
- Northside agentThanks. What is your name, and the service address?
- CallerAna Lopez, 14 Oak St.
- Northside agentThat's 14 Oak St. Is this the best number for the tech to reach you?
- CallerYes, this cell.
- Northside agentI have Tuesday 10 to 12 or Tuesday 2 to 4. Which works?
- CallerTuesday morning.
- Northside agentYou're booked Tuesday 10 am to 12 pm at 14 Oak St. A confirmation is on its way by email.
Notice what is not in the block. There are no prices and no hours. Those live in Knowledge. If the caller asks the price, the agent uses the approved quick answer.
Write the emergency block in the same style. The owner gives the cases in their own words. You write what the agent does: collect name, address and phone, then transfer. Lesson 5 builds this block in detail.
Edge cases to cover in Advanced instructions
Each one needs a short rule:
- Two problems in one call. Book one visit and note both problems.
- A caller who will not give an address. Offer a call back from the office and create a task.
- A caller who asks for a person. Follow the owner's transfer rules from the call map.
- A child or a confused caller. Take a name and number and create a task.
- A caller outside the service area. Say so politely and do not book.
- A wrong number. Apologize and end the call.
Test each edge case once with Practice conversation. It is typed, free and fast.
Languages
The agent can talk in 8 languages. They are English (US, UK, Australia, India), Spanish (Spain, Mexico), French and Hindi. Set the main one with Language in Basics.
Check the call map. If many callers speak Spanish, plan for it. Write the greeting so Spanish speakers know they can switch. Then test the full flow in each language the map shows. Test with a native speaker if you can.
How long should a call be?
Set a target length before you test. Most booking calls can finish in 3 to 4 minutes. Answer calls, such as hours or service areas, should take 1 to 2 minutes. Emergency calls should reach a person within about 1 minute.
Target call length by call type
Time every browser test. If a booking call takes 6 minutes, find the slow step. It is usually one of three things:
- The agent asks questions the call map does not need.
- The agent repeats long confirmations more than once.
- The agent explains too much when a caller asks a simple question.
Watch the cost of each extra minute. At 15 credits a minute, one wasted minute on 100 calls is 1,500 credits. Read the flow aloud before you test it. If you run out of breath on one instruction, it is too long. Cut it into two.
Size changes the flow
- Owner-operator: Keep the flow short. Book the job and tell the caller the owner will confirm. These owners like control.
- Fleet: Add a step to pick the right service type, because the calendar has many techs and skills.
- Multi-location: Ask for the town or ZIP code early. The answer decides which location and calendar to use.
Build it in ServiceAgent
- Open
Voice Agents, then your agent, then theBasicstab. - Fill in
Agent nameandLanguage. - Write the
Initial greeting. Name the business and say this is a virtual assistant. - Paste the seven-step flow into the voice instructions. Add one block per call map row.
- Paste the voice rules under the flow.
- Put rare cases in
Advanced instructions. - Pick a
Voice. Play it to the owner before you decide. - Set
Call behavior. Turn on noise reduction for trades whose customers call from loud places. - Open the
Knowledgetab. Move every fact out of the flow intoQuick answersorKnowledge sources. - Open
Test & publish. UseTalk in browserto run one call per map row. It is free. - Use
Practice conversationto type tricky callers, such as someone who gives two problems at once. - Check it works: each test call should end in the outcome on the map. Then
Publish.
Worked example: Northside Plumbing
Owner Carol says they answer, "Northside Plumbing, this is Carol." Their three words are "fast, honest, friendly". They never want a customer to hear "I don't know".
Your greeting: "Thanks for calling Northside Plumbing. This is Sam, Northside's virtual assistant. What can I help you with today?"
Your voice rules, in part:
- Ask one question at a time.
- Keep each answer under two sentences.
- If you do not have an answer, say "Let me get the right person to call you back."
- Use the caller's first name once, after you learn it.
Now the cost side. Carol's AI line takes about 77 calls a month, the calls their office misses. An early test shows calls average 5 minutes. With the "one question at a time" and "two sentences" rules, browser tests drop to about 4 minutes.
Saved minutes: 77 calls × 1 minute = 77 minutes. Saved credits: 77 × 15 = 1,155 credits a month. That is more than half of Core's 2,000 monthly credits. Short rules matter.
Short answers save credits at Northside
Common mistakes
- Facts inside the flow. Prices and hours buried in instructions go stale. Fix: keep facts in
Knowledge. - No virtual assistant line. Callers feel tricked later. Fix: say it in the
Initial greeting. - Long, stacked questions. "What's your name, address and problem?" confuses callers. Fix: one question at a time.
- Vague voice words. "Be professional" changes nothing. Fix: write concrete rules with examples.
- Testing in one language only. Spanish callers meet an untested flow. Fix: test every language on the map.
Do this now
Write a full greeting, seven-step flow and five voice rules for your practice business. Paste them into a draft agent. Run 5 Talk in browser tests, one per major map row. Write down every place the agent paused, guessed or talked too long.
Practice the conversation
- Operator How do you answer the phone when you pick up yourself?
- Owner "Northside Plumbing, this is Carol."
- Operator Good. The AI will sound like that, and it will say it is a virtual assistant.
- Owner Do I have to say it's AI?
- Operator I recommend it. Callers trust it more when nobody hides anything.
- Owner What words do you need from me?
- Operator Three words for how you treat customers, and anything you never want said.
- Owner Fast, honest, friendly. Never "I don't know".
- Operator Then when it lacks an answer, it promises a call back from the right person.
- Owner That's what I'd say.
Quick check
- The owner raises their service call price. Where should you change it?
- In the voice instructions, inside the booking step
- In one `Quick answers` entry in the `Knowledge` tab
- In the `Initial greeting`
- In `Advanced instructions`
- Calls average 6 minutes. New rules cut them to 4 minutes on 50 calls a month. How many credits do you save each month?
- 100
- 750
- 1,500
- 3,000
- About a third of a cleaning client's callers speak Spanish. What do you do?
- Tell Spanish speakers to call back during office hours
- Set the greeting so callers can switch, and test the full flow in Spanish
- Write a second agent in English only
- Do nothing, because the agent handles all languages the same way
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.