Schedule-Based Call Routing: Setup, Options, Examples

Schedule-based call routing sends callers to different destinations depending on the time of day and day of week. In CallFlow, you attach time windows to specific forwarding targets so each team, buyer, or agent has its own hours and after-hours behavior. Route IVR paths or queues to targets that have their own hours. This per-target model is more granular than a single “open/closed” switch and is critical when you run multiple shifts, serve multiple regions, or sell calls to buyers with distinct operating windows.

Key takeaways

• Use schedule windows to route by business hours and shifts. Always design an explicit after-hours path.
• Pair schedules with queues and IVR so callers get handled (or informed) even when a team is closed.
• Test boundary minutes, local-hour differences, and overlapping windows. Avoid ambiguous routes and set a global fallback.
• Build windows that reflect each team’s local hours; sanity-check daylight saving transitions.
• Keep a fallback path for holidays or outages so no call dead-ends.

What schedule-based call routing is (and how it works)

Schedule-based call routing means your flow decides where to send the call based on defined time-of-day and day-of-week windows. For example, Mon–Fri 9:00–17:00 route to your sales ring group; outside those hours, route to voicemail, an on-call mobile, or a queue with hold music.

How it’s configured in CallFlow:

• Per-target schedules. Each forwarding target—PSTN number, SIP endpoint, or browser agent—can have its own time windows. Route IVR paths or queues to targets that have their own hours.
• Multiple routing strategies. Within a window, use priority, weighted, round-robin, or simultaneous ring to distribute calls.
• Local-hour windows. Define windows that match each team’s local hours. CallFlow evaluates each target’s windows; if no window matches, it follows the next rule or fallback.

Why per-target beats a global switch:

• Granularity. Different teams and buyers have different hours and holidays.
• Control. You can keep support open while sales is closed, or cover weekends with an on-call cell without touching weekday routes.
• Resilience. If a team is capped or down, another target with its own window can take overflow.

If you’re new to routing strategies overall, see the fundamentals in Call routing: methods and use cases.

Common patterns that actually work

Business hours and after-hours

• Open hours: Route to a ring group (simultaneous or round-robin) of your on-shift team. For example, Mon–Fri 8:30–17:30.
• After-hours: Route to one of:
  • Voicemail with a clear callback window.
  • A queue with hold music if you still want to accept calls with some delay.
  • An on-call mobile number for emergencies.

Example: A dental office answers in-clinic Mon–Thu 9–5 via simultaneous ring to front desk lines. After-hours and Fri–Sun, calls route to an IVR that offers “Press 1 for emergency” (goes to on-call) or “Press 2 to leave a message for scheduling.”

Multi-region coverage with local-hour windows

A roofing company advertises in Eastern and Mountain states. Use separate windows that reflect each team’s local hours:

• Assign one local number per state group for better pickup rates and geo relevance.
• ET calls hit the “Northeast Sales” group with windows that reflect Eastern hours.
• MT calls hit the “Front Range Sales” group with windows that reflect Mountain hours.
• If one team is closed, overflow to the other’s after-hours path (queue or voicemail) rather than ringing a closed team.

On-call and weekend coverage

Shift-based call routing with rotation:

• Create a target per on-call cell (e.g., “On-call A,” “On-call B”).
• Give each target a weekly or daily window (e.g., Sat–Sun for A this week, B next week).
• Use simultaneous ring to add a backup device (e.g., office SIP phone or a second mobile) for redundancy.
• Add a whisper message like “Weekend emergency” so the answering person knows context before they speak.

Lead-gen and buyer windows

For pay-per-call:

• Create a target per buyer with its own operating windows aligned to that buyer’s hours.
• During a buyer’s open window, route by priority to that buyer; during overlap windows, distribute by weighted or round-robin so you hit quotas fairly. See more on trade-offs in Weighted call routing.
• Use duplicate-caller rules to prevent re-selling the same caller within your cooling period.
• Apply daily and concurrent caps per buyer target; if hit, overflow to the next available buyer or to a voicemail branded for your network.

Design your schedule map before you click anything

Map entry numbers and paths

