Adjudicate a refund/cancellation request against policy
Reasons through a refund or cancellation request against the product's refund policy — checking timing, usage, and edge cases — and produces an approve/deny recommendation with customer-facing rationale.
In / outRefund/cancellation request + product refund policy + customer usage data → approve/deny recommendation with rationale for the customer response
You might say…
“Someone asks for a refund on day 32 of a 30-day policy and they've done half the course — I never know whether to just say yes or hold the line.”
What it does
Given a request and the product's refund policy, reasons through eligibility (timing, usage, edge cases) and produces an approve/deny recommendation with a customer-facing rationale. Used at the moment a request arrives; a single judgement call the operator confirms before action.
Trigger: Use when a refund or cancellation request arrives and you need a policy-grounded judgement before taking action.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation