Human review
Approvals
Route only the payment requests that need judgment to a human reviewer, with the triggering policy, recipient, amount, and agent context already attached.
Trigger
Policy-driven
Review context
Agent, recipient, rule, amount
Action
Approve, deny, retry
Capabilities
Review tools for the exceptions that matter
Route ambiguous or high-risk payment requests to people with the context they need to decide quickly.
Threshold routing
Hold high-value or unusual requests while letting low-risk payments continue automatically.
Policy explanations
Show reviewers the exact rule that paused the payment so decisions do not depend on guesswork.
Timeout handling
Keep pending requests visible and bounded so stale approvals do not linger unnoticed.
Decision audit
Record who approved or denied the request, when it happened, and what payment state followed.
Workflow
How payment exceptions reach a human
Approval logic keeps routine agent spend moving while pausing the requests that cross configured risk or amount thresholds.
Step 1
Payment requires review
The agent request crosses a configured amount, trust, category, or workflow threshold.
Step 2
Reviewer gets context
Conto presents the payment, policy result, counterparty, and agent information in one decision surface.
Step 3
Decision updates the flow
Approved requests can execute. Denied requests stay blocked with the reason preserved.
Visibility
Approval queues with the full payment story
Reviewers see the agent, recipient, amount, triggering rule, and downstream payment state from one decision surface.
Outcomes
What changes when approvals live in the payment path
Review queues stay focused on real exceptions.
Approvers do not need to reconstruct the payment story from logs.
The agent fast path remains available for trusted, routine spend.
Related
Solution patterns that use human review
Escalation paths
Approval routing for high-value or ambiguous payment decisions
Some payment decisions need a pause, not a hard stop. Agents can keep moving on the standard path while the payment layer pauses only the transactions that need human approval.
ExploreCredits and refunds
Refunds, credits, and make-goods that stay inside policy
Customer-facing agents can issue credits, refunds, and reimbursements quickly while Conto keeps routine corrections fast and sends higher-value exceptions into a controlled review path.
ExploreAutonomous purchasing
Autonomous procurement that still respects budget and vendor policy
Let agents buy inventory, services, software, or repairs on demand without giving up purchasing control. The agent can source and transact on its own, but only inside the vendors, categories, and budgets you approve.
Explore