Trust
Agents do the work. People stay in charge.
Anything that leaves the building waits for a person. Autonomy is earned one action at a time. Every edit can become a rule, and every run keeps a record.
Proposed rule from your edit
“Open renewal emails with the renewal date.”
Review
You approve what matters.
An agent drafts. You edit, approve or reject, in the app, in Slack or by text. Nothing is sent until you approve.
Always asks
Sending email from your mailbox and connecting a new data source always wait for a person. No rule changes that.
Decide where you are
Approve in the app on your laptop or phone, or reply in the Slack thread or text where the request came from.
See the reasoning
Each card shows what the agent read and why it is asking, so the decision takes seconds.
Earned autonomy
Your team sets what runs without asking.
Autonomy is set per action. Small changes you can undo may run on their own. Every automatic run is recorded.
Small changes that can be undone start here
Rejected or undone after it ran on its own? It goes back to waiting for a person and is flagged for review.
Waits for a person
A person approves each run.
Runs on its own
Runs above its confidence bar. Below it, waits.
Waits for a person
A person approves each run.
An admin lets it run on its own
Rejected or undone after it ran on its own? It goes back to waiting for a person and is flagged for review.
Small changes that can be undone start here
Runs on its own
Runs above its confidence bar. Below it, waits.
Always asks
Built in. No rule or promotion changes it.
Small changes, with Undo
Updating a CRM field can run on its own when the agent is confident. Each one is listed with Undo.
More room is earned
When people keep agreeing with an action, an admin can let it run. Rejected or undone? It goes back to waiting.
Set in one place
The Autonomy page lists every action in a workspace with its setting. Rules also live in trust.yaml in git.
A level, a budget, its access, and an off switch.
Pick how much room each agent has. Its budget and connected tools bound what it can do. One switch pauses the whole workspace.
Promotion takes evidence
A low-risk action needs 20 decisions, 90% agreement and no rejections in 14 days. High-risk actions never run on their own.
Always asks
Sending email, connecting a data source and enrolling a contact in a sequence always wait for a person.
Monthly budget
$763 of $1,200
Access
Zendesk · Drive · Slack
Read and draft
Every output waits for a person. The default for anything customer-facing.
Try it. Sample data.
Learning
Agents learn from your edits. You sign off.
When a reviewer edits a draft, Vocion proposes a rule from the change. A person approves it before any agent uses it. No silent self-modification.
You edit a draft
Say, you open a renewal email with the renewal date.
Vocion proposes a rule
"Open renewal emails with the renewal date." Scoped to the agent that wrote it.
A person approves it
Or rejects it. Agents cannot write their own rules.
Next time, it is right
The agent follows the rule, and the record shows which version ran.
Evidence
Every run keeps a record.
Open it when someone asks why. A record shows what ran, and a citation shows what a claim rests on. A team's records are open to that team.
- 01
What it did
Each step and tool call, with input and output.
- 02
What it read
The documents it pulled, cited in the answer.
- 03
Who approved it
Who decided and when, or the rule that let it run.
- 04
What it cost
Model, tokens and cost per turn, mission and build.
Triggered
New support ticket from Acme
Read
Ticket, contract, order history
Tools
Order lookup · help center search
Drafted
Reply with the new ship date
Reviewed
"Mention the credit note."
Approved and sent
By Morgan, support lead
Illustration. Sample data.
Security basics
Secure by default, in every plan.
These are true in the open-source core today. Enterprise controls build on them.
Per-workspace keys
Connector credentials are encrypted with AES-256-GCM under a key for each workspace. Wrap it with your own AWS KMS key.
Workspace access control
A team's agents, records and connected tools belong to its workspace. Only its members can open them.
Private assistants
Your assistant's thread is yours. No one else can open it in Vocion, including admins.
Checked replies
Slack, email and SMS webhooks are signature-checked. A reply decides only the card waiting in that thread.
Data in your Postgres
Records and synced documents stay in your database. Model calls go to the providers you choose.
Source you can read
Vocion is open source under MPL-2.0. Your security team can audit every line.
Get started
Walk your security team through it.
We will run Vocion in a sandbox account, show where every credential, trace and record lives, and answer the questionnaire with the source open.
For your team: a demo built around your job, on sample data.
For your engineers
Run it yourself
The requirements, the AWS path and the repo.