Order EX-1048 never arrived. Can we refund the customer?
CUSTOMER OPERATIONS
Helpful agents. Accountable business decisions.
Help the customer. Review the exact refund, check its scope, and keep the decision and outcome together.
Slack# delivery-support
ChannelThis refund needs a manager’s approval. Here’s the exact request.
Refund ready for reviewApproved
- Order
- EX-1048
- Amount
- $18.42
- Destination
- Original payment method
Approval recorded
Approved. Just $18.42, back to the original payment.
Approval recorded. The amount, destination and current permission still match. Sending this refund once.
The payment provider confirmed the refund.
Refund confirmedRecorded
- Amount
- $18.42
- Destination
- Original payment method
- Record
- RF-1048 · one refund
Thanks. I’ll let the customer know it’s confirmed.
Request rejected. No action was dispatched. A new request needs its own review.
Ready
The exact refund crosses review.
Amount, order and destination stay bound to the request through approval and the provider result.
Read the decision path
- Support lead
- Customer reports a missing order.
- Assistant
- Prepares a $18.42 refund.
- DriftGate
- Order, amount, destination checked.
- Manager review
- Approves the exact refund.
- Payment tool
- Original method refunded once.
- Decision record
- Decision and result recorded.
- Allowed outcome
- The provider confirms one $18.42 refund to the original payment method.
- Changed destination
- New destination denied.
THE OPERATING MODEL
Make the work repeatable. Keep the authority explicit.
For a refund, evaluate the requester, order, amount, destination and current authority. Route an exception for review, bind approval to the actual request and preserve the resulting receipt. Reconcile an uncertain provider response before considering another effect.
The same model applies to sales discounts, subscription changes, contracts and outbound communication. Keep the voice or chat interface with the runtime that handles it well; the protected operation follows its own control path.
SEE IT IN PRACTICE
Put the platform to work.
COMMERCE
Resolve the complaint. Control the refund.
A food-delivery platform uses an assistant to resolve a missing order. A customer requests more than the eligible refund or asks for a different payment destination.
Runtime controls
RETAIL
Keep your support agent focused on support.
A shopping assistant is steered away from product and order questions toward unrelated coding or repeated expensive generation.
Runtime controls
FINANCIAL OPERATIONS
A timed-out refund should not become two refunds.
A payment provider receives a refund request, but the acknowledgement is lost. The agent wants to repeat it.
Runtime controls
SAME FOUNDATION
Explore the connected controls.
9 CAPABILITIES
Environment & Tooling Management
Bring tools, skills, instructions and configuration into one approved environment. Keep the right setup with the right project—not scattered across every client and computer.
Explore MCP & tool governance10 CAPABILITIES
Identity, Access & Policy
Give agents and workloads the access their tasks need—not unrestricted access to your business. Connect every governed request to an accountable identity, resource scope and current policy.
Explore Agent IAM10 CAPABILITIES
Runtime Governance & Execution Control
Put authorization, approvals and limits where your agents act. Follow each consequential operation from intent to an attributable outcome—even when the work waits or a response is lost.
Explore Runtime controls10 CAPABILITIES
Observability, Audit & Assurance
Connect identities, configurations, decisions and outcomes into an investigation path. Know what changed, why an action was allowed and which evidence supports the result.
Explore Audit & investigations10 CAPABILITIES
Lifecycle & Change Management
Give agents, connections, policies and knowledge a deliberate lifecycle. Review changes, release with intent, understand affected consumers and retire access without losing the history.
Explore Agent lifecycle10 CAPABILITIES
Data & Context Governance
Give agents the information their tasks need—not every document your organization owns. Keep source ownership, context boundaries and outbound data rules connected to the work.
Explore Data governanceKeep the conversation useful and the effect controlled.
A support, voice or sales agent may answer with relevant context. A refund, discount, subscription change or outbound message needs a defined operation, current scope and an effect boundary in the business system path.
For a refund, evaluate the actor, order, amount and destination. An approval should bind to those inputs; if they change, review again. If the provider response is lost, reconcile the original operation before considering another request. The transcript alone does not establish whether money moved.
BUILD WITH INTENTION