DocsHow-to
Write guardrails
Short rules that come before shop notes, the schedule and every tool.
By the Callaroo team. Updated November 2026
A guardrail is a short rule the assistant must follow on every reply and every action. It is the first thing the assistant is told, before your shop notes, the saved schedule and any tool result. Use guardrails for behaviour that must not change from call to call: privacy, how to speak, when to stop, and what never to do.
- Where
- Dashboard → Agent → Configuration → Guardrails
- Saved with
- Agent settings. Save settings applies it to the next call.
- Applies to
- The caller conversation and its actions
- Comes before
- Shop notes, the saved schedule and tool results
What a guardrail is not
- It is not a blocklist. A guardrail shapes what the assistant says; it does not stop a phone number from calling.
- It is not a replacement for shop notes. Prices, hours, address and pickup rules belong in shop notes or the saved schedule.
- It does not change dashboard permissions. Owners and managers still control settings; staff still have read-only access to the Agent page.
- It does not make an unavailable tool work. A reservation, text or transfer still needs its own setup.
- It is not a legal or compliance guarantee. Write the rule you need and test it on a real call.
The default rules
New workspaces start with three guardrails. They are on by default and can be edited, turned off or removed.
| Default rule | What it says |
|---|---|
| Sound human | Talk like a person taking an order. One short sentence, then wait. Do not mention tools, lookups, drafts, a dashboard, or that you are an AI. |
| Menu and failures | Answer what you sell from the shop notes. If a lookup is empty or a transfer fails, say you don't have it or you can't connect them, then stop. Do not try another tool. |
| Translation | Speak English unless they ask for another language or keep speaking one. If they ask, translate into that language. The usual set is Spanish, Mexican Spanish, Portuguese, French, Chinese, Japanese, Turkish, Hindi, Bangla, Urdu and Arabic. Then continue the order in the language they are using. |
The assistant also has built-in safety text that is not shown as an editable guardrail row. It covers privacy, off-topic requests and not claiming an action before the tool confirms it. Guardrails are for your own wording on top of that, not the only protection.
Add or change a rule
Open Dashboard → Agent → Configuration.
Find Guardrails and select Add guardrail, or select an existing rule to edit it.
Give the rule a short name and write the behaviour in the description.
Leave Rule is on selected if it should apply now. Save changes.
Select Save settings at the top of the Agent page. A rule is not live until the page is saved.
Test the rule in Try it live. It uses the last saved settings.
The row menu also turns a rule off, turns it on, or removes it. Turning a rule off keeps the text for later. Removing it deletes it from the saved list.
Write a rule that holds up
- Write one behaviour per rule. A rule that tries to cover privacy, ordering and language at once is hard to follow.
- Use plain, direct language: say what to do, not what to avoid where possible.
- Make it testable. If you cannot describe a caller sentence that would show the rule working, rewrite it.
- Do not repeat prices or hours in a guardrail. Put those in shop notes or the weekly schedule so there is one source of truth.
- Do not mention tool IDs or internal steps. The assistant should not talk about tools to a caller.
- Privacy is built in: the assistant is told not to share order counts, sales totals or other customers' details. Add a guardrail only if you need extra wording for this shop.
Examples
| Situation | Rule you can write |
|---|---|
| Callers ask how busy the shop is | Never share order counts, sales totals, revenue or how many other customers called. Say you cannot share that and ask what they need. |
| The shop has a strict allergen script | When a caller mentions an allergy, repeat the item and tell them to confirm ingredients with staff before ordering. Never promise an item is allergen-free. |
| Staff cannot take transfers at close | After the saved closing time, do not offer a transfer. Offer a callback request instead. |
| Callers keep asking for directions to another business | Answer only questions about this business. After one redirect, say goodbye and end the call when the end-call tool is available. |
| The shop speaks English and Spanish | If the caller speaks Spanish, answer in Spanish. If they switch back to English, continue in English. |
Order of rules
The assistant is told to follow safety and guardrails first, then shop notes, then the saved schedule, then the saved result of a named action. That result gives facts such as a price or an available time, but it cannot override a guardrail. If a rule and a shop note disagree, the rule wins and the note should be corrected.
Guardrails are read and enforced by the assistant's instructions, not by a keyword filter. They reduce the chance of a bad reply; they do not make the assistant immune to a determined caller. Use the blocklist, transfers and staff review for problems that need a hard stop.
Limits
- Rules per workspace
- Up to 12
- Rule name
- Up to 80 characters
- Rule description
- Up to 600 characters
- Empty rules
- A rule needs both a name and a description before it can be saved
If Guardrails shows a settings update notice, the workspace has not received the change yet. Existing instructions still apply. Ask support rather than editing the records directly.