Support operations owner
The action waits until this owner approves or denies it.
Workflows · Refunds, payments, and credits
Review a high-value refund before money moves.
Show the order, amount, policy threshold, decision owner, and payment result before the action runs.
Example workflow. Execution requires a configured tool with provider permissions for this action; see the connection’s operation reference or bring your company tool to the demo.
Agent request
Issue a $12,000 refund against order 8472
An incorrect refund creates a direct financial loss and a customer-account discrepancy.
- Identity
- support-agent · Support ops
- Target
- order/8472
- Cost
- $12,000 refund · recorded agent cost
- Evidence
- Order record and refund policy
Policy decision
Refunds above $5,000 require the Support operations owner.
Tool call resumes
The payment tool receives the approved refund request and returns its result.
Tool call stays blocked
The refund does not run and the denial stays with the order context.
Execution order
The agent request stops before the connected tool runs.
- 01Support agent requests the refund
- 02Deixic checks amount, order, agent, and policy
- 03Support operations owner decides
- 04Connected payment tool returns the result
Activity history keeps the request, decision, cost, and result.
Keep the procedure for the next request.
Keep the policy and decision history, save the steps and evidence as a skill, and test changes on real sessions; an approval stays specific to its request.