Scheduling Filters

Q: What timezone do scheduling filters use?

The account-level timezone set in Settings → Account. All schedule times are interpreted in this timezone. Daylight-saving transitions are handled automatically — a schedule of '8am-6pm' stays at local 8am-6pm regardless of DST.

Schedule Lead Distro AI inbound and buyer filters by day of week and hour range. Route leads to different buyers based on staffing hours, enforce overnight rules, or pause filters during maintenance.

Last updated: May 22, 2026

What Are Scheduling Filters?

Every inbound filter and every buyer filter can be active on a schedule — set the days of the week and hour ranges when the filter applies. Outside those hours, the filter is bypassed and leads flow as if it didn't exist. This unlocks time-aware routing without duplicating campaigns or buyers.

Common Use Cases

Pattern	Implementation
Route to daytime buyers M-F 8am-6pm, overnight buyer otherwise	Add buyer filter on Buyer A: active M-F 08:00-18:00. Add buyer filter on Buyer B (overnight): active all other hours.
Pause a buyer during their off-hours	Add buyer filter that always rejects: active during the buyer's off-hours only. Leads route to other buyers during that window.
Stricter TCPA rules outside daytime	Add inbound filter requiring `tcpa_express_consent == true`: active outside 9am-9pm.
Maintenance window	Add inbound filter rejecting all leads: active during the maintenance hours. Suppliers see a clear rejection reason.
Geo-specific timing	Texas buyer active M-F 8am-6pm Central; Florida buyer active M-F 8am-6pm Eastern — different schedules in the same campaign timezone.

Configuring a Schedule

Open the filter (inbound or buyer-level).
Click the Schedule tab on the filter.
Select days of the week (any combination — M, T, W, Th, F, Sa, Su).
Set hour range(s) using 24-hour format. Multiple ranges per day are supported (e.g., 09:00-12:00 and 13:00-17:00 to skip lunch).
Save. The schedule takes effect immediately and uses your account timezone.

Timezone Handling

Schedules use the account-level timezone set in Settings → Account. Leads ingested at 9am Pacific are evaluated against schedules in Pacific if the account is set to PT. Daylight-saving transitions are handled automatically — a schedule of 8am-6pm stays 8am-6pm local across DST changes.

If you serve buyers in multiple US timezones from a single account, the schedule applies in your account's timezone — not the buyer's local time. For a Texas buyer who wants 8am-6pm Central from a Pacific-timezone account, set the schedule to 6am-4pm (Pacific equivalent of Central). For complex cross-timezone setups, contact support for a per-buyer timezone override.

Frequently Asked Questions

Can I have multiple schedules on a single filter?

Yes. A single filter supports multiple time ranges per day (e.g., 09:00-12:00 and 13:00-17:00 to model a lunch break) and multiple days. The filter is active during any of the configured ranges. For non-overlapping schedules across multiple filters on the same buyer, configure them as separate buyer filters.

Do scheduled filters work with ping-post?

Yes. The ping endpoint evaluates schedules just like the post endpoint — a ping arriving outside the scheduled hours sees the filter as inactive, just like a full post would. This keeps supplier-side and buyer-side behavior consistent across the two-step ping-post flow.

What timezone do scheduling filters use?

The account-level timezone set in Settings → Account. All schedule times are interpreted in this timezone. Daylight-saving transitions are handled automatically — a schedule of '8am-6pm' stays at local 8am-6pm regardless of DST.

Can different buyers have different schedules in the same campaign?

Yes — each buyer's filter is independent. Buyer A can be active 8am-6pm M-F while Buyer B is active 6pm-8am M-F (overnight overflow). Combined with state filters, you can build sophisticated routing like 'daytime TX buyer + nighttime overflow buyer covering all states.'

What happens to leads that arrive during a scheduled maintenance filter?

If the filter rejects all leads (e.g., a maintenance-window filter at the campaign level), incoming leads get `REJECTED` with the maintenance filter as the reason. Suppliers see a clear rejection — they can pause their traffic and retry after the window. Use the Notifications tab to send yourself a Slack alert each time the maintenance filter activates so you know suppliers are being rejected.

Can I schedule a filter to run only on weekends?

Yes — select only Saturday and Sunday in the days picker. Common use case: 'TCPA-strict mode' that requires `tcpa_express_consent == true` only on weekends (when state-specific calling restrictions are tighter). The filter is inactive M-F (all leads pass that rule) and active Sat-Sun (consent required to pass).

Does the schedule affect filter behavior or just whether the filter runs?

Whether the filter runs. Outside the scheduled hours, the filter is treated as if it doesn't exist — leads pass through it unconditionally. Inside the scheduled hours, the filter's rules apply normally. This is different from time-conditional rules (e.g., 'reject if hour > 18') which are technically possible to build in inbound filter logic but harder to maintain.

Campaign Basics

Create and configure lead distribution campaigns in Lead Distro AI. Choose your routing method, set daily caps, map custom fields, and assign buyers with priority rules for every pipeline.

Inbound Filters

Use inbound filters to reject leads at the campaign level before distribution. State allowlists, custom field rules, AND/OR groups, scheduling, and FAQs for Lead Distro AI.

Daily Caps

Set per-buyer daily, weekly, monthly, and total lead caps plus dollar budget caps in Lead Distro AI. Cap reset behavior, overflow routing, and FAQs.

If you have any questions, send us an email at support@leaddistro.ai

Duplicating Campaigns Buyer Basics