For instructional designers and L&D teams

eLearning Scenario Voice-Over with a Voice for Every Character

Free to sign up, no card. Creating audio uses credits.

Paste a branching scenario or a role-play script. FullCastBook finds every character, gives each a different AI voice, and exports one audio file per scene or branch for your authoring tool.

Who it's for
  • Customer service
  • Compliance and conduct
  • Leadership conversations
Alice's Adventures in Wonderland — The Cheshire Cat
NarratorNaomiAliceAbbyCheshire CatSnik How it works
Alice's Adventures in Wonderland cover

Lewis Carroll

Alice's Adventures in Wonderland

Alice asks the grinning Cheshire Cat for directions — and gets none.

The Cat only grinned when it saw Alice. It looked good-natured, she thought; still it had very long claws and a great many teeth, so she felt it ought to be treated with respect.

Cheshire Puss, would you tell me, please, which way I ought to go from here?

Cheshire CatSnikSly

That depends a good deal on where you want to get to.

I don't much care where—

Cheshire CatSnikSly

Then it doesn't matter which way you go.

—so long as I get somewhere.

Cheshire CatSnikSly

Oh, you're sure to do that, if you only walk long enough.

~1 min · 3 voices · ready to play7
Free preview, no signup to listen. Your own chapters & export need an account and credits.I'm ready →
AI voices to cast
137
70 standard · 67 premium
file types in
5
EPUB · PDF · DOCX · TXT · MD
ways out
3
M4B with chapters · MP3 · ZIP
voice models
4
Gemini · ElevenLabs

Step-by-step guide

How to use eLearning Scenario Voice-Over

No card to sign up, nothing to install.

  1. Paste the scenario script

    Paste it, or upload the DOCX or PDF from your storyboard. Put each scene or branch under its own heading and a name before each line.
  2. Check who says each line

    Lines are assigned to the customer, the employee, the coach and the narrator automatically. Move any line that's on the wrong character.
  3. Cast and direct

    Pick a contrasting voice per character and add notes like [frustrated, talking fast] so the difficult moments sound difficult.
  4. Export per branch

    Listen, regenerate any line that misses, then download a ZIP with one MP3 per scene or branch to drop onto your slides.

Hear an example

Hear a branching customer-service scenario made in FullCastBook

Generated from the script below with the studio's own voices and settings, one voice per speaker, joined the way an export joins lines. No edits afterwards.

Customer service scenario: the double charge

Narrator · Dana · Sam · Coach · Voices: Gemini 3.8 Flash TTS

0:00 / 0:50
  1. NarratorScenario two. A customer calls about a double charge on her card. Listen, then choose how Sam should respond.Schedar · neutral, instructional
  2. DanaI've been charged twice for the same order, and this is the third time I've called about it.Pulcherrima · frustrated, talking fast
  3. SamI'm sorry, that's frustrating. Can I take your order number so I can see both charges?Achird · calm, friendly
  4. Dana[sigh] It's four four seven one nine. Again.Pulcherrima · tired, clipped
  5. SamThanks, Dana. I can see both payments. One is a pending hold, and it should drop off within five working days.Achird
  6. DanaShould? I need that money back this week.Pulcherrima · sharper, cutting in
  7. NarratorOption B. Sam promises a refund today.Schedar
  8. SamDon't worry, I'll refund it right now. It'll be back today.Achird · confident, too quick
  9. CoachThat sounds kind, but Sam can't promise it. A pending hold isn't his to release. Try again, and explain what he can do.Vindemiatrix · warm, steady

eLearning Scenario Voice-Over

Features & capabilities

What you get, from manuscript to finished audiobook.

  • Every character found

    Names before lines, dialogue tags and turn-taking decide who speaks. A scenario with a customer, two staff members and a coach is cast in one pass.
  • One file per branch

    Each heading in your script becomes a chapter, and the ZIP export gives you one MP3 per chapter: Scene 1, Branch 1A, Branch 1B, and so on.
  • Emotion that teaches

    Write [frustrated], [defensive] or [relieved] before a line and add [sigh] where it fits, so learners hear how tone changes the conversation.
  • Policy changed? Fix one line

    Edit the line that's out of date, regenerate only that line, and export again. The rest of the scenario stays exactly as approved.
  • Same voice in every branch

    A character keeps the voice you chose across every scene and branch of the project, so the customer in Branch 3C sounds like the one in Scene 1.
  • Localised versions

    Voices read many languages, so a translated script can be voiced with the same workflow. English works best today.

Script template

A branching scenario script you can copy

Replace the text in brackets with your own, paste it into the studio, and every speaker gets a voice.

