Skip to main content

Who this guide is for

This guide is for instructional designers and L&D teams using Articulate Storyline 360, Articulate Rise, or another LMS authoring tool. Learners do not need a Real Talk Studio account. Credits come from the studio.

The options

There are two ways to put practice in the course, plus one optional upgrade for named learner tracking.
Start with option 1. Add advanced only if you need per-person scores. Use option 2 only after a published-course mic test.
Do not import Real Talk Studio as a SCORM zip. Publish your Storyline or Rise module as SCORM, and put option 1 or 2 inside it. There is no standalone Real Talk Studio SCORM file.

The big picture

Real Talk Studio does not replace your course. You keep slides, videos, and quizzes, and add AI practice where learners need to apply what they learned.
1

Create the roleplay in Real Talk Studio

Build your scenario, personas, and skills in your studio as usual. Name skills clearly — they appear in feedback and exports (e.g. “Active listening”, “Handling objections”).
2

Copy the anonymous share link

In Studio admin, open the roleplay’s menu → Share linkShare anonymouslyCopy. That URL is /embed/{slug}?studioId=… — no account required.Do not use Share with logged-in users; that path asks learners to sign in to the studio.
3

Add it to the course

Link (recommended): paste the anonymous URL on a Storyline button (new window) or a Rise Link / Button block (new tab). Optional: tick Use studio logo in roleplay setup before copying.For option 2 instead: Studio → ⋮ → Get embed codeEmbed CodeLMS / RiseCopy Code. Paste that full <iframe> into a Rise Embed block or a Storyline Web Object — not as a URL. Height at least 800px. Confirm the snippet includes allow="camera; microphone; display-capture; autoplay".
4

Add a short intro for learners

On the slide before the roleplay, tell learners they will need microphone access (and camera if your scenario uses video). Link to Troubleshooting if your organisation uses strict corporate networks.
5

Publish and test

Publish the course and complete a test run yourself. Confirm the avatar loads, audio works, and feedback appears at the end. If you used an iframe, test microphone inside the published LMS course, not only in Preview.

Where to place roleplays in a programme

You can add roleplays anywhere it helps learning:
  • Before training — diagnostic conversation to see where someone starts
  • After a module — short practice applying one skill
  • At the end — summative assessment using the same scenario as the start (to measure improvement)
Align the skills you configure in Real Talk Studio with the learning objectives on each module. When skill names match your curriculum, reporting and any future automation are much easier. Rough timing: diagnostic or summative roleplays often need 8–15 minutes. Short practice sessions can be 5–8 minutes with fewer skills.

Getting results out

Every session is saved in Real Talk Studio whether you used option 1 or option 2. Without advanced (extCustId), rows are anonymous.

Download a spreadsheet (no IT)

Best for: pilots, manager reviews, compliance records, programmes where the LMS does not need live scores. No technical setup. Anyone with admin access can:
  1. Open your studio in the Real Talk Studio admin portal
  2. Go to Session history
  3. Filter by date or roleplay
  4. Click Download CSV
The file includes date, roleplay name, score, skill ratings, session length, and learner email (when available). If a learner reference ID was added to the URL (see below), it appears as External Customer ID. You can open the CSV in Excel, share it with stakeholders, or import it into your LMS reporting on a schedule that suits you.

Webhook to your LMS (part of advanced)

Best for: updating an LMS gradebook automatically, routing learners to different modules based on scores, or pushing results into another system without manual exports. A webhook is an automatic notification Real Talk Studio sends to a web address when someone finishes a roleplay. That address is usually set up by your IT team or using a no-code tool like Zapier or Make. What you need to do in Real Talk Studio admin:
  1. Open your studio → Settings
  2. Paste the webhook address your IT team gives you into Webhook URL
  3. Save
Full technical details (what data is sent, example setups) are in Webhook config — share that page with your IT contact.
You do not need a webhook for most programmes. CSV export is enough unless you specifically need scores in the LMS the moment a session ends. A webhook without extCustId still fires, but you cannot join the payload to a named learner.

Advanced: linking results to the right learner

This is the upgrade on option 1 or option 2. If many people use the same practice URL, completions are anonymous unless you pass a learner reference. In Real Talk Studio this is called extCustId (external customer ID). It is usually the LMS user ID or enrolment ID — not the learner’s email in plain text. You will see the same reference in:
  • The External Customer ID column when you download CSV
  • Automatic webhook deliveries (if configured)
  • Studio analytics — the embed identification stat on your analytics dashboard
Append it to the practice URL:
A static Rise or Storyline link cannot do this by itself — the id must be added per learner at launch. Details for IT are in Webhook config.

Studio analytics reporting

When learners practise from an LMS link or iframe, Real Talk Studio stores your extCustId as ext_cust_id on the completion record. That value is what ties anonymous sessions back to individual learners in Studio → Analytics. Real Talk Studio reads the query parameter at session start and persists it through completion. There is no separate postMessage step for the learner ID.
Check Studio → Analytics for Embed identification — it shows what share of embed sessions include ext_cust_id. If the rate is low, the course is likely using a static URL instead of injecting a per-learner ID at launch.

