How do I set up time-of-day routing for insurance leads?

Time-of-day routing for insurance leads is about matching lead delivery to agent availability. Sending a lead to an agent who won't pick up the phone for six hours is the same as losing it — the prospect gets called by a competitor first. The fix is not to send fewer leads; it's to route only to agents who are currently working.

This sounds simple but involves three non-trivial pieces: storing operating hours per agent, evaluating them in the agent's local timezone, and defining what happens when no agent is available at that moment.

Why timezone-awareness is non-negotiable

An insurance agency routing leads across multiple states typically has agents in different timezones. An EST agent's 9 AM start is 6 AM PST. A lead arriving at 8 AM EST is within business hours for EST agents but not for PST agents. Without per-agent timezone storage, the router either treats all agents as one timezone (wrong for anyone outside that zone) or requires agents to manually convert their hours to UTC (fragile, breaks on daylight saving).

The correct implementation stores each agent's timezone as a named zone (e.g., "America/New_York") and converts the lead's UTC arrival time to each agent's local time at routing time. This is a standard datetime library operation, but it needs to be built into the routing engine — it can't be patched onto Zapier filters reliably.

Per-agent schedule configuration

Each agent should have a weekly schedule: which days they work and their start/end time in their local timezone. A typical configuration looks like:

• Monday-Friday: 8:00 AM – 6:00 PM EST
• Saturday: 9:00 AM – 1:00 PM EST
• Sunday: closed

Some agencies also configure lunch windows (12 PM – 1 PM, no delivery) or holiday blocks. The more granular the schedule, the more accurately delivery matches agent availability. Dedicated routers store this as structured data; Zapier stores it as filter logic that someone has to update manually on every holiday.

After-hours fallback options

What happens to a lead that arrives when no agent is within their operating hours? There are three standard options, and the right one depends on your vertical:

• Overflow to an on-call agent: designate one agent with extended or 24/7 hours as the after-hours catch. They receive lower volume but ensure no lead goes uncontacted. Common in high-intent verticals like life insurance or health insurance during open enrollment.
• Queue for morning delivery: hold the lead and deliver it at the start of the next business day for the first available agent. Good for home insurance and auto where urgency is moderate and the prospect expects a next-day call.
• Reject and notify source: return a 503 to the webhook source so the form can tell the prospect "we'll call you during business hours." Least common but useful when lead quality is high and agent contact rate matters more than volume.

Tool comparison for time-of-day routing

Combining time-of-day with caps and LOB filters

Time-of-day routing works best when combined with daily caps and line-of-business filters. An agent might be within their working hours but already at their 20-leads-per-day cap — the router should skip them regardless of time. The evaluation order matters: check LOB and geo first (hard filters), then check operating hours, then check caps. Any failed check should trigger the fallback chain, not a silent drop.

LeadProsper ($499+/mo) and LeadMove ($149/mo) both evaluate these conditions in a single pass. LeadMove applies this combined logic on every plan — you don't need to upgrade to access schedule-based routing. Custom-built systems handle it if the original developer included schedule logic; legacy systems frequently don't.

Testing schedule-based routing

Before going live, test three scenarios: a lead arriving within an agent's hours (should deliver), a lead arriving outside all agents' hours (should trigger fallback), and a lead arriving during one agent's hours but after another agent's cutoff (should go only to the agent still working). If your router supports timestamp override in test mode, use it. Otherwise, temporarily extend an agent's hours to include now and verify delivery, then narrow them back.

Time-of-day routing is one of those features that looks optional until the first buyer complaint about cold leads — at that point it becomes urgent. Building the schedule logic correctly from the start, with per-agent timezones and explicit fallback rules, avoids a class of agent relationship problems that are hard to fix retroactively.