Approvals
Route only the payment requests that need judgment to a human reviewer, with the triggering policy, recipient, amount, and agent context already attached.
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.
Approval queues with the full payment story
Reviewers see the agent, recipient, amount, triggering rule, and downstream payment state from one decision surface.
procurement-agent → Quill Data
quilldata.io · data
procurement-agent → Northwind Ops
over weekly limit · waiting 12m
How an exception reaches a human
A payment trips a policy. $8,500 to quilldata.io is over the monthly cap.
Conto packages the full context and creates one request.
Dispatched in parallel. Every link carries a signed, single-use action token (SHA-256).
The reviewer decides right from the message.
The token is validated and consumed atomically. First valid response wins. The rest expire, so no decision lands twice.
Approved, the payment executes. Denied, it stays blocked. Either way it is logged with who decided, when, and through which channel.
Routine spend never stops. Only exceptions ask a human, on whatever channel they already use.
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.
See it in action
Property management in action
A maintenance agent dispatches vendors automatically, and expensive repairs route to a human for approval before any money moves. See routine work clear while exceptions wait for a decision.
Auto-approve below
$500
Vendor day cap
$2k
Allowed categories
Plumbing · electrical · cleaning
The payoff of selective review
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.
Human review in practice
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 Conto holds 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