Branching scenario script template

Copy this, replace the placeholders in square brackets, and paste it in or save it as a DOCX. Notes like [frustrated] are delivery directions; keep them. Each heading becomes its own MP3.

# Scene 1: [SITUATION IN A FEW WORDS]
NARRATOR: [Set the scene in one or two sentences: who, where, what's at stake.]
[CUSTOMER]: [frustrated] [Opening line: the problem, in their words.]
[EMPLOYEE]: [A neutral first response.]
[CUSTOMER]: [A detail that raises the stakes.]
NARRATOR: What should [EMPLOYEE] say next?

# Branch 1A: [BEST CHOICE]
[EMPLOYEE]: [calm] [Acknowledge the feeling, then the next step.]
[CUSTOMER]: [calmer now] [Reaction that shows it worked.]
COACH: [Why this works, in one or two sentences.]

# Branch 1B: [PLAUSIBLE BUT WRONG]
[EMPLOYEE]: [confident, too quick] [The tempting mistake: over-promising, skipping a check.]
[CUSTOMER]: [Reaction that hints at the problem later.]
COACH: [What went wrong and what to try instead.]

# Branch 1C: [CLEARLY WRONG]
[EMPLOYEE]: [flat, dismissive] [The response that breaks the rule or the relationship.]
[CUSTOMER]: [sharper, interrupting] [Escalation.]
COACH: [The consequence, and the policy it breaks.]

Keep each line under about 25 words. Put the exact policy wording on screen, not in the voice-over.

Use cases

What can you make with eLearning Scenario Voice-Over?

Where authors and storytellers put it to work.

  • Customer service

    Complaints, refunds and escalations, with a customer who sounds upset and an agent whose response the learner chooses.
  • Compliance and conduct

    Short dialogues where a colleague asks for something they shouldn't, so learners practise saying no before it happens for real.
  • Leadership conversations

    Feedback, performance talks and difficult one-to-ones between a manager and a report, each in a voice of their own.
  • Sales role-plays

    Discovery calls and objection handling, with a sceptical buyer and a coach who explains what worked.

Hear example character voices

Demo performances. In the studio you cast from standard and premium voice lists.

More examples
On this page
  1. 1eLearning scenario voice-over without booking a cast
  2. 2Script the branches so each one becomes its own file
  3. 3Casting the customer, the employee and the coach
  4. 4Making difficult conversations sound difficult
  5. 5Updates, captions and what to expect
  6. 6Credits and licensing

In depth

eLearning scenario voice-over without booking a cast

eLearning scenario voice-over is what turns a branching scenario from a reading exercise into practice. Learners hear the customer's irritation, the colleague's pressure or the manager's hesitation, and they respond to the tone as well as the words. That's hard to get from on-screen text, and expensive to get from a recording session with several actors every time a branch is added or a policy changes.

FullCastBook gives you a cast from a script. Paste the scenario, and every character is detected and given a different AI voice, with a narrator for any setup text. You review the cast, add direction where a line needs it, and export the audio scene by scene. It's built on the same studio as our multiple voices text to speech tool, organised here for the way training scenarios are actually built: lots of short scenes, branches that reuse the same characters, and frequent revisions.

Script the branches so each one becomes its own file

Authoring tools attach audio slide by slide, so the useful unit is a scene or a branch, not one long track. Write each one under its own heading ("Scene 1: The call", "Branch 1A: Acknowledge first", "Branch 1B: Jump to the fix") and put a speaker name before every line. Each heading becomes a chapter, and the ZIP export gives you one MP3 per chapter, named and ordered the way your storyboard is.

There are no per-line files, so if a single slide needs just one line, give that line its own heading, or split the MP3 in an audio editor. The export is ordinary MP3, which most authoring tools, including Articulate Storyline, Adobe Captivate and Rise, let you import onto a slide or block. FullCastBook doesn't publish SCORM packages or connect to your LMS; it produces the voice tracks your course is built around.

Casting the customer, the employee and the coach

Every scenario has the same three jobs: the other person (a customer, a colleague, a candidate), the employee whose choices the learner controls, and someone who frames or debriefs the scene, such as a narrator or a coach. Give them voices that differ clearly in pitch, age and energy, so a learner who glances away from the screen still knows who's talking. Keep the coach calm and even; it's the voice learners will trust for the right answer.

Think about who the learner is, too. If your audience is front-line staff, the employee character should sound like a peer, not a polished presenter. Audition two or three voices per role before you settle, since voice samples are free to hear. Once chosen, a character keeps that voice in every branch of the project, which matters more than you'd expect: a customer who changes voice between branches breaks the illusion that the learner's choice affected the same person.

Making difficult conversations sound difficult

The wrong branch has to sound wrong. If the employee over-promises, rushes or dismisses a concern, write it that way and direct it: [confident, too quick], [flat, reading a script], [defensive]. Give the customer a reaction that rises or falls with the choice: [calmer now] after a good response, [sharper, interrupting] after a poor one. A [sigh] in the right place does more than a paragraph of feedback text.

Keep lines short and spoken. Real people don't recite policy in full sentences, and learners can't hold a forty-word line in their heads while choosing an answer. Put the exact policy wording on screen and let the characters talk the way people talk. More on writing these notes is in AI voice emotion tags, and if you want to hear a full script read through before you build the slides, an AI table read works the same way.

Updates, captions and what to expect

Training content changes: a refund window moves from 14 to 30 days, a product gets renamed, a regulator updates guidance. Edit the affected line, regenerate only that line, and export the chapter again. Product names, acronyms and internal jargon are worth checking early; write them the way they should be said, and see the pronunciation guide for the techniques that work.

Be clear about the limits. FullCastBook makes audio only: no video, no avatars, no lip-sync, and no caption or timing files. Your script is already the transcript, so paste it into your authoring tool's closed captions. There's no voice cloning, so you can't reproduce a particular trainer's or executive's voice; you cast from the standard and premium voice lists.

Credits and licensing

Signing up is free and needs no card. Generating audio uses credits, counted by the characters voiced, so a short scenario costs little; regenerating a line uses credits again. Compare the plans against the size of your course library.

As between you and us, you own the audio you export and can use it under our terms of service, in internal training or in courses you build for clients. Make sure you have the rights to the script you voice, and don't write scenarios that imitate a real, identifiable person without their consent.

Tips

Tips for scenario voice-over learners believe

  1. Name headings like your storyboard

    Use the same IDs as your slides ("Scene 2", "Branch 2B"). Each heading becomes a chapter and an MP3, so the files line up with the course without renaming.
  2. Three clearly different voices

    The other person, the employee and the coach should differ in pitch, age and energy. Keep the coach or narrator the calmest voice in the scene.
  3. Direct the wrong answers

    A poor choice should sound poor: [too quick], [defensive], [reading a script]. Give the customer a matching reaction so the consequence is audible.
  4. Short, spoken lines

    Learners choose an answer while remembering what was said. Keep lines short, use contractions, and leave long policy text on screen.
  5. Check names and acronyms first

    Generate one line with your product names, system names and acronyms before the whole course. Write tricky ones as they're said, e.g. "S-L-A" or "sequel".
  6. Captions come from your script

    FullCastBook doesn't make caption files. Paste the script into your authoring tool's closed captions; it already matches the audio word for word.
  7. Fix one line after a review

    When a reviewer or legal changes a sentence, edit that line, regenerate it and re-export the chapter. The rest of the approved audio stays untouched.

FAQ

eLearning Scenario Voice-Over: FAQ

Something not covered here? Email us at support@fullcastbook.com

Can AI do the voice-over for a branching scenario with several characters?

Yes. Paste the scenario with a name before each line, and every character is detected and given a different AI voice. You check the cast, add direction where needed and export the audio.

How do I get a separate audio file for each slide or branch?

Put each scene or branch under its own heading. Each heading becomes a chapter, and the ZIP export gives you one MP3 per chapter. There are no per-line files, so give a single line its own heading or split it in an audio editor.

Will the audio work in Storyline, Captivate or Rise?

Yes, as ordinary MP3 files that you import onto a slide or block. FullCastBook doesn't publish SCORM or connect to an LMS; it makes the voice tracks.

Can the characters sound angry, nervous or upset?

Yes. Write a note like [frustrated, talking fast] or [nervous, hesitant] before a line, and add sound tags such as [sigh] where they help. Regenerate the line if the delivery misses.

What happens when the policy in a scenario changes?

Edit the affected line, regenerate only that line and export the chapter again. The rest of the approved audio stays the same.

Does it make captions, avatars or lip-synced video?

No. It makes audio only. Your script is the transcript, so paste it into your authoring tool's captions.

Is eLearning scenario voice-over free to try?

Signing up is free with no card, and voice samples are free to hear. Generating audio uses credits; a short scenario costs little. See pricing.

Can I use the audio in courses for clients?

You own the audio you export, and use follows our terms of service, including client work. Make sure you have the rights to the script.

Give every character in your scenario a voice.

Paste a role-play, cast the voices and export one file per branch. Free to sign up; creating uses credits.