Skip to content
SCENORYX

What the platform does

Written out in full, because the interesting parts of a simulation platform are the ones a feature list usually skips.

Scenario builder

  • Structured sections rather than one long prompt: basics, participant, character, situation, hidden case, objectives, evidence, knowledge, assessment.
  • Case detail written as individual facts, each with its own disclosure rule and an optional hint describing the moment it should come out.
  • Versioning on publish, so completed sessions stay bound to the case as it was when they ran.
  • Import from a document you already have. The result is a draft you review and correct, never something published automatically.

Knowledge library

  • PDF, Word, PowerPoint, Excel, OpenDocument Text, HTML, RTF, JSON, CSV, plain text and Markdown, uploaded straight to private storage from the browser.
  • Processing that follows each format: pages from a PDF, heading levels from Word, slide boundaries from PowerPoint, header rows from a spreadsheet.
  • A scanned page or a diagram with text baked into the image is read too, not just a PDF’s own text layer.
  • Real processing states. Uploading, processing, ready and failed reflect what is actually happening to the file.
  • Attachment per scenario, so a scenario reaches only the documents an author chose for it.
  • The character can look something up mid-conversation when asked a precise detail, rather than only drawing on what was loaded at the start.

Visual evidence

  • JPEG, PNG and WebP images attached to a scenario with a label and a reveal rule.
  • Revealed automatically when the subject comes up, on request, or at a moment you describe.
  • Delivered through a short-lived link issued for that one item at that moment, never a public URL.
  • Alt text required before a scenario can be published, so evidence is usable with a screen reader.

Live sessions

  • Voice in the browser over the participant’s microphone.
  • Timer, connection state and microphone state visible without dominating the screen.
  • Reconnection that resumes the same session rather than restarting the case.
  • Optional transcript, off by default and controlled per organization.
  • A full audio recording of the session, with a synced player and transcript, retained for as long as your plan keeps it and only reachable by the people you allow.

Reaching participants

  • Named sessions assigned to a specific person, or a public link anyone with it can start from, no account required.
  • An exam bundles several scenarios behind one link, in a fixed order, shuffled, or left for the participant to pick.
  • A real contact email collected before either kind of link lets someone start, so there is always a way to follow up.
  • A per-link cap on how many times any one person may attempt it.

White-label

  • Your own logo and accent colour on every page a participant sees.
  • Your own domain for participant links, so people join at your own address.
  • Your own email account for invitation and reminder emails, sent with your own wording.

Scheduling and access

  • Sessions assigned to a named participant, with an availability window, duration and attempt limit.
  • Statuses that reflect reality: scheduled, available, in progress, completed, expired, cancelled.
  • Windows enforced on every connection, not only when the page loads.

Assessment and reporting

  • Rubrics defined per organization, with your own criteria, weights and maximum scores.
  • Every score carries reasoning and a reference to the transcript turn that supports it.
  • Objectives met and missed, facts drawn out and never reached, and the conclusions the participant offered.
  • Results kept against the scenario version that produced them.