00 · Header

T8 · Flows, integrations, and the current product

Flow Designer Essentials

Gateway Flows and tools T8-R01 CustomerFlowAPIAgent
Illustrated scene for Flow Designer Essentials. Original drawing, not a product screenshot.
Sequence · Customer → Flow → API → Agent CustomerFlowAPIAgent 123
Color-coded sequence: Customer → Flow → API → Agent. A packet moves along the arrows. Reduced motion keeps every step visible.

Flow Designer is how Webex Contact Center routes a live call: activities on a canvas, a main flow, and optional event flows. Publish stays dark until validation is on and the errors are gone. This room is the multi-tenant product. It is not the Enterprise script tool.

Room T8-R01 Version v0.1 last-verified: TODO Difficulty L2 Est. time 80–100 min Prereq T3-R01 Reading 14 min

01 · Executive summary

Five lines, then why it matters

  • Flow Designer routes real-time calls. You choose activities, including how agents are assigned, from a drag-and-drop library. [cite:1]
  • Start Flow is already on the main canvas. You cannot delete it. It is the event that triggers the flow. [cite:1]
  • Validation is off by default, so errors stay hidden. With the toggle off, Publish stays disabled. After you turn validation on, Publish stays disabled until every error is fixed. [cite:1]
  • Get Queue Info returns position in queue and estimated wait time. Success needs both values positive. If skills are assigned in the flow on a team-assignment queue, EWT is always −1, and the Insufficient Information branch is the one that still has a valid PIQ. [cite:1]
  • The same article prints two ways to open flows: Services → Contact Center → Flows, and Contact Center → Customer Experience → Flows. Do not pick one and call the other wrong. [cite:1]
Why it matters. A flow that publishes nothing is often just the validation toggle. A flow that treats EWT −1 as “the queue is empty” will mis-route skill queues. The simulator on the Labs page copies these rules. It is not a tenant.

02 · Architecture map

Main flow, then events

Mermaid source (not rendered)
flowchart LR
  Start[Start Flow] --> Play[Play Message]
  Play --> GQI[Get Queue Info]
  GQI --> QC[Queue Contact]

03 · Core concepts

Rules that change what you click

Start Flow

It is on the main canvas by default. You cannot delete it. It indicates the event that triggers the flow and controls how the flow can be used. [cite:1]

Event flows

They are asynchronous to the main flow. You cannot predict when the system triggers one. They are optional extensions of the main flow. [cite:1]

Validation and Publish

The validation toggle is off by default, so errors do not appear. If it is off, Publish stays disabled. After you enable validation, Publish remains disabled until you resolve all errors. [cite:1]

DNIS on a transfer to an entry point

The destination number is presented as NewPhoneContact.DNIS. If the entry point is configured with an E.164 number only, national dialing is converted: the article’s example is 5550101234 presented as +15550101234. If the entry point has both an E.164 number and an extension, DNIS is always the E.164 number. Do not assume one format unless the entry point’s numbering guarantees it. [cite:1]

Not WxCCE scripting

This article is Webex Contact Center. T4 does not treat Flow Designer as the Enterprise script tool. [cite:1]

04 · Ecosystem

Activities and the systems beside them

CustomerFlowAPIAgent This room
Mini map of the neighbors named on this room’s sequence. Orientation sketch, not a new product claim.
Flow Designer
The drag-and-drop surface that routes real-time calls and decides what happens at each stage, including how agents are assigned. [cite:1]
Start Flow
Default activity on the main canvas. Cannot be deleted. Names the triggering event. [cite:1]
Event flow
Optional, asynchronous, not predictable from the main path. [cite:1]
Get Queue Info
Returns the caller’s position in queue (PIQ) and estimated wait time (EWT), plus other output variables. [cite:1]
EWT −1
The value Get Queue Info always returns for queues with team assignment and skills assigned in the flow. EWT does not apply there. [cite:1]
Insufficient Information
The branch when PIQ is valid and EWT is −1. You can use PIQ. EWT was not calculated. [cite:1]
Success branch
Both EWT and PIQ come back positive. [cite:1]
Queue priority
An integer variable from 1 through 9. Outside that range, the default priority is 10. [cite:1]
Fallback queue
Used only when a queue variable fails to return a valid queue ID. [cite:1]
NewPhoneContact.DNIS
The DNIS presented to the receiving entry-point flow after a transfer. Format depends on how that entry point is numbered. [cite:1]
BRE Request
A Flow Designer utility activity. The Business Rules Engine guide says you can build a flow that invokes it. [cite:2]
QueueToAgent
Named in the multi-tenant architecture article as voice, direct to an agent id. It is a different sentence from this room’s Queue Contact activity. [cite:3]

