You decide what the agents do without asking.
Dozens of agents work your plan across every account, campaign and renewal. How far each one may go is your setting, per system — and what always comes back to a person is fixed.
Inform
The agents read and report. They open nothing, draft nothing and send nothing.
Prepare
The agents do the work and stop at the last step. Every output waits for a person to submit it.
Autopilot
The agents run the work inside your guardrails. Only what needs a human comes back.
The difference is how far the work has already got.
You are in charge at all three. What changes is whether an agent is describing the move, holding it finished, or running it.
One job, drawn three times. The lane is the same length at every level — what moves is the point where it reaches you.
Meet the agents →What always comes back to a person, however high you set it.
An agent on autopilot is still an agent inside a boundary. These four are not settings you can turn off, and they are the reason the rest can run unattended.
Low confidence is an escalation, not a guess. An agent that cannot show its working does not act on it.
How guardrails work →Six systems. Six separate decisions about the agents.
Move any system to any level and watch how much the agents take on. Open a system to see every function it covers, and where each one is capped.
hours of human work a week, across the whole company
moves a week Beacon completes without anyone
exceptions a week that stop and ask for a person
Illustrative, at a company the size of the one used across this site. Your own numbers appear here once billing is connected.
Where an agent on autopilot may write.
Autopilot is only meaningful if something moves in the tools you already run. Here is exactly where an agent may write, and the one place it never will.
Each one is a separate switch, revoked in one click in the tool it came from. CRM writing is its own decision — plenty of companies turn record cleaning on long before they turn campaigns on.
Some things never reach level three. That is deliberate.
Turning a system all the way up does not turn everything in it all the way up. A handful of functions are capped in the product, not in your settings, and no amount of trust unlocks them.
The pale track is where each one would go if a setting could take it there. Nothing does — these are capped in the product, and they read the same on your first day and your thousandth.
Nobody starts at the top. Almost nobody stays at the bottom.
The pattern is the same at every company: turn up the systems where the work is obvious and reversible, and leave the ones with a customer or a signature at the end of them.
The three presets in the panel above, drawn. Month one proves the numbers; month three turns up the reversible work you have watched for eight weeks; month six leaves you the calls that were always yours.
Every level is reversible, and the record survives the change.
Drop a system back a level and it takes effect on the next move, not retroactively. Everything Beacon did while it was one level higher stays sealed exactly as it stood, with the setting it was running under attached.
You can always answer the question “who decided this, and under what rule?” — including for the moves that ran at a level you have since turned down.
Start at Inform. Nobody stays there.
Every customer sets this differently, and every one of them changes it. Start free and set it wherever you’re comfortable.