00 · Header

Language, voice, and custom events

T10-R03. Override language and voice with flow variables set before Virtual Agent V2. A voice the engine does not support takes the error path. Custom events are voice only. [cite:11]

01 · TL;DR

Five lines, then why it matters

• Set Global_Language to a language code such as fr-CA before the activity. [cite:11]
• Set Global_VoiceName to a voice code such as en-US-Jennifer. [cite:11]
• If the voice is not supported by the agent’s engine, the call exits the error path. [cite:11]
• State events use Event Name and Event Data. Expressions use the article’s double-brace syntax. [cite:11]
• Custom events are supported for scripted and autonomous agents through the voice channel only. [cite:11]

02 · Map

Set the variable, then the activity

The article says to put Set Variable activities before Virtual Agent V2 when you override Studio defaults. [cite:11]

03 · Core

What the opened pages say

The example custom welcome uses Event Name CustomWelcome and Event Data as a JSON object with a Name field. Event name and data may be static or an expression. [cite:11]

VirtualAgentV2.StateEventName stores the custom event name received back after the flow triggers one. [cite:11]

The supported-languages article is named but was not opened. This room does not copy a language matrix. The fr-CA and en-US-Jennifer strings are the examples s0qro1 itself prints. [cite:11]

04 · Ecosystem

Ecosystem and sister technologies

Global_Language

Flow variable that overrides the Studio input language. Example on the page: fr-CA. [cite:11]

Global_VoiceName

Flow variable that overrides the output voice. Example: en-US-Jennifer. [cite:11]

State event

Event Name plus Event Data sent to the agent’s handler. [cite:11]

Voice-only custom events

The article’s current line for scripted and autonomous agents. [cite:11]

Sister-technology matrix

Integration edges

05 · Flow

Order of operations

1. Decide whether Studio defaults are acceptable.
2. If not, set Global_Language and Global_VoiceName first.
3. Use a voice the agent’s engine supports. The matrix article was not opened, so confirm it before a design review.
4. Add a state event only on the voice flow.

06 · Config

Clicks the articles print

• Set Variable, name Global_Language, value a code the article exemplifies as fr-CA. [cite:11]
• Set Variable, name Global_VoiceName. [cite:11]
• State Event columns: Event Name, Event Data. Expression form uses double braces around the variable, as the article prints. [cite:11]

07 · Limits

Limits the articles state

08 · Trouble

Trouble

09 · Self-question

Oral ladder

10 · Lab

Read it back

• Place two Set Variable steps above a VAV2 box.
• Mark the language-list article as confirm until you open it.

11 · Quiz

Quiz

12 · Audio

Read-along uses the page

13 · Interview

Oral-ready

30 seconds. Language and voice overrides are Global_Language and Global_VoiceName, set before Virtual Agent V2. A bad voice takes the error path. Custom events stay on voice. [cite:11]

2 minutes. I use the article’s own examples, not a matrix I did not open. Expressions use the double-brace form the page prints. StateEventName is how the flow sees the event that came back. [cite:11]

14 · Citations

Ledger

Opened 2026-10. Mirrors cites/T10-R03.md.

1. Use AI agents for customer interactions, help.webex article s0qro1, header August 25, 2026. Virtual Agent V2 outcomes Handled, Escalated, and Errored. Autonomous voice is limited to specific customers. Six digital channels. Custom events are voice only. onTimeOut: the agent has not responded in not more than 15 seconds.

15 · Re-engineer later

Open

• Supported languages and voices article: confirm, no URL, because it was not opened.