00 · Header

T8 · Flows, integrations, and the current product

Flow Design Patterns

Color-coded sequence: Customer → Flow → API → Agent. A packet moves along the arrows. Reduced motion keeps every step visible.

Callback, after-hours, a priority that people call VIP, and overflow are four Flow Designer patterns. None of them is a separate product object named VIP. Priority is P1–P9 on the activity, with 10 as the default when nothing in range is set. After-hours is the Business Hours activity reading schedules from Control Hub. Overflow on a team queue is call-distribution target expansion, not a number this room invents.

Room T8-R02 Version v0.1 last-verified: 2026-10-14 Difficulty L3 Est. time 70–90 min Prereq T8-R01, T3-R03 Reading 23 min

01 · Executive summary

Five lines, then why it matters

Courtesy callback creates a queue task. Keep the original queue if the contact should hold its place. Move it only when you accept the end of the new queue, no skills, and default priority. [cite:2]
Scheduled callback is a future window. Configure the Callback Default Entry Point first. For best results, add the Disconnect the article recommends immediately after the activity. At the scheduled time a new interaction follows that entry point’s flow. [cite:2]
After-hours belongs on Business Hours, fed by Control Hub working hours, holidays, and overrides. Existing customers can keep using Routing Strategy to connect an entry point to a flow until that feature is decommissioned. The routing-strategy article points you at Business Hours and does not delete existing strategies. [cite:3] [cite:10]
“VIP” in a design review means Set Contact Priority or the priority on Queue Contact. P1 is highest. Unset or out-of-range priority is 10. [cite:1]
Team queues overflow by adding the next call-distribution group after the configured wait. Agent-assignment queues do not expand on a timer. [cite:2]

Why it matters. Interviewers ask these four patterns as if they were one checkbox. They are three activities plus a queue setting, and priority loses to queue ranking when the agent’s teams are ranked. T8-R01 already has publish and Get Queue Info. This room is what you draw after the contact is queued.

02 · Map

Where each pattern lives

Pattern	Object	Where to read it	Why it varies
Courtesy callback	Callback activity after Queue Contact or Queue To Agent	Flow Designer canvas, then help.webex.com article np2fdx	Same queue versus a different queue changes skills and place in line
Scheduled callback	Schedule Callback, plus Callback Default Entry Point	Control Hub Channel Settings, then the flow	The entry point’s flow is what runs later, and it is per organization
After hours	Business Hours activity	Control Hub business hours, holidays, and overrides	Overrides and holidays win when they overlap the shift
VIP	Set Contact Priority, or priority on the queue activity	The activity on the canvas. There is no VIP flag in these articles	P1–P9 if set; 10 if missing or out of range. A later queue activity can override an earlier one
Overflow	Call distribution groups on a team queue	The queue in Control Hub	The wait before the next group is configured on that queue. Agent queues do not use it

Mermaid source (not rendered)

flowchart LR
  Start[Start Flow] --> BH[Business Hours]
  BH --> QC[Queue Contact]
  QC --> CB[Callback]
  CB --> Disc[Disconnect]

03 · Core concepts

Rules that change the drawing

Callback

The activity creates a task in a queue so an agent can call the customer back. Place it after Queue Contact or Queue To Agent. Chaining it with Queue To Agent is how the articles describe callback to the preferred agent the contact was queued to. [cite:1] [cite:2]

Same queue versus a different queue

If the callback stays in the original queue, the contact keeps its position, skills, priority, and contextual data. If you pick a different queue, the contact is pushed to the end of that queue with no skills and with default priority. [cite:2]

Schedule Callback

Any telephony queue, inbound or outbound. For best results, the article recommends a Disconnect immediately after Scheduled Callback so the current call ends once the callback is scheduled. At the requested time a new interaction follows the flow linked to the Callback Default Entry Point. CallbackFailed retries if that handler is configured. [cite:2]

Priority, which is the VIP pattern

Set Contact Priority is off by default on Queue Contact. With no priority, the default is 10. Higher priority is handled first. Equal priority uses the longest wait. Static priority is P1–P9, P1 highest and P9 lowest. A variable must be an integer from 1 through 9. Outside that range the default is 10. Queue To Agent uses the same P1–P9 list and the same default of 10. [cite:1]

Which priority wins

