An AI support agent recommends a $500 customer credit to keep someone from leaving. Agentics checks the policy, asks a person when it should, and leaves a receipt anyone can check. About five minutes. Nothing here is a live customer, and no money moves.
Use the arrow keys, or Back and Next.
1 · AI request
A support conversation opens. The customer has been with the company for three years and says they are canceling today.
Inbox
2 · Agent action
The support agent wants to issue a $500 customer credit so this person stays. It does not issue the credit yet. It sends the recommendation to Agentics.
Recommended action
Issue a $500 customer credit
Why
A three-year customer says they are leaving.
Status
Waiting on a policy check
3 · Policy check
In this case, a customer credit over $100 needs a person. Agentics holds the credit and asks. The check itself is recorded.
Rule
A customer credit over $100 needs a person.
This request
$500 customer credit
Result
Hold. Ask a person.
Record
The check was written down.
4 · Human approval
The request shows up as Needs you. Nothing is issued until a person approves it. One tap can also stop everything.
Needs you
Your agent wants to issue a $500 customer credit. Approve?
Approve5 · Verifiable receipt
The request, the policy check, the person's approval, and what happened next are on one receipt. Anyone can check it.
Request
Customer asked to cancel.
Action
$500 customer credit, held for a person.
Decision
A person approved it.
Outcome
Customer stayed. Ticket not reopened.
Check
6 · Downstream outcome
After the credit, the customer stayed. The ticket was not reopened. That is the outcome this case records, not a promise about the next one.
Customer stayed
Ticket not reopened
7 · Financial impact
The credit was $500. Set that against an estimated retained value when you have one. The estimate is not a measured result.
Credit
$500
Estimated retained value
Not a measured result.