---
title: "Multi-Character Dialogue Prompts: Who Speaks When | imaginary.app"
description: "A Imaginary-ready “who speaks when” template for multi-character dialogue prompts—plus rewrites, examples, and fixes for speaker swaps and timing drift."
url: https://www.imaginary.app/blog/kling-30-style-multi-character-dialogue-prompts-in-veo3gen-a-clear-who-speaks-wh
---

Prompt Engineering & Creative Control2026-04-05By [Imaginary team](https://www.imaginary.app/editorial-policy)9 min read

# Multi-Character Dialogue Prompts: Who Speaks When

A Imaginary-ready “who speaks when” template for multi-character dialogue prompts—plus rewrites, examples, and fixes for speaker swaps and timing drift.

On this page

- [Why multi-character dialogue breaks (and what “role labeling” fixes)](#why-multi-character-dialogue-breaks-and-what-role-labeling-fixes)
- [The 7-line “Who Speaks When” template (Imaginary version)](#the-7-line-who-speaks-when-template-imaginary-version)
- [Fill-in template (with placeholders)](#fill-in-template-with-placeholders)
- [How to name characters so the model doesn’t swap voices](#how-to-name-characters-so-the-model-doesnt-swap-voices)
- [Use “anchor names” and distinct visual IDs](#use-anchor-names-and-distinct-visual-ids)
- [Avoid pronoun chains](#avoid-pronoun-chains)
- [Keep each line on its own line](#keep-each-line-on-its-own-line)
- [Timing control: beats, pauses, interruptions, and overlap](#timing-control-beats-pauses-interruptions-and-overlap)
- [What to write](#what-to-write)
- [What to avoid](#what-to-avoid)
- [Scene blocking for dialogue: where each character is + what they’re doing while speaking](#scene-blocking-for-dialogue-where-each-character-is--what-theyre-doing-while-speaking)
- [Three rewrites of the same scene (messy → labeled → labeled + blocking + beats)](#three-rewrites-of-the-same-scene-messy--labeled--labeled--blocking--beats)
- [1) Messy paragraph prompt (what causes swaps)](#1-messy-paragraph-prompt-what-causes-swaps)
- [2) Labeled dialogue prompt (who speaks when)](#2-labeled-dialogue-prompt-who-speaks-when)
- [3) Labeled + blocking + beat markers (best control)](#3-labeled--blocking--beat-markers-best-control)
- [Copy/paste examples (2-person, group, ad call-and-response)](#copypaste-examples-2-person-group-ad-call-and-response)
- [Two-person friendly banter (quick pacing)](#two-person-friendly-banter-quick-pacing)
- [Three-person group scene (explicit turn order)](#three-person-group-scene-explicit-turn-order)
- [Ad-style call-and-response (tight structure)](#ad-style-call-and-response-tight-structure)
- [Common failures and exact fixes (troubleshooting table)](#common-failures-and-exact-fixes-troubleshooting-table)
- [A minimal iteration checklist (change only 1 variable per rerun)](#a-minimal-iteration-checklist-change-only-1-variable-per-rerun)
- [Ethical + disclosure reminders for synthetic dialogue](#ethical--disclosure-reminders-for-synthetic-dialogue)
- [FAQ](#faq)
- [What’s the single biggest improvement for a multi character dialogue prompt?](#whats-the-single-biggest-improvement-for-a-multi-character-dialogue-prompt)
- [Should I write dialogue as a screenplay format?](#should-i-write-dialogue-as-a-screenplay-format)
- [How do I reduce timing drift between lines?](#how-do-i-reduce-timing-drift-between-lines)
- [Do I need shot language like “shot-reverse-shot”?](#do-i-need-shot-language-like-shot-reverse-shot)
- [Related reading](#related-reading)
- [CTA: Build this into your pipeline](#cta-build-this-into-your-pipeline)
- [Sources](#sources)

## [Why multi-character dialogue breaks (and what “role labeling” fixes)](#why-multi-character-dialogue-breaks-and-what-role-labeling-fixes)

Multi-speaker scenes fail for a simple reason: the model has to juggle **identity**, **turn order**, and **cinematic coverage** at the same time. If any of those are ambiguous, you’ll see classic issues—wrong person “talking,” lines merged together, reactions missing, or the pacing drifting away from what you intended.

A practical way to reduce ambiguity is to prompt like you’re **directing a scene**, not listing ideas. This lines up with guidance from the Kling 3.0 prompting playbook: it performs best when prompts read like scene direction, with clear structure and intentional shot language rather than a loose list of objects. (<https://blog.fal.ai/kling-3-0-prompting-guide/>)

Even if you’re generating in Imaginary, the same concept transfers well: **explicit role labeling** (“who speaks when”) makes it easier for the model to keep characters, audio intent, and mouth movement aligned—especially in shot-reverse-shot dialogue (a cinematic pattern Kling explicitly understands). (<https://blog.fal.ai/kling-3-0-prompting-guide/>)

> **Behavior note (as of 2026-04-05):** In Imaginary-style workflows, clearer turn-taking and per-line speaker labels generally reduce speaker swaps and timing drift. Treat this as a prompting best practice rather than a guarantee—outputs can still vary run to run.

## [The 7-line “Who Speaks When” template (Imaginary version)](#the-7-line-who-speaks-when-template-imaginary-version)

Copy/paste this and fill the brackets. The goal is to keep the prompt **structured**, **non-ambiguous**, and **line-based**.

### [Fill-in template (with placeholders)](#fill-in-template-with-placeholders)

1. **SCENE:** `[location, time of day, mood, genre]`

2. **CAMERA / COVERAGE:** `[shot-reverse-shot / two-shot / over-the-shoulder; lens feel; movement]`

3. **CHARACTER A (anchor):** `Name: [A_NAME]. Visual ID: [wardrobe/shape]. Voice: [tone/pace/accent style].`

4. **CHARACTER B:** `Name: [B_NAME]. Visual ID: [wardrobe/shape]. Voice: [tone/pace/accent style].`

5. **BLOCKING:** `[where A stands/sits + what A does while listening] | [where B stands/sits + what B does while listening]`

6. **DIALOGUE (one line per turn; no pronouns without names):**

   - `[00:00–00:02] [A_NAME] (action tag): "[line]"`
   - `[00:02–00:04] [B_NAME] (action tag): "[line]"`
   - `[00:04–00:05] [A_NAME] (interrupts): "[line]"`

7. **CONTINUITY NOTES:** `[must-stay-the-same details: wardrobe, props, labels, silhouettes, proportions]`

Why this structure works:

- It pushes “cinematic intent” up front, which improves clarity. (<https://blog.fal.ai/kling-3-0-prompting-guide/>)
- It uses explicit shot language (e.g., shot-reverse-shot), which the model is built to interpret. (<https://blog.fal.ai/kling-3-0-prompting-guide/>)
- Continuity notes are a proven way to preserve consistent details (e.g., labels, silhouettes, proportions) across a sequence. (<https://invideo.io/blog/hidden-secrets-of-kling-ai/>)

## [How to name characters so the model doesn’t swap voices](#how-to-name-characters-so-the-model-doesnt-swap-voices)

Voice swapping usually starts with **identity ambiguity**. Use these rules:

### [Use “anchor names” and distinct visual IDs](#use-anchor-names-and-distinct-visual-ids)

- Prefer short, unique names: `Mara` and `Dex`, not `Anna` and `Hannah`.
- Pair each name with a **visual identifier** that’s hard to confuse: “red scarf + shaved sidecut” vs “tan blazer + round glasses.”

### [Avoid pronoun chains](#avoid-pronoun-chains)

Bad: “He denies it. She interrupts him. He sighs.”

Better: “Dex denies it. Mara interrupts Dex. Dex sighs.”

### [Keep each line on its own line](#keep-each-line-on-its-own-line)

Don’t bury dialogue inside a paragraph. In multi-shot prompting, clear labeling per unit (shot, or line) is recommended instead of compressing everything together. (<https://blog.fal.ai/kling-3-0-prompting-guide/>)

## [Timing control: beats, pauses, interruptions, and overlap](#timing-control-beats-pauses-interruptions-and-overlap)

You can’t force perfect millisecond timing in every generation, but you _can_ improve pacing clarity.

### [What to write](#what-to-write)

- **Beat markers:** Use simple ranges like `[00:02–00:04]` per line.
- **Pauses:** Write `(beat)` or `(short pause)` once, not repeatedly.
- **Interruptions:** Mark them explicitly: `(interrupts)`.
- **Reactions while listening:** Add action tags to the _listening_ character too: “Mara (listens, jaw tight).”

### [What to avoid](#what-to-avoid)

- Long monologues with multiple intentions. Keep **one intent per line**.
- Vague pace directions like “talk naturally” without specifying _how_ (fast/slow, calm/tense, clipped/warm).

## [Scene blocking for dialogue: where each character is + what they’re doing while speaking](#scene-blocking-for-dialogue-where-each-character-is--what-theyre-doing-while-speaking)

Dialogue scenes fall apart when the model has to guess where everyone is. Add simple blocking:

- **Positions:** “Mara stands by the fridge; Dex leans on the counter.”
- **Eye-lines:** “They maintain eye contact; Dex looks away on the last word.”
- **Hands/props:** “Mara holds a receipt; Dex fidgets with a keyring.”

If you’re generating a sequence, keep blocking consistent and add continuity notes—continuity can cover details like product labels, character silhouettes, or object proportions. (<https://invideo.io/blog/hidden-secrets-of-kling-ai/>)

## [Three rewrites of the same scene (messy → labeled → labeled + blocking + beats)](#three-rewrites-of-the-same-scene-messy--labeled--labeled--blocking--beats)

Below is the same two-person argument rewritten three ways.

### [1) Messy paragraph prompt (what causes swaps)](#1-messy-paragraph-prompt-what-causes-swaps)

A tense kitchen argument at night. Two people argue about a missing package. Make it cinematic and emotional with closeups and realistic audio. One person accuses the other, then the other denies it, then they both calm down.

### [2) Labeled dialogue prompt (who speaks when)](#2-labeled-dialogue-prompt-who-speaks-when)

**SCENE:** Night, small apartment kitchen, tense but grounded.

**CHARACTER A:** Mara, red scarf, tired eyes. Voice: controlled, clipped.

**CHARACTER B:** Dex, tan blazer, neat hair. Voice: defensive, fast.

**DIALOGUE:**

- Mara: “Dex, the package is gone. Don’t tell me you didn’t touch it.”
- Dex: “Mara, I didn’t. I swear I didn’t even see it.”
- Mara: “Then where is it?”
- Dex: “I don’t know. Stop looking at me like that.”

### [3) Labeled + blocking + beat markers (best control)](#3-labeled--blocking--beat-markers-best-control)

**SCENE:** Night, cramped apartment kitchen, overhead light buzzing, tense realism.

**CAMERA / COVERAGE:** Shot-reverse-shot dialogue with occasional tight close-ups; slow handheld drift.

**CHARACTER A (anchor):** Name: Mara. Visual ID: red scarf, smudged eyeliner. Voice: low, clipped, restrained anger.

**CHARACTER B:** Name: Dex. Visual ID: tan blazer, round watch. Voice: defensive, quick, slightly breathy.

**BLOCKING:** Mara stands by the fridge gripping a printed delivery email. Dex leans on the counter holding a keyring, tapping it.

**DIALOGUE (one line per turn):**

- \[00:00–00:02] Mara (stares at Dex): “Dex. The package is gone.”
- \[00:02–00:04] Dex (shifts weight, avoids eye contact): “Mara, I didn’t take it.”
- \[00:04–00:06] Mara (steps closer, quiet): “Don’t dodge. Did you touch it?”
- \[00:06–00:08] Dex (interrupts, faster): “No—Mara, no. I didn’t even see it.”
- \[00:08–00:10] Mara (beat, exhales): “Then help me figure it out.”

**CONTINUITY NOTES:** Mara’s red scarf stays on. Dex keeps the tan blazer on. The printed email paper remains in Mara’s hand.

## [Copy/paste examples (2-person, group, ad call-and-response)](#copypaste-examples-2-person-group-ad-call-and-response)

### [Two-person friendly banter (quick pacing)](#two-person-friendly-banter-quick-pacing)

**SCENE:** Sunny café, upbeat.

**CAMERA / COVERAGE:** Two-shot at table, gentle push-in.

**CHARACTER A:** Lina. Visual ID: yellow beanie. Voice: playful, bright.

**CHARACTER B:** Omar. Visual ID: denim jacket. Voice: dry humor, relaxed.

**BLOCKING:** Lina stirs iced coffee; Omar slides a pastry plate forward.

**DIALOGUE:**

- \[00:00–00:02] Lina (grinning): “Omar, you bribing me with carbs again?”
- \[00:02–00:04] Omar (deadpan): “It’s not bribery. It’s… emotional support pastry.”
- \[00:04–00:06] Lina (laughs): “That might be the nicest thing you’ve ever said.”

### [Three-person group scene (explicit turn order)](#three-person-group-scene-explicit-turn-order)

**SCENE:** Office hallway, hurried.

**CAMERA / COVERAGE:** Over-the-shoulder alternating close-ups.

**CHARACTER A:** Priya. Visual ID: green lanyard. Voice: calm, firm.

**CHARACTER B:** Jules. Visual ID: black hoodie. Voice: fast, anxious.

**CHARACTER C:** Theo. Visual ID: white shirt, sleeves rolled. Voice: confident, persuasive.

**BLOCKING:** Priya stands centered; Jules paces; Theo leans against locker.

**DIALOGUE:**

- \[00:00–00:02] Priya (holds up phone): “Team—deadline moved up. Today.”
- \[00:02–00:04] Jules (stops pacing): “Today? That’s impossible.”
- \[00:04–00:06] Theo (cuts in, upbeat): “Not impossible. We split it. Jules takes visuals. Priya runs approvals. I ship the build.”
- \[00:06–00:07] Priya (nods): “Done. Move.”

### [Ad-style call-and-response (tight structure)](#ad-style-call-and-response-tight-structure)

**SCENE:** Bright studio, product on pedestal.

**CAMERA / COVERAGE:** Clean locked-off shot; quick punch-in on key words.

**CHARACTER A:** Host Ava. Visual ID: white blazer. Voice: energetic, precise.

**CHARACTER B:** Sidekick Ben. Visual ID: blue tee. Voice: curious, friendly.

**DIALOGUE:**

- \[00:00–00:02] Ava (gestures to product): “Meet the quickest way to prep your day.”
- \[00:02–00:03] Ben (leans in): “Quick how?”
- \[00:03–00:05] Ava (one beat, confident): “One tap. Clear steps. No clutter.”
- \[00:05–00:06] Ben (smiles): “Okay—show me.”

## [Common failures and exact fixes (troubleshooting table)](#common-failures-and-exact-fixes-troubleshooting-table)

| Symptom                                   | Likely cause in prompt                        | Exact rewrite to try                                                                                                            |
| ----------------------------------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Wrong character speaks a line             | Pronouns or unclear speaker tags              | Replace pronouns with names; prefix every line: `Mara:` / `Dex:` and keep one line per line                                     |
| Lines merge into one long delivery        | Multiple intents per line; paragraph dialogue | Split into short turns; each line = one intent; add beat markers like `[00:02–00:04]`                                           |
| Monotone or flat delivery                 | Voice direction too vague                     | Add tone + pace: “low, clipped, restrained anger” / “defensive, quick, breathy”                                                 |
| Missing reactions/cutaways                | No blocking or listening actions              | Add blocking and listener actions: “Dex (listens, swallows)” and specify shot-reverse-shot coverage                             |
| Continuity drifts (wardrobe/props change) | No continuity notes                           | Add a `CONTINUITY NOTES` line (labels, silhouettes, proportions, props) (<https://invideo.io/blog/hidden-secrets-of-kling-ai/>) |

## [A minimal iteration checklist (change only 1 variable per rerun)](#a-minimal-iteration-checklist-change-only-1-variable-per-rerun)

- Keep character names and visual IDs identical; change only one thing at a time
- If speakers swap, fix **labels/pronouns** before changing camera style
- If pacing is off, adjust **beat markers** and shorten lines
- If coverage feels random, specify **shot-reverse-shot** (or two-shot) explicitly
- If details drift, add/strengthen **continuity notes** (<https://invideo.io/blog/hidden-secrets-of-kling-ai/>)

## [Ethical + disclosure reminders for synthetic dialogue](#ethical--disclosure-reminders-for-synthetic-dialogue)

- Don’t impersonate real people or public figures without clear permission.
- Use **original or properly licensed** voice assets when applicable.
- If your video is marketing, training, or public-facing, consider a plain-language disclosure that dialogue is synthetic or AI-assisted.

## [FAQ](#faq)

### [What’s the single biggest improvement for a multi character dialogue prompt?](#whats-the-single-biggest-improvement-for-a-multi-character-dialogue-prompt)

Line-by-line speaker labeling with names, plus a clear turn order. Avoid pronouns when turns are fast.

### [Should I write dialogue as a screenplay format?](#should-i-write-dialogue-as-a-screenplay-format)

You can, but keep it _simpler_ than a full script: one intent per line, and add minimal action tags + beat markers.

### [How do I reduce timing drift between lines?](#how-do-i-reduce-timing-drift-between-lines)

Shorten each line, add beat markers, and avoid packing multiple actions and emotions into one sentence.

### [Do I need shot language like “shot-reverse-shot”?](#do-i-need-shot-language-like-shot-reverse-shot)

It often helps because models trained on cinematic intent can interpret that coverage pattern; Kling’s guide explicitly calls out understanding shot-reverse-shot dialogue. (<https://blog.fal.ai/kling-3-0-prompting-guide/>)

## [Related reading](#related-reading)

- [Veo 3.1 vs Sora 2: comparison guide](https://www.imaginary.app/alternatives/sora-2)
- [What is the Veo 3 API?](https://www.imaginary.app/blog/veo-3-1-api-access)
- [Veo 3 API pricing comparison](https://www.imaginary.app/blog/veo-3-1-pricing-plans)

## [CTA: Build this into your pipeline](#cta-build-this-into-your-pipeline)

If you want to generate multi-speaker scenes programmatically, you can turn the template above into a reusable prompt builder and iterate quickly per scene.

- Explore the endpoints and workflow in the [Imaginary API docs](https://www.imaginary.app/api)
- Estimate costs and scale-up options on [Pricing](https://www.imaginary.app/pricing)

## [Sources](#sources)

- <https://blog.fal.ai/kling-3-0-prompting-guide/>
- <https://fal.ai/learn/devs/kling-2-6-pro-prompt-guide>
- <https://leonardo.ai/news/kling-ai-prompts/>
- <https://invideo.io/blog/hidden-secrets-of-kling-ai/>

### Try it on your own idea

Turn text or an image into a video with sound. You see the credit cost before you generate, and failed generations are refunded. No credit card required to start.

[Start creating](https://www.imaginary.app/generate)[See pricing](https://www.imaginary.app/pricing)

[← Back to all posts](https://www.imaginary.app/blog)