If Set Contact Priority sits before Queue Contact or Queue To Agent, a priority on that later activity overrides it. If the later activity sets no priority, the earlier Set Contact Priority remains. If Set Contact Priority sits after the queue activity, it overrides the queue activity. [cite:2]

Queue ranking still sits above priority

np2fdx’s team example: a higher-ranked Billing queue is offered to Team A before Sales, even when Sales holds an older, higher-priority contact. Only when Billing has no waiting contacts do those agents take Sales. When queue ranking and contact priority are the same, the longest wait is the decider. [cite:2]

Business Hours

The activity uses working hours, holidays, and overrides defined in Control Hub. Assign the flow to an entry point. Static Business Hours picks a business hour from Control Hub. Variable Business Hours needs a variable that holds a valid Business Hour ID. An invalid ID takes the error path. [cite:1]

Strategies are not deleted by this activity

The routing-strategy article tells administrators to move toward Business Hours and does not delete existing strategies. What’s new says existing customers can still use Routing Strategy to connect an entry point to a flow until that feature is decommissioned. Read holiday treatment on the Business Hours activity and on the strategy page you still have. The arithmetic is not restated as a second formula in this room. [cite:3] [cite:10]

04 · Ecosystem

Ecosystem and sister technologies

Mini map of the neighbors named on this room’s sequence. Orientation sketch, not a new product claim.

Callback: A Flow Designer activity that creates a queue task so an agent returns the call. It is not a Calling callback number and not an emergency callback. [cite:2]
Callback Default Entry Point: The Control Hub entry point, under Channel Settings, that the new interaction follows when a scheduled callback fires. [cite:2]
Set Contact Priority: The activity and the toggle that assign P1–P9. People say VIP. The articles say priority. [cite:1]
Call distribution group: A team-queue expansion step. The contact waits the configured duration, then the next group’s teams are added. [cite:2]
Call Progress Analysis: Detects an answering system or a live voice on a callback. Placement depends on courtesy versus scheduled callback. [cite:2]

Sister	What it is	Why it matters here	Config touchpoint	Typical failure	Cite
Workforce management	Shift planning outside the canvas.	Business Hours reads a Control Hub schedule. It does not build a WFM shift.	Read the subscription before using a WFO SKU. py6u9h’s list is Enterprise, CCE, and CCX.	Putting a WFM SKU on a multi-tenant flow and calling it after-hours.	[cite:4]
Quality and recording	Calling keeps its own recording store.	A callback task is not a recording policy.	Read nhvl4hw for Webex Calling and Dubber Go. Read the contact-center QM article for a queue.	Pasting one year or 30 days onto the callback flow.	[cite:5]
Emergency calling	WebRTC agents use Control Hub and RedSky.	Callback is not that test.	Read nvfbjts for the agent path. The header on that article is September 08, 2024. re-check	Treating a courtesy callback as the 933 test.	[cite:6]
Analyzer	Contact-center reporting.	Priority and callback outcomes show up as contacts, not as a VIP column these articles name.	Open Analyzer. Refresh intervals are the T3-R07 article, and they change when Cisco revises that page.	Expecting a VIP report from Set Contact Priority.	[cite:2]
CRM connectors	Desktop launch inside Salesforce, Dynamics, or ServiceNow.	Callback reason is call-associated data on the desktop, not a screen pop by itself.	Surface the variable in Flow Designer if agents must see the reason. Digital chat and email stay off the CRM connectors.	Waiting for ServiceNow to schedule the callback.	[cite:7]
Google CCAI and AI agents	Dialogflow and Virtual Agent V2.	A virtual agent can offer a callback. The Callback activity is still the queue task.	Configure the Google connector in Control Hub, then the CCAI feature. Voice agents use Virtual Agent V2.	Dragging Callback and expecting Dialogflow.	[cite:8] [cite:9]
Amazon Connect	Not named in these flow articles.	A Connect routing profile is a different console.	Read that product’s own admin guide before copying a flow.	Renaming a Connect callback flow as this activity.	[cite:1]

Integration edges

