ai contact center · stub
The Flow Designer virtual agent activities
Verified 2026-09-05 · 19 claims · sources tier 2 · 1 disputed
Also known as CCAI configuration, Google CCAI connector, State Event, Virtual Agent V2, Virtual Agent Voice.
Stub. This topic has 19 verified claims and no published article. The claims below are exactly what the corpus holds today.
Disputed claims: 1 claim below carries conflicting evidence.
So far, no summary has been generated for this topic. The claims below are what the corpus currently holds.
See also
Constrained by
- Webex Contact Center platform generations and predecessors — Virtual Agent V2 is Next Generation only
Part of
- The Webex Contact Center Flow Designer activity set — Two activities within the Flow Designer activity set
- Which Flow Designer activities can send customer data outside the platform — One of the routes by which caller content leaves the platform
Uses
- Third-party model and speech vendors behind Webex contact centre AI — Names Google Dialogflow and Webex AI Agent Studio as the receiving services
Referenced by
- Webex Contact Center integration connectors — The Google connector is the credential boundary behind Virtual Agent V2
- What each Webex Contact Center connector type stores — The Google connector is the boundary behind the virtual agent activities
- The Webex Contact Center Flow Designer activity set — Activities that send caller speech outward
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | Cisco's own worked example for Virtual Agent variable passing sends the caller's phone number, with key ANI and value NewContact.ANI. Build and manage flows with Flow Designer · Virtual Agent step 4, Variable Passing, worked example | fact | 0.90 | 2026-09-05 |
| 2 | The JSON that reaches Google Dialogflow is parsed by a fulfilment application that Dialogflow reaches through a webhook configured in Dialogflow, which is a second hop outside Webex Contact Center. Build and manage flows with Flow Designer · Virtual Agent step 4, Variable Passing | fact | 0.90 | 2026-09-05 |
| 3 | Webex Contact Center sends the Virtual Agent key-value parameters to Google Dialogflow as a JSON value in the request.query_param.payload object. Build and manage flows with Flow Designer · Virtual Agent step 4, Variable Passing | fact | 0.90 | 2026-09-05 |
| 4 | The article announces that both virtual agent activities return a transcript URL and publishes no lifetime, authentication model or hosting location for it. Build and manage flows with Flow Designer · Virtual Agent steps 5 and 6; Configure Virtual Agent V2 activity steps 9 and 11 | fact | 0.90 | 2026-09-05 |
| 5 | Flow Designer ships 2 virtual agent activities, named Virtual Agent and Virtual Agent V2; the article names no third variant and no digital-channel equivalent. Build and manage flows with Flow Designer · Activities in call handling; activity palette grouping; self-loop limit table | fact | 0.90 | 2026-09-05 |
| 6 | Cisco states that the Virtual Agent activity is powered by Google Dialogflow and that Dialogflow, not Webex Contact Center, matches the caller's speech to an intent. Build and manage flows with Flow Designer · Virtual Agent, introductory paragraph | fact | 0.90 | 2026-09-05 |
| 7 | Virtual Agent V2 requires a Google CCAI connector and a CCAI configuration created in Control Hub, so the credential relationship with Google is held by the connector rather than by the flow. Build and manage flows with Flow Designer · Configure Virtual Agent V2 activity > Before you begin, second bullet | fact | 0.90 | 2026-09-05 |
| 8 | The Virtual Agent V2 procedure documents setting a custom input language by assigning a language code such as fr-CA to the Global_Language variable, and links to the supported voices and languages in Dialogflow ES. Build and manage flows with Flow Designer · Configure Virtual Agent V2 activity step 7, Conversational Experience settings | disputed | 0.60 | 2026-09-05 |
| 9 | The Virtual Agent V2 closing notes state that en-US is currently the only supported language. Build and manage flows with Flow Designer · Configure Virtual Agent V2 activity step 11, closing notes | fact | 0.90 | 2026-09-05 |
| 10 | Three flow templates drive the Virtual Agent V2 activity against Webex AI Agent Studio agents rather than Google, so the same activity fronts two different AI backends with an identical field set. Build and manage flows with Flow Designer · Templates AI Agent Autonomous (Package Tracking), AI Agent Scripted (Package Tracking), AI Agent Scripted (Doctor's Appointment Booking), activity tables | fact | 0.90 | 2026-09-05 |
| 11 | Virtual Agent V2 retries invalid or no-input errors an infinite number of times, as one of 5 settings that are fixed internally, do not appear in the interface and cannot be changed. Build and manage flows with Flow Designer · Virtual Agent V2 > Default system-level settings, bullet 1 | fact | 0.90 | 2026-09-05 |
| 12 | The other 4 settings Virtual Agent V2 fixes internally are barge-in, the DTMF terminator, the DTMF no-input timeout and the DTMF inter-digit timeout. Build and manage flows with Flow Designer · Virtual Agent V2 > Default system-level settings, bullet 1 | fact | 0.90 | 2026-09-05 |
| 13 | Only customers on the Next Generation platform can configure the Virtual Agent V2 activity. Build and manage flows with Flow Designer · Virtual Agent V2 > Configure Virtual Agent V2 activity, opening sentence | fact | 0.90 | 2026-09-05 |
| 14 | The sentence describing what Virtual Agent V2 sends outward names no vendor; it says the data goes to the integrated third-party AI platform. Build and manage flows with Flow Designer · Configure Virtual Agent V2 activity step 8, State Event settings | fact | 0.90 | 2026-09-05 |
| 15 | Cisco warns that the optional Variable Passing parameters on the Virtual Agent activity may contain personally identifiable information, and offers no masking, redaction or opt-out for that field. Build and manage flows with Flow Designer · Virtual Agent step 4, Variable Passing, first sentence | fact | 0.90 | 2026-09-05 |
| 16 | A Google Contact Center AI connector cannot be deleted while a CCAI configuration is associated with it, and the article never defines what a CCAI configuration is or where it is managed. Set up integration connectors for Webex Contact Center · Edit a Connector, deactivated-connector options | fact | 0.90 | 2026-09-05 |
| 17 | Editing or reactivating the Google Contact Center AI connector requires reauthenticating with Google, and the refresh flow is to be run outside business hours with the browser pop-up blocker disabled. Set up integration connectors for Webex Contact Center · Edit a Connector, step 2 and the deactivated-connector options | fact | 0.90 | 2026-09-05 |
| 18 | A Google Contact Center AI connector record holds a name, a project name, a billable project name and a billable service account, and the administrator types no secret; authentication is a Google sign-in. Configure Google CCAI connector · Configure Google CCAI connector, record fields | fact | 0.90 | 2026-09-05 |
| 19 | The Google Contact Center AI connector article states no maximum number of connectors of this type. Configure Google CCAI connector · Configure Google CCAI connector, record fields | fact | 0.90 | 2026-09-05 |
Sources
tier 2 current vendor documentation
Build and manage flows with Flow Designer
tier 2 current vendor documentation
Configure Google CCAI connector
tier 2 current vendor documentation
Set up integration connectors for Webex Contact Center
Cite this page
APA
WarmTransfer. (2026, September 5). The Flow Designer virtual agent activities. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-virtual-agent-activities
BibTeX
@misc{warmtransfer-wxcc-virtual-agent-activities,
title = {The Flow Designer virtual agent activities},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/wxcc-virtual-agent-activities},
note = {Verified 2026-09-05}
}