Who does what

Share Firewall configuration with IT if learners on office networks have connection issues.

Platform tips

If your LMS must mark the activity complete in the gradebook when the roleplay finishes (not just when the learner clicks Continue), that usually requires extra setup by your IT team — see For your IT team below. Iframe postMessage can drive that; a new-tab link cannot, unless you complete the Storyline/Rise module separately.

Checklist before launch

  • Roleplay skills match module learning objectives
  • Learners open practice via new-tab link, or iframe height is at least 800px
  • Intro slide mentions microphone (and camera if needed)
  • You completed a full test session in the published course (iframe: confirm the mic works there)
  • You know whether you are using CSV export or asked IT to set up a webhook
  • If you need named learners: extCustId is injected at launch (Storyline JS or LMS URL rewrite)
  • Corporate learners: IT has reviewed firewall requirements if needed

For your IT team

The sections below are for LMS administrators, developers, or integration partners. Instructional designers can share this page and point them here.
Each roleplay has an embed URL from Embed Code. Learners do not sign in. Optional query parameters: primaryColor, fontFamily, buttonRadius, language / lang, extCustId, parentDomain. Restrict embed domains under Studio → Security → Allowed domains. See Organization & studio permissions.If you iframe the experience, include microphone and camera permissions:
Iframe failure modes: (1) nested frames (LMS → Rise/Storyline player → Web Object → Real Talk Studio) often deny getUserMedia; (2) Storyline Web Objects that omit allow=; (3) corporate CSP / frame-ancestors that block third-party iframes while a new-tab link still works. Prefer a new-tab link unless a pilot on the production LMS proves otherwise.
Configure Webhook URL in studio Settings. Real Talk Studio POSTs JSON on completion; all fields are nested under data. See Webhook config for the full payload, field reference, extCustId behaviour, and example receivers (Zapier, Node.js, Postgres).Webhooks are optional — session data is always available via Session history → Download CSV. Pass extCustId on the launch URL if you need to join scores to LMS users.
After feedback loads, the iframe notifies the parent frame:
A SCORM wrapper can listen and set cmi.core.lesson_status to completed. Validate event.origin in production. postMessage signals completion only — scores travel via webhook or CSV, not postMessage. A new-tab link does not send this message; complete the Storyline/Rise module with your usual visited / Continue logic.Some platforms (e.g. Evolve LMS) use MessageChannel; the embed also exposes window.notifyAssessmentCompleted().
Real Talk Studio does not assign LMS pathways directly. To route learners by weak skills, a webhook receiver should store skillsFeedback and extCustId, apply mapping rules, and write back via the LMS API.To compare pre- and post-training scores for the same learner, store the first completion keyed by extCustId + roleplaySlug and diff when the second arrives. Embedded sessions do not use the in-app “previous score” API — comparison happens in your systems.
  • Option 1 (simplest): new-tab anonymous share link from Storyline or Rise.
  • Option 2: iframe / Web Object — only after a mic + firewall pilot.
  • Advanced (on 1 or 2): append extCustId at launch; named tracking in Real Talk Studio; optional webhook to the LMS backend.
  • Custom SCORM wrapper around an iframe is extra authoring work, not a Real Talk Studio zip. xAPI and LTI are not standard today.

Webhook config

For IT: automatic score delivery, learner ID (extCustId), and Zapier-style setups.

Firewall configuration

For IT: network requirements on corporate Wi‑Fi.

Troubleshooting

Microphone, browser, and connection issues inside the course.

Organization & studio permissions

Studio access, credits, and allowed embed domains.

FAQ

No — if you use the anonymous share link (Studio → ⋮ → Share link → Share anonymously). That URL uses studio credits. Share with logged-in users does require a studio account; do not put that URL in the LMS.
Not for a basic new-tab link plus CSV reporting. Involve IT if you need learner IDs on every session, automatic gradebook updates, corporate firewall access, iframe framing, or SCORM completion to fire automatically.
No. Webhooks are optional. CSV export from Session history includes scores, skills, and session details. Use a webhook only when results must flow into another system immediately — and pass extCustId if those results must attach to a person.
Not as a standard download. Publish your Storyline or Rise course as SCORM and add a Real Talk Studio link (or iframe) inside it. Enterprise customers can discuss custom SCORM packaging.
That is usually nested-iframe permissions, not a Real Talk Studio bug. Switch to a new-tab link, or ensure every frame in the chain allows camera and microphone. Test in the published LMS course, not only in Preview.
Not directly from Real Talk Studio. The roleplay shows feedback to the learner. To change LMS pathways automatically, IT needs to receive scores (webhook or CSV import) and apply rules in the LMS.
They see full feedback for the session they just completed. Comparing an earlier diagnostic to a final assessment is something you build in reporting — export CSV or ask IT to store webhook history — unless you surface it in a custom LMS page.
Very short sessions may be flagged as too short to score. Treat these as incomplete and ask the learner to try again with a fuller conversation.