From	To	Mechanism	What moves	Cite
Control Hub business hours	Business Hours activity	Static pick, or a variable holding the Business Hour ID	Working hours, holidays, overrides	[cite:1]
Queue Contact or Queue To Agent	Callback	Activity order on the main flow or an event flow	Queue task, and preferred-agent callback when chained to Queue To Agent	[cite:1]
Schedule Callback	Callback Default Entry Point	A new interaction at the scheduled time	The flow linked to that entry point	[cite:2]
Agent Desktop	Scheduled callback	Ellipsis, Schedule and manage callbacks	Date, Call between start and end, optional reason as CAD	[cite:7]
Team queue	Next call distribution group	Park for the configured duration, then add teams	A wider eligible set. Not a new priority	[cite:2]

Sister-system trouble

Symptom	Likely sister-system cause	Check	Fix	Cite
VIP callers still wait behind a normal queue	Queue ranking on the agent’s teams outranks contact priority.	Queue ranking in Control Hub, then the priority on the activity.	Raise the queue’s rank or the contact’s priority, and say which one you changed.	[cite:2]
Scheduled callback never starts	Callback Default Entry Point is missing, or its flow is not the one you tested.	Channel Settings in Control Hub.	Point the entry point at the callback flow before you publish.	[cite:2]
Agents cannot see why the customer asked for a callback	The reason is CAD and is hidden until an administrator surfaces the variable.	Flow Designer variables on the desktop layout.	Expose the variable. Do not expect the popover to show it by default.	[cite:7]
After-hours still follows an old strategy	Moving toward Business Hours does not delete existing strategies.	The entry point’s strategies and the Business Hours activity.	Decide which object is live. Read both pages.	[cite:3]

05 · Flow

Order of operations

Confirm the queue type in Control Hub. Team assignment can expand. Agent assignment cannot. [cite:2]
Put Business Hours near the start if closed, holiday, and override need their own treatment. Overrides and holidays beat the shift when times overlap. [cite:1]
Queue the contact. Set priority on that activity or with Set Contact Priority, and know which box is later, because the later explicit priority wins. [cite:2]
For courtesy callback, place Callback after that queue activity. Choose original queue or a different queue with your eyes open. [cite:2]
For a future callback, confirm Channel Settings, place Schedule Callback, then add the Disconnect the article recommends. [cite:2]
Call Progress Analysis can be placed after Callback on a courtesy flow, or after NewPhoneContact on a scheduled or personal scheduled callback flow. [cite:2]
On the desktop, an agent on a live call uses the ellipsis, then Schedule and manage callbacks, then a date and a Call between window. [cite:7]

Orientation only. An Amazon Connect callback flow, a Teams auto attendant, and an ICM script node are different editors. Open the legacy object in its own tool and this activity on the canvas. No help page cited here prints a node-for-node map.

06 · Config

Clicks the articles print

Business Hours: drag the activity, choose Static or Variable. Variable must hold a Business Hour ID from Control Hub. Empty ordered-list inputs fail validation, and you fix them before publish. [cite:1]
Branches to wire: Overrides, Holidays, Working Hours, Default. [cite:1]
Queue Contact: Set Contact Priority is off until you enable it. Static Priority Level is P1–P9. Variable priority reads an integer flow variable. [cite:1]
Queue To Agent: identify the agent by Webex Contact Center agent ID or email. You can chain another Queue To Agent, then a Queue Contact if no preferred agent is free, and you can chain Callback for the preferred agent. [cite:1]
Callback Failed: the Wait activity between retries is at least 10 seconds and at most 72 hours. The system supports up to 10 attempts across a span of 14 days. [cite:2]
Optional ANI on the callback is how the article describes a recognizable caller ID. Read the field on the activity. The value is the number you configure, and it changes per flow. [cite:2]
Desktop: during the call, ellipsis, Schedule and manage callbacks. Date and Call between are required. Assign to any available agent or to yourself. [cite:7]
Courtesy, web, and scheduled callback are the three types the desktop article names. Web callback is a request from the site or a virtual agent, with a name and a callback number. [cite:7]

Not a procedure yet

A what’s-new note describes scheduled callback for outbound campaigns as upcoming. Do not teach that campaign path as a current click-path. Use the Flow Designer and desktop articles above. [cite:10]

07 · Limits

Numbers the articles print

