Diagnose an access/account issue and prescribe the fix
Given a reported access or account problem and the current account state, diagnoses the likely cause — billing glitch, enrolment error, duplicate account, unprovisioned purchase — and prescribes the concrete steps to fix it.
In / outSupport ticket describing problem + account state (platform, billing, purchase records) → root-cause diagnosis + concrete remediation steps
You might say…
“A student says they can't get in but I can see them in Stripe — I have to work out whether it's an enrolment sync issue or something else entirely.”
What it does
Given a reported access or account problem plus the account state, reasons about the likely cause (billing glitch, enrolment error, duplicate account, unprovisioned purchase) and prescribes the concrete remediation steps. Used per-customer, reactively; a single judgement call the operator carries out manually in the platform.
Trigger: Use when a customer reports an access or account problem and the cause isn't obvious from the symptom alone.
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