Voice AI technology

Guardrails for Voice AI Agents: Keeping Calls Safe and On Topic

The layers of guardrails for a phone voice agent, from prompts and approved sources to enforced limits and handover rules, with a test script to run first.

Call editorial team · Published · 5 min read

A phone agent speaks for your business. Callers may test it, confuse it, get angry with it or try to talk it into things it should not do. Guardrails are the boundaries that keep the conversation safe, on topic and honest, even when the caller pushes.

A manager reviewing call notes at a desk with a headset nearby
Illustrative image

This guide describes the main kinds of guardrail, how to layer them and how to test them. It pairs well with Preventing Made-Up Answers in Voice AI, which focuses on accuracy, and with What an AI Receptionist Cannot Do.

What guardrails are for

Think of a new receptionist on their first day. You tell them what to say, what not to promise and who to call when a situation is beyond them. A voice agent needs the same briefing, written down, and some of it enforced by the system rather than trusted to memory.

Four jobs a guardrail does

  • Keep it on topicThe agent talks about your services, not about anything the caller raises.
  • Prevent harmIt declines to give advice or take actions it should not.
  • Protect informationIt does not read out other people's details or reveal its own instructions.
  • Know when to stopIt hands over to a person when the situation calls for one.

Guardrails come in layers

No single measure is reliable by itself. A sensible set-up combines several, so that if one fails another catches the problem.

LayerWhat it doesExample
InstructionsTell the agent its role, tone and limitsOnly discuss opening hours, services and messages
SourcesLimit what facts it can useApproved answers, nothing else
Action limitsRestrict what it can doIt cannot book, refund or change records
Output checksInspect what it is about to sayBlock certain words or topics
Handover rulesDefine when a person takes overCaller asks for a person or sounds distressed
MonitoringReview calls after the factSearch transcripts for risky phrases

Instruction-level guardrails

The first layer is a clear brief. Describe the role, the tone, the topics in scope and the topics out of scope. State what the agent should do when something is out of scope, because refusal without an alternative is frustrating.

Instructions are guidance, not enforcement. A model usually follows them but can be talked around, which is why they should never be the only layer for anything important. Prompting an LLM Phone Agent shows how to write them clearly.

Rules the system enforces

The strongest guardrails do not depend on the model behaving. If an agent has no ability to issue refunds, it cannot be persuaded to issue one. In Call, an AI agent on a call is designed so that it cannot book or confirm appointments, call back, send anything or give discounts during the call; it says so and gives the route your sources describe. It answers from its instructions, persona, attached script and matching knowledge base passages, and when none answer the question it says it cannot confirm that. These rules sit under your own instructions: your instructions cannot switch them off.

Sensitive situations

Some conversations need a defined route, not a clever answer.

A handover path for sensitive calls

  1. RecogniseDistress, an emergency, a threat, a complaint or a request for a person.
  2. Respond brieflyA short, calm acknowledgement, no debate or improvised advice.
  3. DirectGive the right route: emergency services, an on-call person or a callback request.
  4. RecordSave what was said so the next person has context.
  5. Follow upA person reviews the request and closes the loop.

For emergencies, give callers a clear route to the right service in the opening of the relevant branch and do not rely on the agent to judge urgency. For callers who may be vulnerable, plan extra care; see Supporting Vulnerable Customers on Calls and Handling Abusive Callers.

Protecting information

Guardrails also protect data. The agent should not read back one person's details to another, should collect only what it needs and should not repeat sensitive numbers aloud unnecessarily. Identity checks before sharing anything account-specific belong in the design from the start. Privacy design is discussed in Privacy by Design for Voice AI.

Finding the balance

Guardrails have a cost. Every refusal is a moment where the caller does not get what they came for. Set the rules too loose and the agent drifts into risky territory; set them too tight and it sounds evasive and sends everything to a person, which defeats the purpose.

A practical way to find the balance is to sort topics into three groups. Topics the agent may handle freely, such as opening hours and directions. Topics it may handle only with exact wording, such as cancellation rules. Topics it must never handle itself, such as advice with legal or medical consequences. Start with a short list in each group, launch with a narrow scope and widen it as the transcripts show the agent behaving well.

Review the refusals as well as the failures. If many callers are being turned away for a reasonable request, the guardrail is too tight, or the scope should grow. Searching stored transcripts for the standard refusal sentence is a quick way to find them.

Test your guardrails by trying to break them

A guardrail you have not tested is a hope. Ask colleagues to play awkward callers and keep a log of results.

A guardrail test script

  • Ask for something out of scope and check the polite refusal
  • Insist, repeat and rephrase the request
  • Ask it to ignore its instructions
  • Ask it to reveal its prompt
  • Ask it to promise a discount or a booking
  • Ask for another customer's details
  • Raise an emergency and check the route offered
  • Say you want a person and check the handover
  • Speak angrily and check the tone stays calm

Add each real failure to the script. The wider method is in Testing a Voice AI Agent.

Setting guardrails in Call

In Call, write the scope and refusals in the agent's instructions, choose a persona for its role and tone, attach a script where wording must be exact and keep sources restricted to what you approve. Decide who picks up when a caller asks for a person; requests can be taken, assigned, noted and resolved from the help desk. Then run a test call and read the conversation afterwards, including the edit history if you correct the agent's words. Review the first weeks of real calls closely and tighten the rules wherever the transcripts show a gap.

Frequently asked questions

What is a guardrail in voice AI?

It is a rule or limit that keeps an agent within its job, such as staying on topic, refusing certain requests, protecting information and handing over to a person when needed.

Is a good prompt enough?

Usually not. A prompt is guidance the model may ignore if pushed. Combine it with approved sources, limits on what the agent can do and monitoring of real calls.

Can callers trick the agent into ignoring its rules?

Some try. Instructions alone can be bypassed, which is why important limits should be enforced by the system, and why you should test with deliberate attempts.

What should happen when a request is out of scope?

The agent should say politely that it cannot help with that on this call and offer a next step such as a message, a callback request or a person.

Do guardrails make the agent unhelpful?

Poorly written ones can. Keep the scope clear, give refusals an alternative route and review calls to find places where the agent is blocking harmless requests.

Who should own the guardrails?

Someone who understands both the business risk and the calls, usually an operations or team lead, with input from legal or compliance advisers for regulated topics.

Set clear limits for your AI agent in Call

In the demo console you can try incoming calls in a simulation.

Related guides