> For the complete documentation index, see [llms.txt](https://docs.supademo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.supademo.com/use-cases/training-and-onboarding.md).

# Training & Onboarding

How training, onboarding, and support teams use Supademo: self-paced learning paths, in-app product tours, and interactive support documentation.

Customer success, L\&D, support, and operations teams use Supademo to turn the product itself into the training material: interactive demos that people click through instead of documents they skim, delivered as self-paced onboarding paths, in-app tours, LMS courses via [SCORM](https://docs.supademo.com/share/exports/export-to-scorm), and help articles that walk users through the fix. One recording becomes every format. A single captured workflow exports as a SCORM package for the LMS, an SOP for the wiki, an embed for the help center, and an in-app tour, and editing the master updates all of them. This page maps each training job to the features that do it, with a full guide per use case below.

{% @supademo/embed url="<https://app.supademo.com/demo/cm6szaj7w010vpe1qqzw7qwyk>" demoId="cm6szaj7w010vpe1qqzw7qwyk" %}

## Which Supademo features matter most for training teams

| Job to be done                          | Supademo feature                                                                                                                                                                                                 | Where to start              |
| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
| Onboard customers without live sessions | [Showcase](https://docs.supademo.com/share/multi-demo-sharing/showcase-collection)s with checklist layout, chapters, [conditional branching](https://docs.supademo.com/customize/chapters/conditional-branching) | Self-paced onboarding guide |
| Deliver training through your LMS       | SCORM export                                                                                                                                                                                                     | Export to SCORM             |
| Guide users inside the product          | In-app tours and embeddable [Demo Hubs](https://docs.supademo.com/share/multi-demo-sharing/demo-hub) with categories                                                                                             | In-app product tours        |
| Deflect how-do-I tickets                | Demos embedded in Zendesk, Intercom, GitBook, Notion                                                                                                                                                             | Support documentation guide |
| Keep written docs in sync               | SOP export from any demo                                                                                                                                                                                         | SOP export                  |
| Train global teams from one source      | [AI translations](https://docs.supademo.com/customize/personalize/ai-translations-hub) in 50+ languages, [AI voiceovers](https://docs.supademo.com/customize/voiceovers)                                         | AI translations             |
| Prove training happened                 | Completion and per-step drop-off, lead-level analytics                                                                                                                                                           | Session metrics             |

## Workflow: build an onboarding path new users finish

1. Record each core workflow as its own short guided demo, one task per demo.
2. Assemble them into a Showcase using the checklist layout, so learners see ordered stages and their own progress. Mix in videos and PDFs where a demo is not the right medium.
3. Add [form chapter](https://docs.supademo.com/customize/chapters/forms-and-lead-capture)s as knowledge checks and to identify each learner in analytics.
4. Share one link in the welcome email, embed it in the app, and watch completion per demo to find where new users stall.

The complete pattern is in Self-paced onboarding.

## Workflow: answer support questions before they become tickets

1. Record the top ticket-driving tasks as 5 to 8 step demos.
2. Embed them in the matching help center articles in Zendesk, Intercom, GitBook, or Notion, and add the SOP export as the written version beside each.
3. Surface the same demos inside the product through a Demo Hub so users get answers without leaving the app.
4. When the UI changes, update the master demo once; every embed refreshes.

Details in Support documentation.

## Guides in this section

* In-app product tours: contextual walkthroughs inside your application.
* Self-paced onboarding: structured learning paths for customers and new hires, LMS-ready via SCORM.
* Support documentation: interactive help articles that deflect tickets.

## Frequently asked questions

### What is the best interactive demo software for customer onboarding?

Evaluate on whether one recording can serve every onboarding surface: a self-paced path, an in-app tour, an LMS course, and a help article. Supademo does this from a single demo through Showcases with checklist layouts, in-app tours and Demo Hubs, SCORM export, SOP export, and embeds, with completion analytics identifying where each learner stops.

### Can I use interactive demos in an LMS?

Yes. Supademo exports demos as SCORM packages that upload to SCORM-compliant LMSes, so interactive walkthroughs slot into existing courses with the LMS handling enrollment and completion records. See Export to SCORM.

### How do interactive demos reduce support tickets?

They let users perform the fix instead of reading about it. A demo embedded in the help article walks the user through each click at their own pace, the SOP export covers readers who want text, and per-step analytics show support teams exactly where users get confused, which is where the next demo should go.
