If you have been asked how to add branching rise interactions, the short answer is this: Rise 360 does not support true page-to-page branching by itself. To create real decision-based paths, build the branching interaction in Storyline 360 and then insert it into a Rise 360 lesson.
That matters because many developers lose time looking for branching settings inside Rise that do not exist. Rise is excellent for clean, responsive lessons, but Storyline handles variables, triggers, and slide-based navigation. Use each tool for what it does best.
How To Add Branching Rise Content The Right Way
Start in Storyline 360. Open a new project and sketch the decision path before you build anything. Keep it simple at first: one introduction slide, one question slide with two or three choices, and one result slide for each choice.
On the question slide, add buttons or clickable objects for each learner choice. Then create triggers so each button jumps to the correct slide. For example, if the learner selects Option A, jump to Slide 3. If the learner selects Option B, jump to Slide 4. This is the core of branching.
If you want learners to loop back and try again, add a button on the feedback slide that returns them to the choice slide. If you want the scenario to continue, send each branch to a new decision point. That is where Storyline becomes more useful than Rise alone.
Build The Branching Logic In Storyline 360
Use slide titles that clearly identify the path, such as Good Choice, Risky Choice, or Needs Review. When a project grows, naming slides well makes editing much faster.
Preview the interaction often. Click each choice and confirm that every branch lands where you expect. Most branching errors come from one wrong trigger or a button copied from another slide without updating its destination.
If you need scoring, you can add variables or quiz slides in Storyline. If you only need a realistic scenario, simple jump-to-slide triggers are usually enough. That lighter approach is easier to maintain when deadlines are tight.
Add The Storyline Block To Rise 360
Once the branching is working, publish the Storyline project to Review 360 or export it for Rise 360 insertion, depending on your workflow. In Rise 360, open the lesson where the interaction should appear, add an Interactive block, and choose the Storyline block.
Upload or attach the published Storyline content. After it appears in the lesson, preview the Rise course and test the branch again inside Rise, not just in Storyline. A project can work perfectly in Storyline preview but still need sizing adjustments once embedded.
Keep the surrounding Rise lesson focused. Introduce the scenario before the Storyline block, and follow it with a short knowledge check or reflection. That keeps the branching activity from feeling disconnected.
What To Watch For
The main trade-off is responsiveness. Rise 360 is fully responsive, but embedded Storyline content scales inside a responsive page rather than becoming truly responsive itself. On phones, complex branching slides can feel cramped. If mobile use is a priority, design Storyline slides with larger buttons, less text, and fewer on-screen objects.
Also decide whether you need true branching or just the appearance of choice. In some cases, Rise button stacks, labeled graphics, or separate lessons are enough. But if learners must make decisions and experience different consequences, Storyline is the right answer.
A good branching interaction does more than look impressive. It lets learners practice judgment before the real-world moment arrives. Build the path carefully, test every choice, and your Rise course becomes far more than a linear page-turner.