RedHub AI
How the roll-up gate works
How the Calling-Window Compliance Checker works
This tool grades every queued outbound call against the called party's local calling window, then rolls the queue up to whether any call would fire outside it. It reads 6 queued calls and rolls them into one verdict — the worst, never the average — then a gate that can only make it worse.
The 6 queued calls
A queued call whose timezone can't be resolved is held, never dialed — unknown is never treated as clear. And the effective window is the stricter intersection of the federal 8am-9pm baseline and any editable state overlay, never the looser of the two. Every call rolls up worst-first: one held call puts the whole queue at HOLDS QUEUED, and the queue only clears when every call resolves inside its own window.
Why: Two calls resolve inside their window and clear. Four are held for four different reasons: Q-1002 fires before the federal 08:00 open, Q-1003 after the federal 21:00 close, Q-1004 is caught only by the stricter FL state overlay that closes the window at 20:00, and Q-1006's timezone can't be resolved so it's held rather than dialed. One held call puts the whole queue at HOLDS QUEUED.
No single call is the crisis — the clustering is. The roll-up takes the worst, the gate escalates when trouble compounds, and it names the one thing to fix first. Not legal advice. This tool renders a calling-window read you act on, mapped to the federal 8am-9pm baseline as a default and an editable state overlay you maintain — not an authoritative list of state calling-time laws, and it guarantees no current-law status. It grades queued calls, not people; confirm the current federal window, its exemptions, and every state and local calling-time rule with counsel.