Agent actions: check availability, book, recognize callers, answer questions
Give the AI its tools: check availability, book, recognize callers and answer questions. A workflow sends the text.
Read the lesson
Goal: Switch on the right agent actions. The AI can then find the caller, book the job and answer from approved facts.
You need: A draft or published agent and a calendar with services set up. Bring the call map from lesson 1.
Why this matters
An agent with no actions can only talk. It can say "someone will call you back", and that is all. That is a nicer voicemail, not a receptionist.
Actions turn talk into work. With the right actions on, the agent checks the calendar, books the visit and saves the caller in the CRM. A booked job at the end of the call is the whole point. About 42% of answered calls book a job across trades. An agent that cannot book loses that share to the next company the caller tries.
Actions also carry risk. An agent that can cancel jobs can cancel the wrong one. So you switch on only what the call map needs.
What the agent can do today
Open Voice Agents, your agent, then the Actions tab. The Allowed actions list is grouped like this:
| Group | Actions | Use it for |
|---|---|---|
| Know who's calling | Recognize returning callers | Greeting repeat customers and finding their record |
| Capture new business | Save the caller as a new lead, Open a support ticket, Create a follow-up task | New callers, problems after a job, call backs |
Schedule | Check calendar availability, Recommend the right tech and time, Book an appointment, Reschedule appointments, Cancel appointments | Every Book row on the call map |
Answer questions | Searches Knowledge | Hours, areas, approved prices |
Custom integrations | Connected outside tools | Advanced setups only |
The old course title named a "send SMS" tool. The agent has no text action during a call. It also cannot take a card or look up an invoice. This lesson shows how texts happen after the call instead.
Matching actions to the call map
Go row by row through the call map. Write the action each row needs.
Call map outcomes to actions
| Call map outcome | Actions to switch on |
|---|---|
| Book | Check calendar availability, Book an appointment |
| Reschedule or cancel | Reschedule appointments; Cancel appointments only if the owner agrees |
| Answer | Answer questions |
| Task | Create a follow-up task |
| New caller on any row | Save the caller as a new lead |
| Repeat caller on any row | Recognize returning callers |
Leave off what no row needs. If the owner wants every cancellation handled by a person, keep Cancel appointments off. Then the agent creates a follow-up task for the office.
Recommend the right tech and time helps fleets with many techs and skills. An owner-operator with one calendar does not need it.
How the confirmation reaches the customer
When the agent books, ServiceAgent sends a built-in confirmation by email. Many home service customers want a text instead. A text confirmation needs a workflow. You have two ways to build it.
- Agent
Follow-uptab. Attach a workflow to the agent. It runs when the call ends. The quick create offers "WhenCall endedthenCreate CRM task". You can build your own from there. Appointment Scheduledtrigger. Build a workflow inWorkflows:Appointment Scheduled→Send SMS. It runs for every new booking, not only AI bookings.
Most Operators use the second way. Every customer gets the same text, whoever booked. Before any text goes out in the US, the business needs carrier approval. Set it up in SMS registration & consent.
How a booking becomes a text
- CallerAsks for a repair visit
- AI agentChecks calendar availability
- AI agentBooks the appointment
- AI agentSays a confirmation is on the way
- WorkflowAppointment Scheduled fires
- WorkflowSend SMS: time and address
- CallerGets the text and the email
Each switched-on workflow counts as 1 of Core's 10 active automations. Growth and Franchise have no limit.
The agent books inside your calendar rules
The agent can only book what the calendar allows. So the calendar setup decides what the agent offers. Check these before you test any booking.
- Services. Each service needs a real duration. If drain clearing really takes 90 minutes, do not set 60. The agent will book jobs too close together.
- Booking rules. The booking calendar has
Minimum Notice (hours),Maximum Advance (days)andBuffer Between Appointments (minutes). A buffer leaves time to drive between homes. There is no travel-time setting, so the buffer does that job. - Business hours and closures. Set
Closures & Holidaysfor days the shop is shut. The agent then never offers Christmas morning. - Who gets the job. A
New Appointmenthas oneAssigned To, and it must be a user with a login. On Core, the client has 2 users, and your Operator login takes the second. Techs without a login cannot be assigned. The client can move to Growth for unlimited users. Or a workflow onAppointment Scheduledtexts each job to the tech.
Who can be assigned the job
- The agent books a job
- Does the tech have a login?YesSet the tech in Assigned ToEnds hereNoThe tech cannot be assigned
- Will the client move to Growth?YesAdd each tech as a userNoText each job to the tech by workflow
- The tech knows the job
If a test call offers a strange time, check these settings first. The agent is usually right about the calendar. The calendar is wrong.
A test matrix for actions
Test each action you switched on, once, in Talk in browser. Write the result in a table with three columns: test, expected result, actual result.
- A new caller books a repair. Expect a new lead and a booking.
- A returning caller gives a known phone number. Expect the agent to greet them and find the record.
- A caller reschedules. Expect the old time freed and the new time booked.
- A caller cancels when cancelling is off. Expect a follow-up task, not a cancellation.
- A caller asks the hours. Expect the quick answer, word for word.
- A caller asks for a time outside
Maximum Advance. Expect the agent to offer the latest open date.
Action tests in Talk in browser
- New caller books a repair: new lead and booking
- Returning caller: agent greets them and finds the record
- Reschedule: old time freed, new time booked
- Cancel with cancelling off: a follow-up task
- Hours question: the quick answer, word for word
- Date past Maximum Advance: latest open date offered
Browser tests do not change customer records. To see records change, use one real call at the end. Then delete the test records.
Post-call extraction
Under Actions → Recording & call data, Post-call extraction pulls fields from the conversation after it ends. Examples are caller name or intent. You set each field with a name and a type. The results land on the call record. They do not fill the contact's Custom fields. If the office needs a value in a custom field, plan who copies it.
Knowledge the agent can search
Answer questions searches the Knowledge tab. Fill it with care:
Quick answers(Add FAQ): one question and one approved answer each. Best for prices, hours and areas.Knowledge sources(Manage sources): uploaded files such as a service list. PDF, Word, Excel or text files, up to 10MB each.Website knowledge & answer testing: test what the agent answers from the website.Pronunciation help: teach town names and product names the agent says wrong.
What Answer questions searches
Knowledge
Build it in ServiceAgent
- Open
Voice Agents, your agent, thenActions. - Turn on
Recognize returning callersandSave the caller as a new lead. - Turn on
Check calendar availabilityandBook an appointment. - Ask the owner about
Reschedule appointmentsandCancel appointments. Turn on only what they approve. - Turn on
Create a follow-up taskfor Task rows. Turn onOpen a support ticketif the business handles warranty problems. - Turn on
Answer questions. OpenKnowledgeand add one quick answer per Answer row. - Add
Pronunciation helpentries for local town names. - In
Workflows, buildAppointment Scheduled→Send SMSwith a short confirmation. Test it with the builder'sTest, which is free and sends nothing. ThenPublish. - Run three
Talk in browsertests. Use a new caller who books and a returning caller who reschedules. Add a caller who asks the hours. - Check it works: open
Jobsand confirm each test booking. OpenContactsand confirm the new lead. Then delete the test records.
Worked example: Northside Plumbing
Northside's map has 57 Book calls out of 100. Carol allows rescheduling but not cancelling. They want a person to try to save every cancelled job.
You switch on the two caller actions: Recognize returning callers and Save the caller as a new lead. You switch on three Schedule actions: Check calendar availability, Book an appointment and Reschedule appointments. You also switch on Create a follow-up task and Answer questions. Cancel appointments stays off. A cancel request becomes a task for the office.
Now the text confirmation. Northside books about 250 appointments a month, from all sources. That is an example input. The workflow runs on each one.
- One run: 1 credit.
- One text of 1 segment: 2 credits.
- Per booking: 3 credits.
- Per month: 250 × 3 = 750 credits.
Now say the text uses an emoji and runs to 90 characters. With an emoji, one segment holds only 70 characters. The text becomes 2 segments, or 4 credits. Per booking it is 5 credits. Per month it is 250 × 5 = 1,250 credits. One emoji costs 500 credits a month.
The cost of one emoji at Northside
Write the confirmation in plain characters, under 160:
"Northside Plumbing: you're booked for Tue 10am-12pm at 14 Oak St. Reply here if you need to change it."
That text is about 100 characters, one segment, no emoji.
Common mistakes
- Switching on every action. The agent cancels jobs the owner wanted to save. Fix: match actions to the call map.
- Promising a text the agent cannot send. The agent says "I'll text you" during the call. Fix: tell it to say a confirmation is on the way. Build the text in a workflow.
- Emoji in transactional texts. They halve the segment size. Fix: plain characters, under 160.
- No carrier approval. Texts fail or get blocked. Fix: finish
SMS registration & consentbefore launch. - Expecting extraction to fill custom fields. It lands on the call record only. Fix: plan who copies values that matter.
Do this now
Copy your call map. Add a fifth column called "Actions" and fill it for every row. Then write your confirmation text. Count its characters. Work out the monthly credits for your practice business at its booking volume.
Practice the conversation
- Operator Do you want the AI to book straight into your calendar?
- Owner Yes, if it picks real open slots.
- Operator It checks availability live, so it only offers open times.
- Owner What about cancellations? I like to talk those people round.
- Operator Then I leave cancelling off. The AI creates a task, and your office calls back.
- Owner Will customers get a text?
- Operator Yes. A short confirmation goes out on every booking, from any source.
- Owner What does that cost?
- Operator About 3 credits a booking. I keep it to one plain text to stay there.
- Owner Fine. Keep it short.
Quick check
- During a test call, the agent says, "I'll text you the details now." Why is that a problem?
- Texts during calls cost double
- The agent has no text action during a call
- Texts need Franchise
- The caller has not given a ZIP code
- A workflow sends a 1-segment text on 180 bookings a month. How many credits does it use?
- 180
- 360
- 540
- 900
- An owner wants staff to handle every cancellation. Which setup fits?
- Turn on `Cancel appointments` and tell callers to call back
- Turn off `Cancel appointments` and use `Create a follow-up task`
- Turn off all `Schedule` actions
- Send cancellations to voicemail
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.