Item	Value	Source	Verified?
Static priority	P1 highest through P9 lowest	[cite:1]	Quoted
Unset or out-of-range priority	10	[cite:1]	Quoted for Queue Contact and Queue To Agent
Variable priority range	Integer 1 through 9	[cite:1]	Quoted
Callback retry wait	Minimum 10 seconds, maximum 72 hours	[cite:2]	Quoted. Header October 01, 2026
Callback retries	Up to 10 attempts across 14 days	[cite:2]	Quoted
Different-queue callback	End of that queue, no skills, default priority	[cite:2]	Quoted
Expansion delay	The duration configured on the call distribution group	[cite:2]	The article does not print one global number of seconds
Outbound campaign scheduled callback	Described as upcoming	[cite:10]	Not used as a current procedure

08 · Trouble

What the pattern usually broke

Symptom	Wrong story	What you can cite	Do this	Cite
Callback lost the caller’s skills	“Callback always resets the contact.”	Only a different queue drops skills and priority and sends the contact to the end.	Put the callback back on the original queue if place-in-line matters.	[cite:2]
The customer stays on the line after scheduling	Schedule Callback ends the call by itself.	For best results, the article recommends Disconnect immediately after Scheduled Callback so the current call ends.	Add the activity, then publish.	[cite:2]
Priority 1 was set and the contact still sorts last	P1 means first in every queue the agent can see.	A higher queue ranking is served first. Out-of-range variables become 10.	Read ranking on the queues and the value in the variable.	[cite:2]
Holiday audio plays during the shift	Working hours always win.	Holidays and overrides take their branches regardless of the shift when the times coincide.	Read the holiday list and the override list in Control Hub.	[cite:1]
Variable business hours always errors	Any string name works.	The variable must hold the Business Hour ID. An invalid ID takes the error path.	Copy the ID from Control Hub into the variable.	[cite:1]
The team queue never widens	Overflow is a Flow Designer percent.	Expansion is the next call distribution group after the configured duration. Agent queues do not expand on a timer.	Open the queue type before you edit the flow.	[cite:2]
Call Progress Analysis never runs	One placement works for every callback.	Courtesy: after Callback in the main flow. Scheduled or personal scheduled: after NewPhoneContact in the main flow.	Move the activity to the placement the article names.	[cite:2]

09 · Self-question ladder

L1Where do you place Callback?

After Queue Contact or Queue To Agent. [cite:1]

L1What does a different callback queue do to skills?

The contact goes to the end of that queue with no skills and with default priority. [cite:2]

L2What must exist before Schedule Callback is useful?

The Callback Default Entry Point under Channel Settings in Control Hub. [cite:2]

L2Which Business Hours branch wins over the shift?

Overrides and holidays, when their times coincide with the shift. Default is the leftover. [cite:1]

L2What is P1?

The highest static priority. P9 is the lowest. [cite:1]

L3A priority variable returns 15. What priority is used?

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

L3Set Contact Priority is before Queue Contact, and Queue Contact also sets P5. Which one is used?

The queue activity’s priority. A later explicit priority overrides the earlier activity. [cite:2]

L3Why can a lower-priority Billing contact beat a higher-priority Sales contact?

Queue ranking. Billing is offered first while it still has waiting contacts. [cite:2]

L4How many callback retries, and over what span?

Up to 10 attempts across 14 days. Each Wait is between 10 seconds and 72 hours. [cite:2]

L4Where does Call Progress Analysis go on a scheduled callback?

It can be placed after NewPhoneContact in the main flow. Courtesy callback can place it after Callback. [cite:2]

10 · Lab

Draw one flow, then point at Control Hub

Prereq: a lab tenant you are allowed to change. Production entry points are out of scope. Read licenses on the subscription. The flow articles do not name them.
On paper, draw Start Flow, Business Hours with four branches, Queue Contact, Callback, and Disconnect. Mark Disconnect as the scheduled-callback neighbor.
Write two callback rows: original queue, and a different queue. Fill skills, priority, and place in line for each.
Set a variable priority of 15 and write 10 next to it. Set P1 on a later Queue Contact and write which activity wins.
Open the queue. If it is team assignment, name the call distribution groups and the duration configured between them. If it is agent assignment, write “no timed expansion.”
In Control Hub, find Channel Settings and the Callback Default Entry Point. Write the flow name attached to it.
On a test call, open the ellipsis and find Schedule and manage callbacks. Do not save a callback against a real customer number.
Reflection: which pattern did you used to call VIP, and which article name will you use instead?

