✅
Study AlwaysNotes
build
individual
Schedules
first,Topic |
thenExplanation |
assemble
them
| Schedule |
A time-based object that determines when routing or flow logic is active. |
| Schedule Group |
Groups multiple schedules into aOpen, Closed, and Holiday categories for routing. |
| Architect Usage |
Architect uses schedules to determine how inbound and outbound interactions should be handled. |
| Recurrence Support |
Schedules can be one-time or repeating (daily, weekly, monthly, yearly, or custom iCal rule). |
| Evaluation Order |
In Architect: Emergency → Holiday → Closed → Open |
| Default Branch |
If no schedule matches, Closed is the default branch in Evaluate Schedule Group. |
| Time Zone |
Set on the Schedule Group — most common misconfiguration is a wrong or missing time zone. |
Navigation
| Task |
Navigation |
| View Schedules |
Admin → Routing → Scheduling |
| Create Schedule |
Admin → Routing → Scheduling → Add Schedule |
View Schedule ComponentsGroups |
Admin → Routing → Scheduling → Schedule Groups |
| Use in Architect |
Architect → Open Flow → Add Evaluate Schedule Group action |
Schedule Configuration Fields
| Field |
Description |
Example |
| Schedule Name |
Unique identifier — no spaces recommended for flow references |
Division |
Administrative ownership |
Repeating Event |
Off = one-time only; On = recurring |
Start / End Date |
Date boundsname for the schedule |
Start / End Time |
Time window; or use All DayUS_Support_BusinessHours |
Recurrence RuleDivision |
HowDetermines oftenadministrative itownership repeatsand (Daily,access |
Weekly, Monthly, Yearly, Custom iCal)Home |
StartRepeating ConditionEvent |
OnEnables Date,recurring orschedule Nextlogic |
Time Criteria MetEnabled |
| Start Date |
Date when the schedule starts |
2026-03-01 |
End ConditionDate |
Date when the schedule ends |
2026-12-31 |
| Start Time |
Time when the schedule starts |
08:00 |
| End Time |
Time when the schedule ends |
18:00 |
| All Day |
Enables full-day schedule instead of start/end times |
Disabled |
| Repeats Every |
Defines recurrence pattern |
Weekly |
| Start Option |
Defines when recurrence begins |
On Date |
| End Option |
Defines when recurrence stops |
No End Date,Date |
After
N
Occurrences,iCal orRule |
OnAdvanced recurrence rule configuration |
FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR |


Schedule Types
| Schedule Type |
Example |
| One-Time |
July_4_Closure |
| Daily |
After_Hours_Daily |
| Weekly |
Mon_Fri_BusinessHours |
| Monthly |
First_Monday_Maintenance |
| Yearly |
Christmas_Holiday |
| Advanced Rule |
FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR |
Example business-hours schedule:
| Field |
Value |
| Name |
US_Support_BusinessHours |
| Repeating Event |
Enabled |
| Repeats Every |
Weekly |
| Days |
Monday–Friday |
| Start Time |
08:00 |
| End Time |
18:00 |
| End Option |
No End Date |
RecurrenceSchedule Types
Group Configuration
Type |
Use Case |
One-Time |
Single maintenance window, one-off closure |
Daily |
Every day, or every N days |
Weekly |
Selected weekdays (e.g., Mon–Fri) |
Monthly |
Specific day of month or weekday pattern |
Yearly |
Annual holidays (e.g., Dec 25 every year) |
Custom iCal Rule |
Advanced recurrence syntax |
iCal example — Monday through Friday:
FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR
Creating a Schedule
Admin → Routing → Scheduling
Click Add Schedule
Enter a unique Schedule Name and select Division
Toggle Repeating Event On or Off
Set Start Date and Start / End Time (or check All Day)
If repeating: configure recurrence type, start condition, and end condition
Click Save