Mind map

Sister matrix

This is Webex Contact Center. Peer flow builders are labels. No parity matrix is published on help.webex.com.
IdeaWhat the flow article saysWhy it mattersWhere you touch itWhat goes wrongCite
Workforce managementNot a flow activity in the sections used here.Schedules are not the canvas.WFO stays in T3 and T4.Putting a schedule bot in the IVR. Check the subscription in Control Hub before using a WFO SKU. py6u9h’s list is Enterprise, CCE, and CCX, and a multi-tenant subscription shows a different set.[cite:1]
Quality and recordingThe activity list includes Record and Recording Control. Retention numbers are not in this article.A record activity is not a retention policy.Voice activities.Quoting Calling’s one-year retention as a flow setting.[cite:1]
E911Not a flow activity in this article.Emergency calling is a phone path.T2 and nvfbjts. No flow-level emergency activity is in the Flow Designer article. [cite:6]Testing 911 by reading the flow trace only.[cite:1]
ReportingPIQ and EWT are activity outputs, not Analyzer history.A positive EWT is a branch input.Get Queue Info.Using EWT −1 as a report of zero wait.[cite:1]
SalesforceScreen Pop can take a URL. The article’s example is a website such as a Salesforce URL. That is not the CRM connector install.Screen pop is a flow setting. The connector is another article.Screen Pop activity.Assuming the example URL provisions Salesforce.[cite:1]
Dynamics connectorNot specified here.Keep Microsoft’s product name off this canvas.nhovcy4 does not name Dynamics. Do not draw it as an activity.Drawing Dynamics 365 Contact Center as a Flow Designer node.[cite:1]
ServiceNowNot named in nhovcy4.Same boundary.Absence is the cited fact. Do not invent an activity.Inventing a ServiceNow activity.[cite:1]
Virtual agentVirtual Agent and Virtual Agent V2 are activities in the library. The VAV setup guide is a separate article.The activity name is not the whole setup.Activity library, then the VAV guide.Skipping the setup article.[cite:1] [cite:4]
AI AssistantNot this article’s activity list.Control Hub AI Assistant is T3’s article.No flow node in nhovcy4 is the AI Assistant. The desktop icon is nvvv1zb. Virtual Agent V2 is s0qro1. [cite:8]Renaming Virtual Agent to AI Assistant.[cite:1]
IVRVoice activities include Menu, Collect Digits, Play Message, Play Music, Callback, and Schedule Callback.Self-service is these activities, not CVP, on this product.Voice group in the library.Expecting a CVP application name to appear.[cite:1]
DigitalThe article’s opening job is routing real-time calls. as of 2026-10-14, s0qro1 names six Connect channels. utqcm7 remains the architecture list. [cite:7]Do not stretch a voice rule onto a channel the page did not name.Voice sections used here.Claiming every digital channel uses EWT the same way.[cite:1]
IdentityYou sign in to use the activity library. The article points at Control Hub.SSO failures look like a missing flow.Control Hub sign-in. The printed cascades differ; see config.Debugging activities while the admin session is dead.[cite:1]

Integration edges

FromToWhat crossesRuleCite
Entry point transferReceiving flowNewPhoneContact.DNISE.164-only entry points present E.164, including the article’s 5550101234 → +15550101234 example. E.164 plus extension always presents the E.164 number.[cite:1]
Get Queue InfoSuccess or Insufficient InformationPIQ and EWTSuccess is both positive. Insufficient Information is valid PIQ and EWT −1.[cite:1]
Skill plus team assignmentEWT outputAlways −1EWT does not apply. Do not treat −1 as a measured wait.[cite:1]
Queue variableFallback queueQueue IDFallback is used only when the variable does not return a valid queue ID.[cite:1]
Priority variableQueueInteger 1–9, else 10Out of range does not reject the flow. It defaults to 10.[cite:1]
Queue ContactHTTP RequestData the request needsAn HTTP Request immediately after Queue Contact may not retrieve it. Insert Play Message or Play Music.[cite:1]
FlowBusiness Rules EngineBRE Request activityThe BRE guide: a flow can invoke the BRE activity.[cite:2]
Screen PopA URLVariables as {{variable}}Example in the article uses {{NewContact.ANI}} and a website URL.[cite:1]

