Per-target call windows: schedule hours per buyer or agent

Set per-target call windows by editing each buyer or agent target. Pick its local time zone, and set the days and hours it can take calls. Outside those hours, the router (the rule that decides who to ring next) skips that target. Windows then work with daily and concurrent caps to control spill and overflow to a short queue, then voicemail.

What per-target call windows do (and what they don’t)

A per-target call window is the time range when a specific target (a buyer or agent you forward calls to) can receive calls. If a call arrives outside that target’s window, the system skips that target and tries the next rule in your routing. Windows don’t hold or delay a call; they only decide if that target is eligible to ring right now.

Start on paper. Write each buyer’s local hours, their quiet hours (times you must not ring them), and their time zone. If you serve multiple regions (US, India, Philippines, Thailand, Bangladesh, Pakistan), you’ll often need different windows and time zones per buyer. This prep helps you avoid mistakes when you click through settings.

At a high level, the order is simple. For each target, the router checks that target’s window and then its caps. If a target is closed or capped, the platform skips it. It then moves to the next target using your chosen routing method: priority (try in set order), weighted (split by percent), round-robin (rotate), or simultaneous ring (ring several at once). If no targets can take the call, send the caller to a short queue (a brief waiting line with hold music), then voicemail.

We’ll use a running example: a dental pay-per-call campaign with three buyers in different US time zones. Buyer A in Eastern Time takes 9:00–17:30, Buyer B in Central Time takes 12:00–20:00, and Buyer C in Pacific Time takes 10:00–16:00. After hours, we send callers to a 20-second queue, then to voicemail with a clear message and a callback plan.

If you need a refresher on capacity controls, see daily and concurrent call caps. If after-hours handling needs polish, see after-hours call routing.

Set per-target call windows for each buyer

You’ll set windows per target, not per campaign. That keeps each buyer’s hours clean and avoids time-zone math in your head.

1. Open the target and set its time zone. Pick the buyer’s local time zone, not yours. This makes daylight saving time (DST) shifts and regional holidays easier to manage later. If you leave a US buyer on UTC or an India buyer on US time, you’ll wake them at night or miss their peak hours.

2. Choose open days and the start/end times, then save. A common office pattern is Monday–Friday, 9:00–17:30. Use the on-screen 24-hour or 12-hour time controls. Save after each target to avoid mixing up windows between buyers. This creates the core “call buyer schedules” you’ll rely on every day.

3. Keep each attempt short so you avoid personal voicemail. If your system lets you set ring time, use about 15–25 seconds on a buyer’s phone before trying the next target. Many mobile voicemail systems pick up after about 25–30 seconds. If you ring longer than that, callers may hit the buyer’s personal voicemail instead of your recorded line or queue.

4. Mark quiet hours by closing nights and weekends. This is the cleanest way to enforce buyer quiet hours. If a buyer wants no calls at lunch, don’t create a hole in the middle of the same window. Instead, create a second target for the same buyer with an afternoon window (for example, 13:00–17:30). Keep the morning window 9:00–12:00. This makes it obvious in reports and lets you split caps cleanly across day parts.

5. Keep caps aligned with your split windows. If a buyer expects 20 calls per day and you split them into morning and afternoon targets, set caps like 10 and 10 (or 12 and 8) to match their staffing. That way, a rush in the morning won’t consume the entire day’s allowance.

6. Test open and closed behavior. Place a test call when a target is open and one when it’s closed. Watch real-time logs to confirm the system rings the target during open hours. Confirm a skip due to a closed window or a reached cap during quiet hours. Also confirm the ring attempt hands off to the next target before personal voicemail picks up.

Once each buyer has a clean window, routing rules do the rest. Priority routing will try them in order. Weighted will spread calls within overlapping open windows. Round-robin will rotate across targets that are open right now. Simultaneous ring will ping multiple open targets at once. That’s useful if you’re forwarding to several agents in one office.

How windows and caps work together

For each target in the routing order, the system checks:

• Is this target’s time window open right now?
• Is this target under its daily cap and within its concurrent cap?
• If yes, ring it briefly (about 15–25 seconds). If not, skip it and try the next.

If every target is closed or capped, send the call to a short queue with hold music (10–30 seconds) and then to voicemail. Make the voicemail greeting useful: “We’re currently offline. Leave your number and best time to reach you. We’ll call back during our open hours.” You can tune that script for your market and language.

If a call lands at 11:30 ET, Buyer A is within 9:00–17:30 ET. Buyer B’s 12:00–20:00 CT window opens in 30 minutes, so only Buyer A rings. If A doesn’t answer in about 20 seconds, the router tries B only if B’s window is open. If not, it goes to the next step without delay.

If Buyer A hits their daily cap at 15:00 ET, the router skips A for the rest of the day and tries B or C if their windows are open. Caps act like a “closed” state until the next day.

If all buyers are closed at 21:30 local time, the call goes to the queue for 20 seconds and then to voicemail. This protects the caller’s time and preserves the lead.

