Use cases

A student wants the guarantee honoured.

An online course platform offers a 14-day money-back guarantee. Requests peak when a cohort starts.

The guarantee as a rule

14 days, any reason, up to an amount you choose. Above it, your team decides. Every student gets the same answer, in their language.

  • Readable rules, no code
  • Replies in the student’s language
  • Same answer every time

The course is not for me. Can I get my money back?

You enrolled on 3 Nov, inside the 14-day guarantee. I can refund the €149.00 to Mastercard •• 5100.

Refunded

Change it without guessing

Thinking of 30 days? Replay last quarter’s requests on the draft and see exactly which ones would change.

  • Replay on real past requests
  • The changed cases listed
  • Publish with a note
Simulator results: outcomes per currency, top reasons and the list of cases whose outcome would change, each with a link to its case.
Illustrative example, not real data

Email works too

Students who write to your support address get a ticket. Identity is proven by a link to the address on file.

  • Your inbox becomes a channel
  • Link-based identity
  • Hands off when unsure

From: [email protected]

Re: Your request [#1182]

Thanks! Could you also cancel my plan?

↳ Threaded into ticket #1182

✓ Identity proven by email link

Illustrative example, not real data

Start with low limits. Raise them when the record shows it works.

Start in test mode, run your policy against your own history, and go live when the results meet your standards.

  1. 1A test workspace on your provider’s test mode
  2. 2Your past requests replayed against your policy
  3. 3Live with low limits, raised as the record allows