Bridges

Flow DesignerOlder habitPeer labelCite
Activities on a main flowTrace the ICM node in Script Editor and the activity on the Flow Designer canvas. No help page prints a node-for-node map, and activity names change when Cisco updates the canvas.No parity matrix is published on help.webex.com. Documented calling migrations are Unified CM and BroadWorks/BroadCloud, which are not flow editors. [cite:5][cite:1]
Get Queue InfoA queue node that returned position. The −1 rule is specific.Amazon Connect and Genesys queue blocks are orientation only.[cite:1]
BRE RequestAn external database dip. BRE is in-platform in that user guide’s scope.Do not rename it to a CRM connector.[cite:2]

Future hooks

  • Open the activity on the Flow Designer canvas. Unquoted parameters are the fields on that node, and they change when Cisco updates the activity.
  • Enterprise scripting is T4’s open item, not a second name for this canvas.
  • When a help page retires one of the two menu cascades, update the config table. Until then, cite both.

Ecosystem troubleshooting

SymptomMix-upCheckMoveCite
Publish is grey and no errors showValidation is still offFooter toggleTurn validation on, then fix what appears[cite:1]
EWT is −1 on a skilled team queueRead as a failure of the queueTeam assignment with skills assigned in the flowUse the Insufficient Information branch and PIQ[cite:1]
HTTP after Queue Contact is emptyThe activities are adjacentArticle’s warningInsert Play Message or Play Music[cite:1]
DNIS is +E.164 although the caller dialed an extensionThe entry point has both formatsDNIS tableExpect the E.164 number[cite:1]

05 · Flow

A queue treatment you can defend

  1. Open flows with either printed cascade: Services → Contact Center → Flows, or Contact Center → Customer Experience → Flows. Functions are under Services → Contact Center → Customer Experience → Functions. [cite:1]
  2. Leave Start Flow in place. Add Play Message or Menu only if the treatment needs them. [cite:1]
  3. Add Get Queue Info before you promise a wait announcement. Branch Success only when EWT and PIQ are both positive. Branch Insufficient Information when PIQ is valid and EWT is −1. [cite:1]
  4. If the queue is team-based and the flow assigns skills, plan on EWT −1. Do not announce a calculated wait. [cite:1]
  5. Queue Contact can use a static queue or a variable. If you use a variable, set a fallback queue for an invalid ID. Priority 1–9; anything else becomes 10. [cite:1]
  6. If you need an HTTP Request after Queue Contact, put Play Message or Play Music between them. [cite:1]
  7. Turn validation on. Fix every error. Only then does Publish leave the disabled state the article describes. [cite:1]

06 · Config

Paths and switches

ControlArticle textNotes
Open flowsServices → Contact Center → FlowsAlso printed: Contact Center → Customer Experience → Flows. The Flows page has Flows, Subflows, and Global Variables in one of those procedures.
FunctionsServices → Contact Center → Customer Experience → FunctionsCustom code used across flows. Not the same page as Flows.
ValidationToggle on the right side of the footer. Off by default.Errors appear only after it is on.
PublishDisabled while validation is off. After validation is on, disabled until all errors are resolved.Both halves are required.
Queue choiceStatic queue, or a variable plus Fallback Queue.Fallback applies when the variable returns an invalid queue ID.
PriorityFlow variable, integer 1–9.Otherwise the default is 10.

Open Flow Designer in the live tenant. nhovcy4 documents more than one menu cascade, and the highlighted cascade depends on what that tenant has enabled.

07 · Limits

BoundValueCite
Priority range1 through 9, otherwise 10[cite:1]
EWT on team assignment with skills in the flowAlways −1[cite:1]
SuccessEWT and PIQ both positive[cite:1]
Insufficient InformationValid PIQ and EWT of −1[cite:1]
DNIS when the entry point has E.164 and an extensionAlways the E.164 number[cite:1]
E.164-only example5550101234 is presented as +15550101234[cite:1]
Activity schemas not quoted hereOpen the activity on the canvas and read the fields Cisco shows for that node. Parameters change when the activity is updated.Do not invent parameters

08 · Troubleshooting