Schedule Groups
Components
FieldComponent |
Description |
NameOpen Schedule |
UniqueDefines identifierwhen the business is open |
DivisionClosed Schedule |
AdministrativeDefines ownershipafter-hours or closure periods |
TimeHoliday ZoneSchedule |
AllDefines scheduleholiday evaluations use this time zonedates — criticaloverrides for accuracyOpen |
OpenTime HoursZone |
SchedulesApplied representingat businessthe hoursSchedule Group level — determines when schedules activate |
ClosedEmergency HoursGroup |
SchedulesSeparate representingobject after-hours | that
overrides all Holiday | schedule-based Holidaylogic /when special closure schedulesactivated |
⚠️ Time zone is the mostMost common misconfiguration.misconfiguration: A schedule group set toSetting the wrong time zone will route calls incorrectly — especially after Daylight Saving Time transitions. Always alignon the timeSchedule zoneGroup, causing callers to thehit businessclosed locationor theholiday grouppaths serves.at unexpected times.
CreatingArchitect aEvaluation Order
Evaluate Schedule Group
↓
AdminEmergency? → Routing → Scheduling → click Schedule Groups tab
Click Add Schedule(Emergency Group Enteractivated?)
name,↓
selectHoliday? division,(Current and select date/time zone matches Assigna schedulesHoliday toschedule?)
each↓
category:Closed? (Current Clickdate/time + besideoutside Open Hoursschedule?)
→↓
searchOpen and(Default select— schedulecurrent →date/time clickmatches Open schedule)
If nothing matches, the AddClosed
Repeatbranch foris Closedtaken Hoursby and Holiday as needed
Click Save