• Inventory your entry points:
  • Which phone numbers (local and toll-free) will you advertise?
  • Do callers first hit an IVR (Press 1 Sales, 2 Support), or go straight to a queue?
• For each number and IVR option, note:
  • Primary business hours.
  • After-hours behavior.
  • Local hours by team/region.
  • Fallback route if no schedule matches.

Choose routing per window

Within each open window, pick how to distribute calls:

• Priority: Calls try Target A first, then B, then C. Use when there’s a clear primary team or top buyer.
• Weighted: Proportionally allocate calls (e.g., A 60%, B 40%). Good for balancing among teams or buyers by budget or capacity.
• Round-robin: Cycle evenly through a set of agents or numbers to spread load.
• Simultaneous ring: Ring several devices at once for fastest answer in short-staffed hours or for on-call escalation.

Define after-hours handling

Pick one or more:

• Voicemail with a concise prompt and a promise of when you’ll call back.
• Queue with hold music for moderate after-hours coverage when staff occasionally picks up.
• On-call forward to a rotating mobile for urgent issues.
• Info-only IVR path (hours, website URL, emergency instructions) so callers get clarity without agent time.

Set fallbacks and overflow

• If no schedule window matches (holiday, DST shift, or a misconfiguration), route to a closed-hours IVR or voicemail—never to a dead-end.
• Define overflow per window:
  • If concurrency is exceeded, overflow to a secondary queue or voicemail.
  • If a buyer/team hits a daily cap, route to the next priority target.

Step-by-step setup in CallFlow

Create numbers and targets

1. Provision a local or toll-free number from your prepaid wallet. There’s no subscription commitment; you pay only for usage.
2. Create forwarding targets:
   • PSTN phone numbers (desk or mobile).
   • SIP endpoints.
   • Browser agents for users logged into the CallFlow app.
3. Name targets clearly by team/shift (e.g., “Sales ET,” “Support MT,” “On-call Week A”).

Build schedules

1. For each target, define time windows with day-of-week and start/stop times.
2. Define windows that reflect each team’s local hours so staff doesn’t have to translate times.
3. Include weekend and holiday variations as needed by creating alternate windows or temporarily disabling open windows during closures.

Attach schedules to routing rules

1. Choose the routing strategy per window: priority, weighted, round-robin, or simultaneous ring.
2. For IVR menus, route each option to targets with their own hours so Sales can close earlier than Support. For ideas on menu design, see IVR for business: structure and prompts.
3. Configure queues with hold music where you expect bursts or short staffing.
4. Enable whisper messages to identify the shift or queue when an agent answers (e.g., “LeadGen — Phoenix”).
5. Set daily and concurrent caps per target if you anticipate spikes. If a cap triggers, overflow to the next target or your after-hours path. For right-sizing concurrency, see Concurrent call capacity planning.

Test and verify

• Turn on call recording where appropriate; confirm consent requirements with your legal counsel before recording.
• Place test calls:
  • Just before open and just after open (e.g., 8:59 and 9:01).
  • Just before close and just after close.
  • Across regions to confirm windows reflect local hours.
  • During overlapping windows to confirm the intended rule fires.
• Check real-time call logs to see which rule and window matched; use live call monitoring if you need to listen to active calls. Schedule email reports to track answer rates by window.

After-hours options compared

Option	When to use	Pros	Trade-offs
Voicemail	Non-urgent callbacks; teams that work next-day follow-up	Low agent load; clear expectations if prompt is specific	Slower response; some callers may hang up
Queue with hold music	Short-staffed evenings; expect intermittent pickup	Captures more calls without full staffing	Higher drop risk if hold times grow; must monitor concurrency
On-call forward	Urgent support; high-value leads that justify immediate response	Fastest human response; simple rotation via schedule windows	Agent fatigue; must maintain accurate on-call numbers
IVR info path	Inform-only use cases (hours, website, emergency instructions); closures/holidays	Zero agent load; gives callers clear guidance	No live handling; may frustrate sales callers

Example configurations:

