Question 1

What does it check?

Accepted Answer

Whether each queued outbound call would fire inside the called party's local calling window. The federal telemarketing baseline is 8:00am–9:00pm in the recipient's local time. The tool resolves the called party's local time at the scheduled fire moment and returns CLEAR TO DIAL or HOLD for every row, then rolls the queue up to QUEUE CLEAR or HOLDS QUEUED. It reads calls, not people.

Question 2

Why does the timezone flip matter so much?

Accepted Answer

Because the queue is built in your (the operator's) timezone, but the calling window is the recipient's. A call scheduled for 4:30pm on your West-Coast dialer is 7:30pm for an East-Coast contact — still fine — but a 6:30am West-Coast slot is 9:30am on the East Coast, and an 8:00pm West-Coast slot is 11:00pm on the East Coast, well past the window. Nobody re-checks each row against the recipient's clock by hand. That flip is exactly what the tool computes, using deterministic, DST-correct timezone math.

Question 3

What is the state overlay, and is it a legal list?

Accepted Answer

It's an editable planning reference, not a legal register. Some states narrow the federal window (for example, an earlier evening close). The overlay table lets you encode a stricter open or close per state; the effective window for a row is the intersection — the stricter of federal and your overlay on each end. The rows shipped are illustrative examples marked 'verify,' not a maintained or authoritative list. Replace them with your own counsel-confirmed values.

Question 4

What happens if a contact's timezone is ambiguous?

Accepted Answer

It's held. If a row's state spans multiple time zones (Texas, Florida, and others) and the row has no explicit timezone, the tool can't prove the local time — so it returns HOLD with reason 'timezone unresolved.' Unknown is never treated as dial. Add an explicit IANA timezone to the row (or split the list by zone) and it resolves. This is the honest-verdict move: when the window can't be proven, the safe answer is hold.

Question 5

Does it place or block calls?

Accepted Answer

No. It reads your scheduled queue export and returns a verdict per row. It connects to nothing, dials nothing, and blocks nothing — acting on a HOLD (rescheduling or dropping the call) happens in your dialer. It's a pre-flight check you run before the batch fires, not a gate wired into your dialing system.

Question 6

Is this legal advice?

Accepted Answer

No. It renders a calling-window compliance read you act on, mapped to the federal 8am–9pm baseline as a default. It encodes no current-law guarantee, maintains no authoritative state list, and grades queued calls, not people. The current federal window, its exemptions, and every state and local calling-time rule are legal questions — confirm them with counsel. Not legal advice.

Your dialer says 4:30pm.Your contact hears 7:30pm — or 11pm.

The queue looks fine in your timezone. That’s the trap.

The state overlay catching a call the federal window would clear.

Feed it your queue. Get a per-row verdict.

Three rules the checker holds to.

The window is the recipient's, not yours

Stricter of federal and state — never looser

If you can't prove the window, hold

A pre-flight check. Not a dialer, not a legal register.

Anyone whose queue crosses time zones.

The two halves of outbound-call eligibility.

The parts worth pinning down before you buy.

Catch the after-hours call
before it dials.