Duplicate-caller rules (rules that decide whether a repeat caller should count as new and where to send them) run alongside this. If your rules say to send repeat callers back to the same buyer for 7 days, the system filters to that buyer first. It then still applies windows and caps. A repeat caller who rings after the previous buyer’s window may skip that buyer and go to the next open target or your overflow path, depending on your settings. If you must keep repeats with the same buyer only when they’re open, set the rule and make the overflow voicemail rather than another buyer. For more routing building blocks, see target routing for pay-per-call.

Time zones, overnight shifts, and midday breaks

Always set each target’s own local time zone. Don’t try to run a single campaign time zone for buyers across the US, India, the Philippines, Thailand, Bangladesh, and Pakistan. You’ll avoid 3 a.m. surprise rings, and you won’t have to do mental math when daylight saving time shifts in some regions but not others.

Overnight windows that cross midnight, like 20:00–06:00, need a split. Create two targets for the same buyer: one 20:00–23:59 and another 00:00–06:00. This keeps reports readable and lets you use different caps if night shift staffing is tighter. If the buyer also has a day shift, use a separate day window target (for example, 09:00–17:00). You can cap day and night independently.

For day-parting and lunch breaks, use the same idea. Create a morning target and an afternoon target for the same buyer. Divide the daily cap between them so the total matches the buyer’s contract or comfort level. If you weight-route during shared hours, set weights per target (for example, 70% to Buyer A and 30% to Buyer B). Keep those targets open only during the intended bands.

DST and regional holidays can change local clocks or staffing. Plan a quick check on changeover weeks. Skim your targets’ schedule pages and confirm the time zone and open hours look right. A short review saves you a stack of missed or unhappy calls.

Test and monitor without losing calls

Use real-time call logs to watch routing decisions while you test. Make one live call per buyer during open hours and one during their quiet hours. Confirm the open-hours call rings the right phone and plays the correct whisper, if you use one. Keep the attempt short. Confirm the quiet-hours call skips that target and tries the next step right away.

Check analytics for answer rate and cap usage by target. If one buyer answers below your target during open hours, shrink their window or weight. Give more volume to a higher-performing buyer in the same time band. Set scheduled email reports that show daily and concurrent cap usage by target. You can adjust before you spill too many calls to queue or voicemail late in the day.

If a buyer changes hours for a day, don’t rewrite all your windows. Close today’s window or set the cap to zero. The router will skip that target cleanly and overflow to the next rule. Reopen the window or restore the cap tomorrow. This keeps your saved schedule intact and prevents accidental long-term edits.

When you’re testing after-hours handling, call right at the edge of a window (for example, 17:29 and 17:31). Confirm the boundary works as you expect. If you use a queue, keep it short (10 to 30 seconds) so callers aren’t punished when all buyers are shut.

Common routing patterns for multi-buyer campaigns

Priority with after-hours overflow. Put Buyer A first with a 9:00–17:00 window and Buyer B second with a 12:00–20:00 window. If your system lets you set ring time, use about 20 seconds on each attempt. After 20:00, when both are closed, route to a queue for 20 seconds, then voicemail. This is clean when you have a “primary” and a “backstop” that works later.

Weighted inside shared hours. If two buyers are staffed 10:00–18:00, set both windows to 10:00–18:00. Split weights 70/30 based on performance or payout. Outside those windows, go straight to voicemail or an answering service. This keeps lead flow stable during the core period.

Weekend reroute. Keep Monday–Friday on your professional buyers. Create a separate weekend target for an answering service with a narrow window (for example, Saturday 10:00–14:00) and a tight concurrent cap to avoid long holds. If weekend volume overruns the service, your queue-and-voicemail overflow still catches callers without ringing weekday buyers on their days off.

Geo + window. First filter by caller state or region, then apply per-target windows. For example, calls from CA go only to in-region agents who are open now, and calls from NY go to East Coast buyers during their hours. This avoids time-zone mismatch and improves answer rate. If no in-region buyer is open, fall back to an out-of-region buyer that agreed to handle spill in your off hours.

Round-robin within a team. Create each agent as a target and give them a shared window (for example, 09:00–21:00 local). Use round-robin so each agent takes a fair share. If your system lets you set ring time, use an 18–20-second ring per agent before moving on so calls don’t hit personal voicemail. Set a small concurrent cap per agent to protect handle time during spikes.

A short aside if you use CallFlow

You set per-target windows under each Target’s Schedule, pick the target’s time zone, set open days and hours, and save. Caps live in the same target, so you can split day parts cleanly. The queue with hold music and voicemail are available as routing steps if all targets are closed or capped.

Make the changes and verify today

• Set aside a short block of time.
• List each buyer’s local hours and quiet hours with time zones.
• In your platform, set each target’s time zone, open days, and hours.
• Keep each attempt short (about 15–25 seconds) before trying the next target.
• If a buyer has lunch or split shifts, create a second target and divide caps.
• Place two test calls per buyer: one during open hours, one during quiet hours. Watch logs and confirm skip/route behavior.
• Adjust caps and, if needed, weights so your totals and performance match plan.

Once you’ve confirmed calls only ring when the right buyer is open, and that your overflow catches the rest, you’re ready for live traffic. If you want to try this on CallFlow’s prepaid, no-subscription setup, you can quickly create targets and set per-buyer schedules. Sign up at /register and route your first calls on your own terms. If you prefer a walkthrough, reach out via /contact.