SymptomLikely causeEvidenceNext moveCite
Publish never enables and the canvas looks cleanValidation is off, so errors are hidden and Publish stays disabledFooter toggleEnable validation and clear the errors that appear[cite:1]
Publish still disabled after validation is onErrors remainThe article’s second sentence on PublishFix all of them[cite:1]
Wait announcement says the wait failedEWT −1 on a skilled team-assignment queueAlways −1 for that caseTake Insufficient Information and use PIQ[cite:1]
Both branches feel wrongSuccess was used when a value was −1Success requires both positiveMove the −1 case off Success[cite:1]
Lookup after the queue returns nothingHTTP Request is the next activityThe article’s delay warningInsert Play Message or Play Music[cite:1]
Variable queue dumps the callNo fallbackFallback exists for an invalid queue IDSet Fallback Queue[cite:1]
Priority 0 or 15 was requestedOutside 1–9Default becomes 10Expect 10, or pass 1–9[cite:1]
DNIS is not the extension the caller dialedEntry point has E.164 and an extensionDNIS tableMatch on the E.164 value[cite:1]
Start Flow is missing from a new main flowSomeone deleted it, or this is not the main canvasYou cannot delete Start FlowReopen the main flow[cite:1]

09 · Self-question ladder

L1What does Flow Designer route?

Real-time calls, including how agents are assigned and what happens at each stage. [cite:1]

L1Can you delete Start Flow?

No. It is on the main canvas by default. [cite:1]

L2What is true while the validation toggle is off?

Errors do not appear, and Publish stays disabled. [cite:1]

L2When does Success fire on Get Queue Info?

When both EWT and PIQ are positive. [cite:1]

L2When does Insufficient Information fire?

PIQ is valid and EWT is −1. [cite:1]

L2When is EWT always −1?

Queues with team assignment and skills assigned in the flow. EWT does not apply. [cite:1]

L3What priority is used if the variable is 12?

10. Only 1 through 9 are in range. [cite:1]

L3When is the fallback queue used?

Only if the queue variable fails to return a valid queue ID. [cite:1]

L3What do you insert between Queue Contact and HTTP Request?

A short delay such as Play Message or Play Music. Otherwise the request may not retrieve the data. [cite:1]

L3A caller dials extension 1234 and the entry point also has an E.164 number. What DNIS should the flow expect?

The E.164 number, not the extension. [cite:1]

L4Name both flow-opening cascades in the article.

Services → Contact Center → Flows, and Contact Center → Customer Experience → Flows. [cite:1]

L4What is BRE Request?

A utility activity. The Business Rules Engine user guide says a flow can invoke it. [cite:2]

10 · Lab

Trace a queue treatment on paper, then in the simulator

11 · Quiz

Twelve checks

0 revealed
Q1MCQ

With validation off:

  1. Publish is available and errors are hidden
  2. Errors are hidden and Publish stays disabled
  3. The flow auto-publishes
  4. Start Flow is removed
Reveal

B. [cite:1]

Q2MCQ

Start Flow:

  1. Can be deleted after the first activity
  2. Cannot be deleted
  3. Exists only on event flows
  4. Is a BRE rule
Reveal

B. [cite:1]

Q3Scenario

PIQ is 6 and EWT is −1. Which branch?

Reveal

Insufficient Information. Success needs both values positive. [cite:1]

Q4MCQ

EWT on a team-assignment queue with skills assigned in the flow:

  1. Is the average of the last hour
  2. Always returns −1
  3. Is always 0
  4. Disables the activity
Reveal

B. [cite:1]

Q5MCQ

A priority variable of 0 becomes:

  1. 0
  2. 1
  3. 10
  4. A validation error that the article says blocks the activity
Reveal

C. Out of range 1–9 defaults to 10. [cite:1]

Q6Scenario

HTTP Request is the next box after Queue Contact and returns nothing. What does the article tell you to insert?

Reveal

Play Message or Play Music, as a short delay, so the request can see the data. [cite:1]

Q7MCQ

Fallback queue is used when:

  1. EWT is −1
  2. The queue variable returns an invalid queue ID
  3. Publish is off
  4. DNIS is an extension
Reveal

B. [cite:1]

Q8MCQ

Entry point has E.164 and an extension. DNIS presented to the receiving flow is:

  1. Always the extension
  2. Always the E.164 number
  3. Whichever the caller dialed, unchanged
  4. Empty
Reveal

B. [cite:1]

Q9MCQ

The article’s national-to-E.164 example is:

  1. 1234 → 1234
  2. 5550101234 → +15550101234
  3. +1555 → 555
  4. 911 → 933
Reveal

B. For an entry point configured with an E.164 number only. [cite:1]

Q10Scenario

