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. If the campaign working hours are empty, calls go out during the whole legal window of the contact’s jurisdiction. Forbidden days and holidays accumulate. Dialing stops 30 seconds before the window closes, so that the connection does not land after the cut-off; this buffer is not configurable. A conversation already under way may continue. Contacts outside the window are not lost — they are deferred to the next permitted time. If no permitted time remains before the campaign ends, the contact is excluded with the reason “No allowed window before campaign end”. If the intersection of the limits is empty, the contact is excluded with the reason “No legal calling window (empty intersection)”. Local time is derived from the file. One of two columns is mandatory:
  • contact_zip — the postal code: five digits or ZIP+4 (12345-6789). A 3–4-digit code is padded with leading zeros. Preferred.
  • contact_state — the two-letter state code.
A contact_city column is optional and used for reporting only. A contact_timezone column does not affect the window: the zone is taken from the ZIP or the state. If the zone in the file differs from the resolved one, the row is flagged in the upload report.
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.Contacts without a location in a campaign. If a campaign has contacts without a location, it cannot be launched, and a running campaign pauses itself. Upload the file again with a contact_zip or contact_state column.
If the state does not match the ZIP, the ZIP is used. The row is accepted, and the upload report shows a note. Possible notes: “State contradicts ZIP (ZIP wins)”, “Invalid state code”, “Unreadable or unknown ZIP”, “Location resolved by state only”, “State spans multiple time zones”, “City doesn’t match resolved location”, “File time zone differs from resolved”. 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. Frequency caps. On top of your organization’s limits, the state’s legal caps apply — by the contact’s location. State caps do not apply to campaigns classified as “Servicing” (your organization’s limits still apply). “Debt collection” campaigns follow Reg F: at most 7 attempts per debt within 7 days, and a 7-day pause after a conversation. A dial over the limit is deferred. See Call frequency for details. Automatic do-not-call capture. If a person asks not to be called again during the conversation, their number enters the registry automatically. Capture is triggered by a trigger phrase or by the agent’s classification of the call. If the organization has a classifier model configured, the model decides on the phrase by weighing the context of the conversation — to tell a genuine request from someone recounting another conversation. Without a model, the number is added on the phrase. Every entry stores the fragment the decision was based on, and a mistaken entry can be removed with Remove. If the model is unsure, the number is added to the registry and lands in the “Review queue”. If the model is unavailable, the number is added on the phrase, without the review queue. Automatic capture works only on the us_tcpa market profile. 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 “Calling rules (US)” page shows the rules in force across 56 jurisdictions — 50 states, the District of Columbia and five territories: hours, restricted days, holidays, legal frequency caps and version history. The “Forbidden-windows grid” is built by week or by calendar, in the “With ZIP” and “Without ZIP (zone intersection)” variants, and is exported with “Export XLSX” and “Export CSV”. The rules cannot be changed from your organization’s cabinet.