Use cases

Role-playing training

Practise the conversation, not the slide about it

A difficult customer, a refusal, a diagnosis delivered badly. People learn those by making the call and living with it — not by watching someone else make it.

See what Wall of Voice could look like for your audience.

3. Tell me what that song means…Add

Question

Tell me what that song means to you

How people can answer

Record a videoWrite a comment

This is what your audience taps.

  • The choice decides the scene

    Each answer names where it leads: another scene, an ending, or a link out. One question can branch while the rest of the scenario runs straight.

  • They say it out loud

    A step can ask for a spoken answer rather than a click. "Now tell them" is the whole exercise, and it comes back with a transcript.

  • Decisions on the frame

    Put the options on the video itself as buttons, timed to appear when the moment arrives, and point each one at a different outcome.

  • Endings that are endings

    A path can stop on its last frame, on purpose. Losing the customer is a legitimate outcome, and the scenario is allowed to say so.

  • Which choice loses people

    Per-step engagement and drop-off show where a scenario stalls — usually one badly-worded option, not the whole exercise.

  • One row per person

    Every path someone took, every answer they recorded, kept together with them. Reviewing a trainee is reading one row, not hunting files.

What actually happens

The scenario is steps with a video and a question underneath, and an answer's destination outranks the step's. That is why you can build the whole thing as a straight sequence first and make exactly one question branch later — the step's own ending stays the fallback for everyone who did not take a route of their own.

Every destination speaks one vocabulary — play the next step, jump to a specific one, end here, open a URL — whether it is an answer, a button on the frame, or the end of a scene. Learning it once is the whole learning curve.

Publishing checks the graph before a trainee does: a jump to a scene you deleted, a question that routes nowhere, a step nobody can reach. You get the list of what blocks it and where, instead of a dead end discovered mid-exercise.

Questions people ask

Do people need an account to take a scenario?
No. It opens from a link — open to anyone, or a personal invitation that is resumable, so someone can stop halfway and come back to where they left.
Can a scenario branch on a spoken answer?
Routing is driven by choice questions, where each answer names its destination. A spoken answer is recorded, transcribed and reviewed, but it is the choice that decides the path.
Can I see which route each person took?
Yes. Engagement and progress are recorded per step, and each person's answers are kept together with them, so you can read one trainee's path end to end.
Can I run the same scenario in two languages?
Yes. A project carries language versions, each with its own publication state, so you can ship one language and keep another in draft rather than cloning the scenario.
Can it live inside our own learning site?
Yes. The player embeds on your page, with the embed locked to your domains or gated by a token, and webhooks fire as answers arrive.

Your audience has something to say.

Give them a way to say it. We'll walk through what Wall of Voice could look like for your audience.

See what Wall of Voice could look like for your audience.