Learning Paths
A learning path is an ordered sequence of scenarios. Use paths to onboard new hires (Week 1 — basics, Week 2 — escalations), to certify on a new product, or to coach a specific skill (De-escalation track).
Anatomy of a path
| Field | What it does |
|---|---|
| Name | Short, clear — New hire — week 1. |
| Description | Why this path exists, who it’s for. |
| Steps | Ordered scenarios. Each step can require the previous to pass. |
| Pass threshold | Minimum rubric score to count a step as completed. |
| Reattempts | How many times a trainee can retry a failed step. |
| Due date | Optional. Shown to trainees and rolled up in reports. |
Sequencing rules
| Rule | Use it for |
|---|---|
| Strict | Each step must be passed before the next unlocks. Best for onboarding. |
| Open | Trainee picks any step in any order. Best for skill drills. |
| Mix | First N steps strict, rest open. |
Pass thresholds are deliberately tunable. If your rubric is strict, a 70% threshold may be plenty; if it’s lenient, 85% might be the right floor. Calibrate after the first cohort runs through.
Build a path
Open Training
Go to Training → Learning Paths → New path.
Name and describe
Make the name something a trainee would recognize on their dashboard.
Add steps
Drag scenarios into the path in order. Each step shows its rubric and an estimated duration.
Set thresholds and reattempts
Per-step or path-wide. Reattempts can be unlimited or capped — capped is more honest.
Add a due date (optional)
Trainees see a countdown; managers get a “stalled trainees” alert if anyone falls behind.
Save
Assign to trainees
Open the path and click Assign. Pick individuals or whole teams. Each trainee gets:
- A notification.
- A row on their My Training dashboard.
- A countdown if there’s a due date.
- An auto-generated reminder email if they don’t start within 3 days.
Track progress
The path’s Progress tab shows:
- Completion rate.
- Median rubric score per step.
- Time-to-completion distribution.
- Step-level failure heatmap (which scenarios are tripping people up?).
Use the heatmap to find scenarios that are too hard, too easy, or unclear — those are the ones to rewrite.
Cloning and versioning
Paths can be cloned. Clone before tweaking if you have an active cohort — otherwise their assignment will move under their feet. Use Versions to see what changed when.
Open in Omniflow
Related
| If you want to… | Go to |
|---|---|
| Build the scenarios in your path | Scenarios |
| Run a practice call | Practice Calls |
| Review attempts | Reviews & Coaching |