Skip to content

product

Let agents act. Keep control of every run.

Verundo does not make agents smarter. It gives you five things for everything they do, across every system a run touches.

01 · before

See what an agent will do, before it does it

Ask for the plan and get a plain answer before anything has happened.

preflight · run r-4f2a
  1. ticket.updateruns alone
  2. subscription.cancelneeds a person
  3. refund.create · €1,200refused · 10× this customer's history
  4. email.sendneeds a person
exposure €1,320customer-visible 2cannot be undone 2

Every step comes back marked: runs on its own, waits for a person, or refused. You see how much money is at stake, what would reach a customer, and which steps could never be taken back.

02 · control

Decide what runs alone, and what waits for a person

You set the rules, per kind of action. The agent never decides for itself.

policy · support-agent · v3
reversible
runs alone
compensatable
needs a person
irreversible
needs a person
refund over €500
never
outside the org's own history
held
awaiting approval · step 2 of 4
subscription.cancel
Stripe · sub_9f2 · compensatable
so far: 1 executed · after this: steps 3 and 4 depend on it
agent support-bot · model claude-sonnet-5 · recorded

Routine changes run on their own, anything that reaches a customer or moves money can wait for a yes, and some things never run at all. Unusual amounts are held automatically. The person approving sees the whole run, not a lone request, and every step is on the record with the agent that took it.

03 · stop

Stop a run the moment something looks wrong

One click, the agent itself, or a rule you set.

run r-4f2a · contained
  1. 1ticket.updateexecuted
  2. 2refund.createheld · anomaly
  3. 3refund.createheld · anomaly
  1. 4email.sendnot executed
  2. 5opportunity.updatenot executed
pending approvals closednothing rolled back yeta person decides what happens next

Nothing further executes and pending approvals close. Nothing is undone behind your back either: what happens next is a person's decision.

04 · undo

Undo a bad run, and know it is really undone

One run, many systems, put back as one.

recovery · run r-4f2a
  1. 3email.sendGmail · irreversibleeffect remains · surfaced
  2. 2subscription.cancelStripe · compensatablereactivated · compensated
  3. 1ticket.updateZendesk · reversiblebefore-state restored · verified
2 of 3 recovered1 surfaced, never pretendeddependencies respected

Everything the run changed is put back, in the right order, across every system it touched. Where an exact undo does not exist, Verundo takes the closest counter-action. What can never be taken back, like a sent email, is named plainly instead of pretended.

A rollback that answered OK is not proof, so each system is checked afterwards: verified means it is really back as it was. And if an agent's request got no answer, Verundo finds out what happened before anything is sent again, so nothing happens twice.

05 · people

Never overwrite your colleagues' work

Agents are not the only ones changing things. A colleague edits the deal, a customer replies, another system syncs.

external state · opportunity 006Rt
agent wrote · 14:02
stage
Closed Won
amount
€48,000
owner
Anna
changed since · 14:31 · by a colleague
stage
Negotiation
amount
€48,000
owner
Anna
recovery would overwrite a person's work · held

Verundo notices when someone changes what an agent touched. If undoing the agent would overwrite a person's later work, both versions are shown side by side and a person decides.

See it on your own agents.