• Small clinic: Business hours to front desk ring group; after-hours IVR with “Press 1 for urgent nurse line” (on-call), “Press 2 to leave a message for scheduling.”
• Home services contractor: Evenings route to a queue with hold music; overnight use a separate path to an on-call tech or voicemail with a morning callback commitment.
• Agency with rotating manager: After-hours route to “Manager A” this week and “Manager B” next week via two targets with alternating weekly windows; add simultaneous ring to a backup line to catch missed calls.

Advanced rules that pair well with schedules

• VIP and urgent callbacks during closed hours: Publish a separate number that routes with priority to a small, always-on ring group. Use a distinct whisper (“Priority line”) so agents know to answer immediately.
• Geographic + schedule chaining: First route by caller state to the nearest team, then evaluate that team’s local business hours. If closed, push to that region’s after-hours path, not the other region’s open sales line unless you’ve planned for it. For franchise scenarios that need territory-based forwarding and brief IVR prompts, see franchise call routing.
• Caps by window: During high-spend campaigns, enforce per-target daily and concurrent caps within open windows to protect teams and buyers. When caps hit, overflow to a secondary queue or closed-hours voicemail.
• Whisper messages: Tell the agent which queue/window the call came from—“Weekend On-call,” “MT Sales,” or buyer name—so they open the conversation correctly.
• Validation and reporting: Check real-time call logs to see which rule and window matched; use live call monitoring if you need to listen to active calls. Schedule emailed reports by team to compare answer rates and call volume by window.

Testing, monitoring, and maintenance

Boundary testing

• Opening/closing minutes: Validate the minute boundaries and verify inclusive/exclusive behavior (e.g., does 17:00 route to closed or open? Set it intentionally).
• Weekends: Confirm that Sat/Sun windows match your staffing plan; many teams forget to disable Sunday.
• Daylight saving time (DST): Build windows that reflect local hours; sanity-check DST transitions, including the short and long days in spring/fall.

Read call logs and analytics

• For each number and IVR path, review:
  • Which schedule window matched each call (timestamp and window).
  • Answered vs. missed, by window.
  • Use scheduled email reports to review answer rates and call volume by window.
• If after-hours voicemail volume spikes, consider adding an on-call window or a short queue.

Routine checklist (quarterly or when staffing changes)

• Review all schedule windows for each target and confirm they still reflect local hours.
• Confirm on-call numbers and backups are still correct.
• Test overflow routes (secondary queues, voicemail) still work.
• Revisit caps per buyer/team to match current budgets and staffing.
• Update IVR prompts to reflect hours changes and holiday closures.

Troubleshooting and pitfalls

• Overlapping windows cause ambiguity:
  • Symptom: Calls sometimes route to the “wrong” team during overlap periods.
  • Fix: Order rules intentionally (e.g., VIP first, then Sales, then Support) or separate by IVR option so each path has unambiguous windows.
• Windows reflect the wrong local hours on a target:
  • Symptom: Calls start ringing an hour early/late around DST or across regions.
  • Fix: Adjust that target’s windows to line up with the team’s local hours; re-test boundary minutes.
• No-match case on holidays or ad-hoc closures:
  • Symptom: Calls don’t hit any open window and drop or bounce.
  • Fix: Add a closed-hours IVR or voicemail fallback that always exists outside windows. For planned closures, disable open windows temporarily and enable the IVR info path with holiday messaging.
• Under-sizing concurrent capacity during peaks:
  • Symptom: Long holds or missed calls in busy windows.
  • Fix: Increase simultaneous ring targets, add a queue with hold music, and set realistic concurrent caps with overflow.
• Calls don’t follow expected windows:
  • Action: Capture specific examples with timestamps, called number, caller ID, and observed path. Check logs for the matching rule. If behavior still looks off, contact support with those details so we can trace the schedule evaluation.

What to do next

• Sketch your windows by team, buyer, and region. Note local hours and after-hours behavior.
• Choose a routing strategy per window (priority, weighted, round-robin, or simultaneous ring) and set clear fallbacks.
• Build targets, attach schedules, and test boundary minutes and DST scenarios.
• Turn on caps, whisper messages, and recording (with consent) where they add value.

If you need to route by business hours without contracts or monthly subscriptions, you can try CallFlow with a prepaid wallet and provision numbers instantly at register. For help designing complex multi-zone or on-call schedules, reach out at contact.