Skip to main content

​
US campaigns

For organizations on the US market profile, the platform applies federal and state law automatically. These rules cannot be bypassed — not even by you. The permitted time is computed in the local time of the person being called. The resulting window is the intersection of three limits, and the strictest always wins: federal (8:00–21:00 local time), state (many are stricter — an earlier evening cut-off, bans on particular days, their own holidays), and yours — the campaign working hours, which may be narrowed but never widened. Forbidden days and holidays accumulate. Dialing stops ahead of the window closing so that a call already in progress does not run past the cut-off. Contacts outside the window are not lost — they are deferred to the next permitted time. Local time is derived from the file. One of two columns is mandatory:
  • contact_zip — the five-digit postal code. Preferred.
  • contact_state — the two-letter state code.
A contact_city column is optional and used for reporting only.
Leading-zero ZIP codes in Excel. Codes like 00601 or 02134 are often turned into 601 and 2134 by Excel. The platform can recover them, but storing the column as text is safer — the downloaded sample is already set up that way.Why a ZIP beats a state code. A state spanning several time zones is ambiguous without a ZIP, so the platform takes the intersection of every possible zone — that is, a narrower window. In practice that costs about an hour at each end of the day. For single-zone states it makes no difference.Rows with no usable location are rejected at upload and block the launch: there is no way to tell when such a person may be called. Military addresses (APO/FPO) are not dialed. If the file has no location column at all, it is rejected in full.
Accuracy of the location is your responsibility: the platform guarantees compliance relative to the location you supplied and does not verify where the person actually lives. Automatic do-not-call capture. If a person asks not to be called again during the conversation, their number enters the registry automatically. Detection starts from a trigger phrase, but the decision is made by a model that weighs the context of the conversation — to tell a genuine request from someone recounting another conversation. Every entry stores the fragment the decision was based on, and a mistaken entry can be lifted. All doubt is resolved toward caution: if the model is unsure, or temporarily unavailable, the number is suppressed and flagged for review. What is stored per call: the time in your zone and in the contact’s zone, the resolved location, the window applied, and the rules it came from. This data is never recomputed after the fact — if the law changes tomorrow, yesterday’s call still shows the rules in force when it was dialed. The rules in force across all 56 states and territories are available for review, including a grid of forbidden hours.