A colleague says the only legal path is Services → Contact Center → Flows. What else does the same article print?

Reveal

Contact Center → Customer Experience → Flows. Functions use Services → Contact Center → Customer Experience → Functions. [cite:1]

Q11MCQ

Event flows are:

  1. Required and synchronous
  2. Optional and asynchronous
  3. A replacement for Start Flow
  4. Partner Hub roles
Reveal

B. [cite:1]

Q12MCQ

BRE Request is:

  1. A utility activity a flow can invoke
  2. The Enterprise ICM script editor
  3. A Calling dial plan
  4. An emergency callback number
Reveal

A. [cite:2]

12 · Audio

90 seconds. Validation off means Publish stays off. EWT −1 on a skilled team queue is Insufficient Information, not a zero wait.

No mp3 shipped.

45 seconds. Do not put HTTP Request directly against Queue Contact.

13 · Interview

“Flow Designer is the Webex Contact Center canvas, not the Enterprise script tool. Start Flow stays. I do not publish until validation is on and the errors are gone, because Publish is disabled in both of those earlier states. Get Queue Info’s Success branch needs a positive wait and a positive position. If the queue is team-based and the flow assigns skills, estimated wait is always −1 and I use the Insufficient Information branch. Priority outside 1 to 9 becomes 10. A variable queue needs a fallback. I never chain HTTP Request directly onto Queue Contact. If an entry point has both an E.164 number and an extension, DNIS is the E.164 number. The help article itself prints two different menu paths, so I cite both.”

14 · Citations

  1. Build and manage flows with Flow Designer — help.webex — article nhovcy4 — help.webex.com article nhovcy4 — retrieved 2026-10-14. Validation, Publish, Start Flow, event flows, Get Queue Info branches, EWT −1, priority, fallback, DNIS, menu cascades, HTTP Request spacing.
  2. Webex Contact Center Business Rules Engine User Guide — help.webex — article nve6qddb — help.webex.com article nve6qddb. Flow Designer can invoke the BRE Request activity. Page viewed 2026-10-14; the article header on that fetch said August 19, 2026.
  3. Webex Contact Center Architecture — help.webex — article utqcm7 — help.webex.com article utqcm7. QueueToAgent is the architecture article’s voice activity, kept distinct from this room’s Queue Contact notes.
  4. Configure Virtual Agent-Voice in Webex Contact Center — help.webex — article n6gaghu — help.webex.com article n6gaghu. Separate setup article from the activity name in the library.
  5. Migrate Unified CM to Webex Calling, introduction — help.webex — article nbedetf — help.webex.com article nbedetf. Cited only to mark that a calling migration is not a flow-editor parity matrix.
  6. Provision Emergency Calling in Webex Contact Center — help.webex — article nvfbjts — help.webex.com article nvfbjts — retrieved 2026-10-14. Emergency for WebRTC agents is Control Hub and RedSky, not a Flow Designer activity in nhovcy4.
  7. Use AI agents for customer interactions — help.webex — article s0qro1 — help.webex.com article s0qro1 — retrieved 2026-10-14. Header August 25, 2026. Six Connect channels. Virtual Agent V2 is the voice activity for scripted and autonomous agents.
  8. Cisco AI Assistant for Webex Contact Center — help.webex — article nvvv1zb — help.webex.com article nvvv1zb — retrieved 2026-10-14. Header October 06, 2026. Paid add-on. Agent Desktop icon. Not described as a Flow Designer activity.
  9. Set up digital channels in Webex Contact Center — help.webex — article nmzsthj — help.webex.com article nmzsthj — retrieved 2026-10-14. Social, email, and chat queues. Skill routing is a Connect QueueTask node. The page does not print estimated wait time.

15 · Re-engineer later

  • Open each activity on the canvas for parameters this room did not quote. Those fields change when Cisco updates the activity.
  • Open Flow Designer in the tenant you are configuring. The highlighted cascade follows the features that tenant has enabled.
  • nhovcy4 describes Get Queue Info for a caller and for previous calls, and reports EWT in milliseconds. The digital setup article nmzsthj uses a Connect QueueTask node for social, email, and chat, and it does not print EWT. Do not teach the voice rules as the digital rule. [cite:1] [cite:9]
  • ICM node parity stays marked in T6-R04.
  • Enterprise script tool, still open in T4.

Sources and go deeper

Checked links were opened this month. A confirm row has no address because that page was not opened.

sources.json for this page.