An agent recommends, a workflow acts
An agent flags an account for closure, and a step three stages later closes it. You could review every answer the model gave and still not know whether the closure was allowed.
Supported agents, automated workflows
Put your business rules on the workflow steps that act
Most of what gets automated never touches a model. Even when an agent recommends a refund, a workflow step usually issues it. VeriProof checks that step against your rules before it runs, and brings in a person when the rules can't decide.
Where the consequences land
No AI at all
A nightly job writes off small balances. Nobody calls that AI, but your auditors will still ask who set the limit and who approved the exceptions.
Tools built with an AI assistant
Plenty of internal tools are now written with AI help and then run on plain logic. What they change needs limits like anything else.
What happens at a checked step
Before the step runs
The service behind the step asks VeriProof first, passing along what the rule needs, like the amount and the customer. If the answer is no, the refund never starts.
When the rules can't decide
The step pauses for a human-in-the-loop review. Whoever holds the authority gets a notice by email, Teams, or Slack and makes the call in VeriProof. Then the step resumes or stops.
After it runs
Your service reports the result, whether that's a refund issued or a payment that bounced. Until that report arrives, the record shows the outcome as pending.
One record
All of it ends up in a single sealed record, which an auditor can verify quickly and independently.
Connect the step, not the whole workflow
Your workflow tool keeps doing its job. VeriProof only needs to sit where the change happens, which is usually the service that issues the refund or updates the account. Add the developer kit there. If your platform can call an API and wait for the reply, the step can call the VeriProof API itself.
Timing matters here. A workflow that tells VeriProof about an action after it's done gets a record, not a check. To stop something, the step has to ask first.
Keep the approvals you already run
If your workflow platform already handles approvals well, keep using it. On its own, though, it can't apply one set of rules across every workflow and agent you run, and its records live inside its own system. VeriProof covers both.
Which steps to connect first
Start with the steps you'd least like to explain after the fact: refunds, account changes, anything that releases sensitive information. Notifications and lead syncing can usually stay as they are.
For pricing, a connected workflow counts as one agent. See pricing.
Have a workflow step you'd want checked?
Tell us what the step changes and where the workflow runs, and we'll suggest a connection. You'll hear back within one business day.