Guardrails
Hard rules your agent can’t break
Safety shouldn’t be an enterprise SKU. Every Flowyte agent ships with five deterministic guardrails — enforced on every turn, on voice and chat — which means the agent literally cannot cross the lines you set. Here they are, in full.
Free credits included. No credit card required.
Scripted demo — a replay of the real product, not a live session.
The five policies
Deterministic rules, not vibes
Most platforms claim safety in one sentence and gate the actual controls behind an enterprise contract. This is our entire Guardrails screen, restyled for this page. Values below are illustrative — you set your own.
Verify before disclose
Which fields the agent may read back, and to whom
Caller verification methods are configured on the same screen — you choose what counts as verified.
Which means the agent can read an appointment back to the account holder — and only the account holder. Everyone else hears exactly what you decided everyone can hear.
Writes gate
Nothing changes in your systems without a gate
- Confirm before any write
- Require a verified caller
Always escalate to a human
Which means the agent can book, update, and log — but it confirms first, and the actions you flag always land with a human instead.
Rate limits
Ceilings on how fast and how much it can act
Which means even a strange call can only do so much — the agent has a hard budget for actions, per minute and per call.
Business hours
A weekly schedule, plus after-hours behavior
After hours: explain the schedule, take a message, and offer the first opening tomorrow.
Which means the agent answers 24/7, but behaves the way you want at 2 AM — it knows the difference between open and closed.
Content & escalation
Banned topics, PII redaction, and the human threshold
Banned topics
The escalation threshold: how many negative-sentiment turns before the agent offers a person.
Which means the topics you ban never come up, transcripts stay clean of personal data, and a frustrated caller reaches a person before they reach their limit.
When it doesn’t know
It says so — and hands the call to a human
No AI answers everything, and we won’t pretend ours does. When a caller asks something outside the agent’s knowledge or its rules, it doesn’t improvise. It says it can’t help with that, and warm-transfers to a person with the full context of the conversation — so the caller never repeats themselves. The question it couldn’t answer shows up the next morning in Observe, ranked by how often it comes up, ready to fix. For the edge cases, that handoff builds more trust than any claim of omniscience would.
The last gate before live
Read what it will say — and won’t — before anyone hears it
Guardrails aren’t a settings page you configure once and hope about. Every publish opens a pre-publish report: what the agent will say, what it won’t, exactly which data leaves your system, and how much of your knowledge it covers. Watch the real publish flow below.
ACT 4 — PUBLISH: Review what it will and won’t say, then go live with one click.
Scripted demo — a replay of the real product, not a live session.
FAQ
Guardrails, answered plainly
What are guardrails in Flowyte?
Are guardrails included on every plan?
What happens when the agent doesn’t know the answer?
Can the agent leak customer data?
How do I know what the agent will say before it goes live?
Set the lines. Then let it answer.
Draft an agent in minutes, read its guardrails, and publish when you’re ready.
Free credits included. No credit card required.