default.
How Schedule Groups Work in Routing
In Call Routing (AdminArchitecture
→Customer RoutingInteraction
→ Call Routing)
The↓
Call Route referencesor aArchitect Flow
↓
Schedule / Schedule Group directly:
Evaluation
Open Flow — executes when schedule group evaluates to Open
Closed Flow — executes when schedule group evaluates to Closed
Holiday Flow — executes when a Holiday schedule is active (optional — can fall back to Closed Flow)
In Architect Flows
Use the Evaluate Schedule Group action inside a flow to branch on↓
Open / Closed / Holiday logic/ — useful when routing decisions need to happen mid-flow rather than at the entry point.
Routing Decision Logic
Incoming CallEmergency
↓
CallMenu Route/ checksQueue Emergency/ GroupVoicemail ↓/ NoExternal emergencyTransfer active/ →
↓
Schedule Group evaluated
↓
┌─────────────┬───────────────┬──────────────┐
│ Open │ Closed │ Holiday │
│ Flow │ Flow │ Flow │
└─────────────┴───────────────┴──────────────┘Disconnect
Real Flow Scenarios
CommonScenario 1 — Business Hours Menu
Caller Enters Flow
↓
Evaluate Schedule PatternsGroup
↓
Open
↓
Play Welcome Prompt → Send to Menu → Route to Agent
Scenario 2 — After-Hours Voicemail
Caller Enters Flow
↓
Evaluate Schedule Group
↓
Closed
↓
Play Closed Prompt → Route to Voicemail
Scenario 3 — Holiday Transfer
Caller Enters Flow
↓
Evaluate Schedule Group
↓
Holiday
↓
Play Holiday Prompt → Transfer to External Number
Scenario 4 — Emergency Shutdown
Caller Enters Flow
↓
Evaluate Schedule Group
↓
Emergency
↓
Play Issue Prompt → Disconnect Call
Implementation Steps
PatternStep |
Schedule SetupAction |
Mon–FriStep 8am–6pm business hours1 |
WeeklyNavigate recurrence,to Mon–Fri, 08:00–18:00Admin → assignRouting to→ Scheduling |
| Step 2 |
Click OpenAdd HoursSchedule |
After-hoursStep (everything outside Open)3 |
NoEnter explicit closedunique schedule needed — anything not matching Open = Closedname |
AllStep US federal holidays4 |
CreateSelect one yearly schedule per holiday → assign all to Holidaydivision |
HolidayStep with custom message5 |
AssignChoose holidayone-time schedulesor torepeating Holiday category; build a dedicated Holiday Flow in Architectevent |
MaintenanceStep window (one-time)6 |
One-TimeConfigure schedule,start specificdate, date/end date, and time →range (or All Day) |
| Step 7 |
Configure recurrence settings if repeating |
| Step 8 |
Save the schedule |
| Step 9 |
Create a schedule group and assign schedules to Open / Closed Hours/ Holiday |
| Step 10 |
Set the correct time zone on the schedule group |
| Step 11 |
Use the schedule group in call routing or Architect |
Naming Conventions
Convention
FormatResource |
Example |
<Region>_<Dept>_BusinessHoursSchedule |
US_Support_BusinessHours |
<Region>_<Dept>_Holiday_<Name>Holiday Schedule |
US_Support_Holiday_ChristmasUS_Support_Christmas |
<Region>_<Dept>_MaintenanceMaintenance Schedule |
EU_Support_MaintenanceUS_Support_MaintenanceWindow |
| Schedule Group |
US_Support_Main_SG |
Recommended pattern: <Region>_<DeptDepartment>_ScheduleGroup_<Purpose>
Best Practices
| Practice |
Reason |
| Use clear schedule names |
US_Support_ScheduleGroupMakes routing easier to understand and maintain |
| Separate business hours and holidays into distinct schedules |
Improves flexibility and troubleshooting |
| Always use Schedule Groups for production routing |
Simplifies open/closed/holiday branching |
| Set the correct time zone on the Schedule Group |
Prevents incorrect routing behavior |
| Test all branches (Open, Closed, Holiday, Emergency) |
Ensures callers hear the correct experience |
| Review holiday schedules annually |
Keeps routing accurate over time |
Troubleshooting
| Issue |
Likely Cause |
FixResolution |
CallsFlow routingalways toroutes wrong flowClosed |
Time zone mismatch onor no active Open schedule group |
Verify schedule times and schedule group time zone matches business location |
ScheduleHoliday notpath triggeringnever triggers |
RecurrenceHoliday rule misconfigured |
Review start/end conditions and recurrence settings |
Calls always treated as closed |
Schedule groupschedule not assigned to call routegroup |
EditAdd callholiday routeschedule and assign theto schedule group |
HolidayEmergency routingpath does not workingwork |
HolidayEmergency schedulesgroup not activated or not assigned to Holiday categoryflow |
MoveVerify holiday schedules to the Holiday slot in theemergency group setup and flow logic |
DST-relatedRecurring routingschedule errorsnot firing |
TimeRecurrence zonesettings doesincorrect |
Review repeating event settings and end conditions |
External transfer not observe DST automaticallyreached |
UseHoliday abranch namedmisconfigured |
timeCheck zoneArchitect (e.g.,holiday America/Chicago)branch notand aexternal UTCnumber |
offset
| Schedule group unavailable in flow |
Permission or object visibility issue |
Confirm access and division permissions |
KeyInterview FactsCheat for Exam / Interview
Sheet
TopicQuestion |
Answer |
WhereWhat areis a schedule in Genesys Cloud? |
A time-based object that determines when routing or flow logic is active |
What can schedules configured?be used for? |
AdminBusiness →hours, Routingafter-hours, →holidays, Schedulingrecurring events, and special situations |
| What is a schedule group? |
A containergrouping combiningof schedules into Open, Closed, and Holiday schedules into a routing definitioncategories |
What evaluatesis the scheduleevaluation grouporder in a flow?Architect? |
TheEmergency Evaluate→ ScheduleHoliday Group→ actionClosed in Architect |
Can you have multiple open schedules in one group? |
Yes — multiple schedules can be assigned to→ Open Hours |
What handleshappens routingif outsidenothing Open Hours?matches? |
The Closed Flow — no explicit closed schedule is requiredthe default path in Evaluate Schedule Group |
What overridesis schedule-basedthe routingmost entirely?common misconfiguration? |
AnWrong activetime Emergencyzone set on the Schedule Group |
See Also
Emergency Groups — overrides all schedule-based routing when activated
Call Routing — where schedule groups are assigned to inbound numbers
Architect Overview — the Evaluate Schedule Group action in flow logic