11 · Quiz

Eight checks

0 revealed

Q1MCQ

Callback belongs:

Before any queue activity
After Queue Contact or Queue To Agent
Inside a WFM schedule
On the Calling E2EE toggle

Reveal

B. [cite:1]

Q2Scenario

The callback is sent to a different queue. What happens to skills and place in line?

Reveal

End of the selected queue, no skills, default priority. The original queue would have kept position, skills, and priority. [cite:2]

Q3MCQ

For best results, immediately after Schedule Callback the article recommends:

Get Queue Info
Disconnect
A WFO SKU
Nothing, because the caller is already gone

Reveal

B. [cite:2]

Q4MCQ

Static priority P9 is:

Highest
Lowest of the static list
The default when the toggle is off
A queue ranking

Reveal

B. P1 is highest. Unset priority is 10, which is outside P1–P9. [cite:1]

Q5Scenario

Billing is ranked above Sales. Sales holds an older P1 contact. Billing holds a P9 contact. Who does Team A get first?

Reveal

The Billing contact, while Billing still has waiting contacts. Queue ranking is applied before that priority comparison. [cite:2]

Q6MCQ

A holiday that falls inside the shift takes:

Working Hours
The Holidays branch
Whatever the old routing strategy still says, and Business Hours is ignored
The error path

Reveal

B. Holidays win regardless of the shift when today is on the holiday list. [cite:1]

Q7MCQ

Agent-assignment overflow on a timer:

Uses call distribution groups
Is not how those queues expand
Is the Callback activity
Is P1

Reveal

B. Timed target expansion is the team-queue call distribution group. [cite:2]

Q8Scenario

Call Progress Analysis is after Callback on a personal scheduled callback. Where can the article place it instead?

Reveal

It can be placed after NewPhoneContact in the main flow. After Callback is a placement the article names for courtesy callback. [cite:2]

12 · Audio

90 seconds. Callback after the queue activity. A different queue drops skills. Schedule Callback needs the default entry point. Disconnect immediately after is the article’s recommendation. VIP is P1 through P9, and 10 is the default. Queue ranking can still go first.

No mp3 shipped.

45 seconds. Do not teach an outbound-campaign callback that the what’s-new page still calls upcoming.

13 · Interview

“Courtesy callback sits after Queue Contact or Queue To Agent. If I keep the original queue, the contact keeps position, skills, and priority. If I move queues, it goes to the end with no skills and default priority. Scheduled callback needs the Callback Default Entry Point under Channel Settings. The article recommends Disconnect immediately after so the current call ends, and the later call follows that entry point’s flow. After-hours is Business Hours: overrides and holidays beat the shift, then working hours, then default. I do not delete old routing strategies just because Business Hours exists. Existing customers can keep using Routing Strategy until that feature is decommissioned. What people call VIP is Set Contact Priority, P1 highest through P9, and 10 when the value is missing or outside 1 to 9. A later queue activity overrides an earlier priority. Queue ranking can still serve a higher-ranked queue before a higher-priority contact in a lower-ranked queue. Overflow on a team queue is the next call distribution group after the configured wait. Agent-assignment queues do not expand on a timer. I do not describe a VIP flag, a holiday formula, or an outbound-campaign callback the what’s-new page still marks as upcoming.”

14 · Citations

Retrieved 2026-10-14. Mirrors cites/T8-R02.md.

