Diagnose an access problem and produce fix-or-escalate steps
Given a learner's reported access or technical blocker plus available context, identifies the likely cause and produces concrete resolution steps or an escalation message to the platform provider.
In / outLearner's reported blocker + platform context → diagnosis with fix steps (apply-now) or escalation message to provider
You might say…
“She can't log in and she's been waiting 20 minutes. I need to know what's wrong and what to tell her right now.”
What it does
Given a learner's reported access/technical blocker (login failure, broken link, enrolment glitch, playback error, missing community access) plus available context, identify the likely cause and produce concrete resolution steps the educator can apply directly or an escalation message to the platform/provider. Used when a learner reports being technically blocked.
Trigger: Use whenever a learner reports being technically blocked — login failure, broken link, enrolment glitch, missing community access — and you need a fast, concrete response.
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