How it works
Seven stages, from the material sitting on your shared drive to a scored session you can put in front of an examiner.
Bring in the material you already have
Upload protocols, policies, case libraries or course handbooks. Each file is read, split along its own structure and indexed. A scenario draws only on the documents attached to it, so a sales roleplay never reaches into your compliance library.
Write the case, and the rules for revealing it
Set who the participant is and who they are meeting. Then write the case as discrete facts, each with a condition: volunteered, given on a direct question, given once the participant has built some rapport, or held back unless asked for exactly.
Attach what the character can show
An invoice, a contract page, a radiograph. Say when each becomes available: as soon as the subject comes up, only when the participant asks, or at a point you describe.
Define what good looks like
Build a rubric with your own criteria and weights. A classroom scenario and a support call are marked on different things, so they use different rubrics against the same engine.
Assign it, with a window
Schedule a session for a participant with an availability window, a duration and an attempt limit. Outside that window the simulation will not open.
They talk, and the case unfolds
The participant allows their microphone and starts. The character answers what was asked, in role, with the case detail released according to the rules you set. What they release is recorded as it happens.
Read what actually happened
The session ends and assessment runs. You get a score per criterion, the reasoning behind each, the questions never asked, and the transcript turn that supports every judgement.
Common questions
- Do participants need a phone number or any software?
- No. The conversation runs in the browser over the participant’s microphone. There is no telephony provider, no dial-in and nothing to install.
- Can the character be made to reveal the case or its sources?
- The rules that keep the character in role sit above scenario content and cannot be overridden by a participant or by an author. Retrieved material reaches the character without any indication of which document it came from, so there is no file name, book title or page number available for it to disclose.
- What happens if a scenario is edited after sessions have run?
- Editing publishes a new version. Sessions already completed stay attached to the version they ran against, so a historical result always reflects the case as it was at the time.
- Where are uploaded documents stored?
- In private Supabase Storage, reachable only by the organization that owns them. Participants never browse the library; they see only what the running scenario surfaces, through a short-lived link issued for that one item.