.svg)
Guardrails on a Braze AI decisioning agent are the limits you set before it starts choosing: the audience it can reach, the options it can pick, when it may send, and how often it may repeat itself. The agent learns inside those limits, so every guardrail you add also narrows what it can learn.
Key Takeaways
- Guardrails are the limits an agent learns within: audience, options, schedule, caps and repeat limits.
- In Go the audience is one segment that no other campaign uses, with filters and suppression built inside it.
- Agent quiet hours guide the times it chooses and aren't a guaranteed block. Workspace quiet hours is the hard control.
- Repeat limits can exhaust your options, so count creatives against the window before you set it.
- Test every guardrail with one question: does it protect a person, or protect the measurement?
- Leave the audience and control split alone while the agent trains, and read lift at the Fully trained stage.
What are guardrails on a Braze AI decisioning agent?
A decisioning agent doesn't write your content. It picks from the options you supply, and Braze describes it as testing and learning within limits you define. In Pro, the action bank holds those options, and the agent can only take actions that you've added to it.
The Go FAQ goes further: every individual element comes from variants you provided, and you are accountable for what the agent sends. Decisioning agents learn from outcomes across your population, while Braze Agents reason over one user's context. This post covers the first kind.
Which guardrails does each tier give you?
Decisioning Studio Go is the self-serve tier, set up inside Braze for recurring email programmes. Braze announced general availability on 14 Oct 2026, and its release notes list it as GA on 15 Oct 2026. Pro is the full-service tier, with support from the Braze AI Decisioning Services team.
| Guardrail | Decisioning Studio Go | Decisioning Studio Pro |
|---|---|---|
| Audience | One Braze segment, split into an agent group and a random control group | Eligibility and experiment cohorts built from segments |
| Options | Subject line, call-to-action and image variants inside each base creative | The action bank, with dimensions such as time of day, frequency and offers |
| Schedule | One send frequency, allowed days and quiet hours | Timing and frequency can be dimensions the agent chooses |
| Repeat limits | Windows on base creative and on subject line | Custom constraints and logic |
| Frequency caps | Apply your workspace caps, and choose whether agent sends count | Agents are designed to respect frequency caps and send the same campaign to a user no more than once per day in production |
Go ships its guardrails as productised settings. Pro opens them to custom constraints, and Braze's examples include blocking an offer in an ineligible geography or setting a maximum budget.
We recommend setting the Go guardrails deliberately, one at a time. Reach for a Pro constraint only when a rule can't be written as a segment, a schedule or a repeat window. A rule held in a segment is easier to audit than one buried in agent logic.
How do you set the audience guardrail?
In Go, the audience is one Braze segment. The agent splits it into a Decisioning Studio group and a random control group, and Braze lists the control as required. Braze recommends at least 20,000 users, and the maximum is 40,000,000.
The setup guide for Decisioning Studio Go asks for a segment that no other Canvas or campaign actively uses. If members also receive other messages, the engagement the agent observes is affected by them, and it can't tell whether a click came from its decisions or from something else.
Audience filters aren't supported in this release, so put your filters inside the segment. Build exit and suppression logic there too, for example an exclusion group that removes a user for 14 days after a purchase. The agent reevaluates segment membership daily.
Inside a broader journey, add users to the segment with a User Update step and make sure they leave the Canvas email path afterwards. Check a few representative members with User Lookup before you launch.
We recommend naming one owner for the segment. Membership is reevaluated daily, so a colleague's filter edit changes who the agent reaches by tomorrow.
The failure mode we watch for is a segment that looks dedicated but isn't. A rewards reminder and a promotion can both reach the member the agent is learning from, and the overlap shows up only as noisy results.
In Pro, the Braze example builds a master segment of marketing-opted-in consumers. It randomly assigns each consumer to one cohort, such as an AI decision, a random comparison, business as usual or a holdout.
How do schedule and quiet hours limit the agent?
Go takes a single send frequency, for example three times a week. The agent picks days and times within that frequency and doesn't optimise between frequencies. You must select at least as many days as the frequency requires.
Allowed days and quiet hours compound. Each day you rule out removes a day from the agent's menu, so our suggestion is to check that the remaining slots still suit the frequency.
Quiet hours limit the times the agent chooses, and Braze states they aren't a guaranteed send block. For a guaranteed block, Braze points to workspace quiet hours. Across several time zones, the agent prioritises delivering your message over the precise local time.
As at 21 Oct 2026, Braze lists workspace quiet hours as early access. Each channel supports one window, the window can't exceed 20 hours, and it applies in each recipient's local time zone. Check access with your Braze account team before you rely on it.
Decide first what an out-of-window send would cost you. If it's a nuisance, agent quiet hours are enough. If it would break a house policy or a contract term, we recommend treating the workspace window as the control and the agent window as a hint.
How do frequency caps and repeat limits work together?
Go lets you apply your workspace frequency caps and choose whether the agent's sends count toward them. Braze says a cap that protects user experience may not need the agent's sends counted, because they're already targeted. A cap that controls overall volume or spend likely does.
Counting the agent's sends also changes what your other programmes can send to the same people. We recommend deciding which programme gives way before you tick the box.
Repeat limits work at two levels. One stops the same base creative reaching a user twice inside a window you define, and the other does the same for subject lines. The random control follows the same constraints, so the comparison stays fair.
Braze lists variant-level limits on specific images or call-to-action text as not supported in this release. Plan your variety at the base creative and subject line level instead.
If a repeat limit leaves no valid option, the agent has nothing valid left to send and skips the send. Braze advises making sure every personalised component has enough valid options that a repetition cap can't exhaust them. A handful of distinct subject lines beats a hundred reworded versions.
At three sends a week, a 15-day window can hold up to seven sends to one person. Do that sum before you set the window: a subject line window that long needs at least seven distinct subject lines. Braze notes that a daily programme needs more creatives than a weekly one.
How many guardrails is too many?
Braze's Pro guidance is to minimise constraints, so they respect business rules while freeing agent-led experimentation as much as possible.
We turn that into one test for each guardrail: whether it protects a person or protects the measurement. A frequency cap, a quiet hours window and a suppression rule protect the person. A dedicated segment and an untouched control split protect the read.
A guardrail that does neither is a preference, and we recommend dropping preferences first.
Guardrail drift is the second failure mode we name early. A rule gets added after each uncomfortable send, and the agent's room to learn shrinks with each one. Review the list at a fixed interval and put the same test to every rule.
Order matters too. Audience changes reshuffle users between groups, while creative, schedule and constraint edits don't, so settle the audience first. Our suggested order for a first Go agent:
- Build a dedicated segment with exclusions and suppression inside it.
- Load options that differ in strategy, then review the full list of allowed combinations.
- Set the frequency, allowed days and quiet hours.
- Set repeat windows after counting how many options each one leaves.
- Decide whether the agent's sends count toward your frequency cap.
- Resolve every validation warning, then launch.
Which guardrails should you leave alone after launch?
Braze says not to judge results, resize the audience or change the control split while the agent is still training. Changing the split or swapping the segment reshuffles users between groups, while promoting other changes doesn't reset the agent or its training.
Braze says to plan on at least 30 days, and ideally to keep the agent always on. Early performance can look close to random, which Braze describes as expected. The stage to read lift is Fully trained.
We recommend writing the earliest date you may judge the agent on the launch ticket, so nobody argues about it in week two. If you must change the audience mid-flight, treat it as a relaunch: note the date, expect a reshuffle and compare results only from then.
Stop is the control for a send you didn't intend. Braze documents that it halts the agent, which resumes when you reactivate it, so our suggestion is to agree before launch who may press it and why.
What does a worked example of guardrail setup look like?
Take a hypothetical retailer with a rewards programme and a weekly rewards email. The example is illustrative: it uses no client data and carries no outcome, because the point is the order of decisions.
The team starts with the audience. It builds a rewards-member segment with exclusions inside the definition and checks a few members with User Lookup. A separate Canvas reminds members about expiring points, so the team removes agent members from that email path.
Next comes the schedule: three sends a week, with every day allowed except one that its own policy rules out. It sets agent quiet hours overnight in members' local time. A late send would break an internal policy, so it asks its Braze account team about workspace quiet hours.
Then come the repeat limits. The team picks 15 days as the subject line window, the example in the Braze FAQ. By our arithmetic that allows up to seven sends, so the team writes at least seven subject lines on different angles and reviews every allowed combination before launch.
The workspace cap exists to control overall volume, so the team counts the agent's sends toward it. After launch, it leaves the segment and split alone and judges lift only at Fully trained, after at least 30 days.
What can the agent not see when you set guardrails?
The agent evaluates each creative's fully resolved content, so Liquid, catalog references and Content Blocks are expanded first. Connected Content is the exception: it renders and sends normally, but the agent doesn't see what it returns. Braze advises against relying on it to make two creatives different.
We recommend auditing this as you would a suppression rule: list every difference between creatives and ask whether the agent could tell them apart. Test sends show only the combinations you select, so review the full list of allowed combinations too.
How does this connect to the rest of the programme?
Our post on which Braze AI features to adopt first, and in what order sets the sequence. Our guide to choosing between Decisioning Studio Go and Pro covers tier fit.
The audience guardrail starts with a good segment, which our post on segmenting your audience for better engagement in Braze covers. For send-time thinking on another channel, see optimising push notification timing in Braze.
Audience-level tests find one winner for everyone, while a decisioning agent finds an answer for each person. Our post on email A/B testing in Braze covers the audience-level side.
As a Braze implementation partner, CustomerIK recommends writing each guardrail down with the person or measurement it protects, and removing any that has neither before launch.
Frequently Asked Questions
1. Does Decisioning Studio Go guarantee that no email sends during quiet hours?
No. Agent quiet hours limit the times the agent chooses, and they aren't a guaranteed send block. Braze points to workspace quiet hours for a guaranteed block.
2. Can the agent send something I have not approved?
The agent only sends content that you've added as a variant, and you are accountable for what it sends.
3. Can I limit how often a single image or call-to-action text repeats?
As at 21 Oct 2026, Braze lists variant-level constraints on specific images or call-to-action text as not supported in this release. You can set windows on the base creative and the subject line.
4. What happens if my repeat limit leaves no valid options?
The agent has nothing valid left to send and skips the send.
5. Does changing a guardrail after launch reset the agent?
Promoting changes doesn't reset the agent or its training, but changing the control split or swapping the segment reshuffles users between groups.
Sources
- Braze, BrazeAI Decisioning Studio Go. Retrieved 21 Oct 2026.
- Braze, Set up your Decisioning Studio Go agent. Retrieved 21 Oct 2026.
- Braze, Decisioning Studio Go FAQ. Retrieved 21 Oct 2026.
- Braze, What to expect after launch. Retrieved 21 Oct 2026.
- Braze, Troubleshooting Decisioning Studio Go. Retrieved 21 Oct 2026.
- Braze, Use Decisioning Studio Go with Canvas. Retrieved 21 Oct 2026.
- Braze, Creative setup and management. Retrieved 21 Oct 2026.
- Braze, Design decisioning agents. Retrieved 21 Oct 2026.
- Braze, Get started with Decisioning Studio Pro. Retrieved 21 Oct 2026.
- Braze, Decisioning Studio Pro overview. Retrieved 21 Oct 2026.
- Braze, Identify eligible audiences and experiment cohorts. Retrieved 21 Oct 2026.
- Braze, Set up orchestration for Decisioning Studio Pro. Retrieved 21 Oct 2026.
- Braze, Workspace quiet hours. Retrieved 21 Oct 2026.
- Braze, Bring 1:1 decisioning to every marketing journey with BrazeAI Decisioning Studio Go. Retrieved 21 Oct 2026.
- Braze, Release notes. Retrieved 21 Oct 2026.
- Decisioning Studio Go reached general availability on 14 Oct 2026, so limits and "in this release" statements above reflect the documentation as read on 21 Oct 2026.
- Written by CustomerIK, a Braze implementation partner.
CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.
If you're planning a first decisioning agent and want to talk through the audience and schedule guardrails, let's talk.
.svg)