Build and manage flows with Flow Designer — help.webex — article nhovcy4 — help.webex.com article nhovcy4 — retrieved 2026-10-14. Callback after Queue Contact or Queue To Agent. Queue To Agent chaining. Set Contact Priority off by default, default 10, P1–P9, variable 1–9. Business Hours branches and Control Hub IDs.
Understand Routing and Queueing in Webex Contact Center — help.webex — article np2fdx — help.webex.com article np2fdx — retrieved 2026-10-14. Header October 01, 2026. Same-queue versus different-queue callback. Schedule Callback. Callback Default Entry Point is the prerequisite. Disconnect immediately after is recommended for best results. CallbackFailed waits. Call Progress Analysis can be placed after Callback or after NewPhoneContact. Queue ranking example. Call distribution groups. Set Contact Priority override order.
Set up routing strategies — help.webex — article nfrs2adb — help.webex.com article nfrs2adb — retrieved 2026-10-14. Move toward Business Hours. Existing strategies remain. Holiday-priority arithmetic stays on that article.
Webex WFO: Feature Specific SKUs — help.webex — article py6u9h — help.webex.com article py6u9h — retrieved 2026-10-14. Header June 09, 2026. Enterprise, Contact Center Enterprise, and Contact Center Express. Not a multi-tenant flow activity.
Manage call recording for Webex Calling — help.webex — article nhvl4hw — help.webex.com article nhvl4hw — retrieved 2026-10-14. Calling retention. Not WxCC quality-management retention and not a callback setting.
Provision Emergency Calling in Webex Contact Center for Agents — help.webex — article nvfbjts — help.webex.com article nvfbjts — retrieved 2026-10-14. Header September 08, 2024. re-check WebRTC agents use Control Hub and RedSky. Not a Flow Designer callback.
Manage your calls in Agent Desktop — help.webex — article mmcf7p — help.webex.com article mmcf7p — retrieved 2026-10-14. Header date was not in the extract. re-check Courtesy, web, and scheduled callback. Ellipsis path. Callback reason as CAD, hidden until Flow Designer surfaces it.
Configure Virtual Agent-Voice in Webex Contact Center — help.webex — article n6gaghu — help.webex.com article n6gaghu — retrieved 2026-10-14. Google CCAI connector in Control Hub, then the CCAI feature. Not the Callback activity.
Use AI agents for customer interactions — help.webex — article s0qro1 — help.webex.com article s0qro1 — retrieved 2026-10-14. Header August 25, 2026. Virtual Agent V2. Not a substitute for the Callback activity.
What’s new for administrators in Webex Contact Center — help.webex — article a1gx3h — help.webex.com article a1gx3h — retrieved 2026-10-14. Header October 08, 2026. Existing customers can still use Routing Strategy to connect an entry point to a flow until that feature is decommissioned. Scheduled Callback for outbound campaigns is announced as upcoming availability. Not a current procedure in this room.

15 · Re-engineer later

Open the Callback activity on the canvas for ANI and output variables this room did not quote. Those fields change when Cisco updates the activity.
Read the configured duration on each call distribution group in the live queue. np2fdx does not print one global number of seconds.
When a1gx3h stops calling outbound-campaign scheduled callback upcoming, replace the warning with the click-path that article then prints.
Confirm the mmcf7p header date. The extract used on 2026-10-14 did not include it.
ICM script parity stays in T6-R04. Enterprise scripting stays in T4.

Sources and go deeper

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

Wikipedia Webex (Wikipedia) last checked 2026-10
Vendor doc Webex Help Center last checked 2026-10
DevDocs Webex developer documentation last checked 2026-10
DevDocs Webex developer getting started last checked 2026-10
Community Webex community last checked 2026-10
SRND Cisco Collaboration design zone last checked 2026-10
RFC RFC 3261 SIP: Session Initiation Protocol last checked 2026-10
Port table IANA service name and port number registry last checked 2026-10
Port table Port reference for Webex Calling last checked 2026-10
Wikipedia Call centre (Wikipedia) last checked 2026-10
Wikipedia Interactive voice response (Wikipedia) last checked 2026-10
Release notes What's new for administrators in Webex Contact Center last checked 2026-10
RFC RFC 3263 Locating SIP Servers last checked 2026-10
RFC RFC 3264 An Offer/Answer Model with SDP last checked 2026-10
Wikipedia Session Initiation Protocol (Wikipedia) last checked 2026-10
Vendor doc help.webex.com article nhovcy4 last checked 2026-10
Vendor doc help.webex.com article np2fdx last checked 2026-10
Vendor doc help.webex.com article nfrs2adb last checked 2026-10
Vendor doc help.webex.com article py6u9h last checked 2026-10
Vendor doc help.webex.com article nhvl4hw last checked 2026-10
Vendor doc help.webex.com article nvfbjts last checked 2026-10
Vendor doc help.webex.com article mmcf7p last checked 2026-10
Vendor doc help.webex.com article n6gaghu last checked 2026-10
Vendor doc help.webex.com article s0qro1 last checked 2026-10
Vendor doc help.webex.com article a1gx3h last checked 2026-10

sources.json for this page.