Skip to main content

Call frequency

Calling windows say when a number may be dialed. Frequency limits say how often. They apply to each phone number across all campaigns of the organization, so two campaigns calling the same person share one budget.

Where the numbers come from

Your organization sets five company limits: calls per number over a rolling 7 days, calls per number per day, a pause after a marketing conversation, a pause after a servicing conversation, and the days without an answer before the number is slowed down. The sixth frequency limit — the weekly voicemail ceiling — is set in the Voicemail message policy block. It is a frequency limit too: it counts every campaign and holds the dial once reached. A campaign can carry its own Setting for this campaign on top of that.

What the limits mean

  • A conversation is a human answer lasting at least 15 seconds. An answering machine is never a conversation.
  • The pause after a marketing conversation applies to Marketing campaigns and runs from a marketing or inbound conversation with the number.
  • The pause after a servicing conversation applies to Servicing campaigns and runs from a servicing conversation of the same agent or an inbound conversation.
  • Debt collection campaigns get neither pause. On the US market profile the Reg F wait applies instead — 7 days after a conversation about the debt.
  • Slowing down: after the set number of days without an answer, the number is dialed at most once per 7 days.
A campaign setting can only tighten, never loosen. Lower the limits or increase the waiting time and it is accepted; anything looser than the organization setting is refused by the server when you save. The campaign wizard and the campaign card say so in the field itself, so the rule is visible before you try.The one exception is the on/off switch below, which is not a value but a separate control, and which only a platform administrator may turn off.
Each limit in the wizard and the campaign card shows:
  • Applied limit — the value actually in force, or Not applicable to this campaign type;
  • Set by — Organization, Platform default (the organization has not set its own values) or Campaign;
  • when the campaign has its own setting — the Organization setting and Campaign setting rows;
  • Recommended.
The warning about exceeding the recommendation follows the applied limit of the campaign, not the raw value you typed. Legal caps are not shown in this block: the exact restriction applied is visible in the contact’s stored frequency decision. The Frequency settings block on the Dialing step: applied limit, source, recommendation, and the not-applicable note

Switching the limits off

Frequency limits can be switched off — for the whole company, or for a single campaign. This exists for trials: the platform switches them off while it is being tested, and you switch them on when you are confident. Two settings. Organization sets the default for the company. Campaign inherits it and can override it. Switching them on is yours; switching them off is the platform administrator’s.
Which way the switch starts is decided by the organization’s market.
  • US profile — a new organization is created with the limits on: there frequency is part of compliance, with state law and Reg F on top of it.
  • Kazakh profile — with the limits off: the market norm is the calling window and the do-not-call registry, not frequency caps.
For a Kazakh organization the limits are a company’s voluntary self-restriction, not a legal requirement. You can switch them on yourself at any time: the values you entered are stored and apply as soon as the switch is on. Only the platform administrator can switch them off again.Moving an organization to a different market profile resets the switch to the new market’s default: to the US profile switches it on, back switches it off. The activity log records that as its own entry, so an automatic change is distinguishable from a manual one.

The company setting

Open Organization → the Settings tab → Edit settings → the Calling rules section (see Organization). The Frequency limits switch sits above the five company limits. The weekly voicemail ceiling is below, in the Voicemail message policy block; with the limits off it is marked Not applied. Under the switch are the Company limits: Recommended or Custom. Custom values come with a Starter template: Conservative, Standard (the same as the recommended values) or Custom — the template values are in the table above. A changed value shows Recommended: N next to it, and values above the recommendation trigger a warning. On the US profile the line Debt collection cooldown: 7 days (Reg F, law) sits under the limits — it is law, not a setting. The Frequency limits switch turned on, with recommended values Switch it off and the block says plainly what changed. The limit values and the weekly ceiling stay saved but are not applied while the switch is off. The same block with the switch off and its notice Press Save changes. The change takes effect on the very next dial; nothing needs restarting.

The campaign setting

Open the campaign → Frequency settings. The control at the top has three states: Inheritance is resolved at dial time, not copied when the campaign is created: flip the company switch and every inheriting campaign follows. Campaign frequency settings inheriting an organization with limits off Inheriting a company that has the limits off: a banner names the source, and every limit tile is marked Not applied. The campaign card has six such tiles, the weekly ceiling included; the wizard has five, and the ceiling tile sits in the Voicemail message policy block. Switch the control to Apply limits for this campaign and both the banner and the marks go. The same control switched to Apply limits for this campaign Frequency settings are editable in a draft campaign. Before launching, the review screen carries the same statement: the company frequency limits are off, and the source — organization or campaign. On the US profile it adds that Reg F rules and state caps still apply; on the Kazakh profile that sentence is absent — promising a legal layer where there is none would be untrue. With the limits on, the review screen shows the informational note A frequency policy is active: at most N attempts per 7 days and M per day per number.

What the switch does not touch

  • State caps and Reg F stay on — on the US market profile. They are law, not a client setting — see Legal caps below. Reg F applies only to Debt collection campaigns, and state caps do not apply to Servicing campaigns. The Kazakh profile has no legal layer at all: Reg F applies only on the market that declared it.
  • Calling hours stay on. A contact waiting because of the time of day keeps waiting. If a test campaign still does not dial, check the hours before the limits.
  • The do-not-call registry stays on.
  • The voicemail message policy stays on — see below.
Calls made with the limits off still count later. They are written to the number’s call history as usual, and when the limits come back on those calls count towards them. The switch gives you freedom to dial during testing, not a clean history afterwards. If a clean history matters, ask the platform administrator to create a separate test organization.

Who can do what

Every switch is written to the activity log — who, when, and the value before and after. Each call also records which mode it was placed in, so the call history stays honest about the calls made with the limits off.

Watching it during the run

The campaign progress has a Frequency block that separates two outcomes: contacts held by frequency restriction — waiting, to be dialed once the restriction passes — and contacts closed by frequency restriction, which will not be dialed by this campaign at all. The contact listing carries the reason next to each contact, a Retry no earlier than time for a waiting contact, and the Stored frequency decision behind them:
  • Governing restriction and Source — which limit fired and who set it (organization, campaign, state or federal law);
  • Frequency limits — whether they were on or off at the moment of the decision;
  • Restriction end in the saved decision;
  • the Stored counters, Applied restrictions and Legal restrictions groups.
The decision is stored, not recomputed — a contact shows the rule that applied when it was evaluated.

Voicemail message policy

The Voicemail message policy decides when the agent leaves a message on an answering machine. The organization sets the policy, and every campaign inherits it unless it sets its own. If the organization has not configured a policy, a message is left on every answering machine. The message text itself lives on the agent; an agent that leaves no voicemail overrides all of this.

Modes

In By rules mode the conditions are combined: all of them must pass.
  • The attempt number is — the attempts on which a message is allowed, for example 1, 3. Whole numbers from 1 to 99, up to 20 of them. Numbered of each day or overall.
  • At least … since the last … — a pause after an event for this number: a call attempt (any outcome), a voicemail left, an unanswered call, or a human answer. Durations from 1 minute to 7 days; you can add several of these rules.
  • No more than … voicemail per … — a cap per day or per 7 days, from 1 to 10. The cap counts only messages left. With frequency limits on it cannot be higher than the weekly voicemail ceiling: to allow more, raise the ceiling.
Under the editor the platform restates the policy in a sentence, for example “A voicemail is left only when it is attempt 1 of each day, counting across all campaigns at Acme”. Check that sentence before saving. A voicemail left means a message played to the end. A machine reached without a message, a message cut off midway, or one that never played is not a voicemail left: it does not restart the since the last voicemail left pause and does not use up the voicemail caps. When a rule forbids a message, the call still goes out and ends without speaking: the machine is detected, the call is closed, and the attempt counts as a call for the frequency limits, but not against the voicemail caps. In the call history such a call has its own end reason, Voicemail, no message left, so “the agent does not leave messages” and “the policy forbade it this time” can be told apart.

Which calls are counted

Count attempts to a phone number across has two values:
  • All campaigns across your organization — a number already called twice today by another campaign arrives here on attempt three;
  • This campaign only — attempt numbers count only this campaign’s calls. The since the last … pauses and the voicemail caps still see calls made by other campaigns.
This setting governs attempt numbers only. The since the last … pauses and the voicemail caps count every call to the number in your organization, whichever campaign made it. The frequency limits and the legal caps always count every campaign too, because the subscriber’s phone rang whichever campaign dialed it. HubTalk recommends at most one voicemail per contact per day across the whole organization. Restore recommended sets exactly that. If your policy can leave more, the panel shows an amber warning: frequent messages increase the risk of complaints and opt-outs. You can still save it; the change is written to the activity log with a mark that it is weaker than recommended.

The organization policy

Open Organization → the Settings tab → Edit settings → the Calling rules section. The Voicemail message policy panel is directly under the company limits. It has its own Save voicemail policy, Discard changes and Restore recommended, so a half-written rule does not reach the campaigns. The Weekly voicemail ceiling is in the same panel and is saved with it; with frequency limits off it is marked Not applied. Only an administrator of the organization can change the policy. A change takes effect on the next dial of every inheriting campaign; campaigns with their own override are not touched.

The campaign policy

On the Dialing step of the campaign wizard:
  • the Attempt counting group holds the choice of which calls are counted;
  • the Voicemail message policy card, the last on the step, shows the weekly ceiling, the rules under When a message is left, and who set them.
Override for this campaign opens the editor with the organization’s rules as the starting point; Change it for every campaign leads to the organization page instead. Unlike the frequency limits, a campaign override may go either way: stricter or looser than the organization. The weekly ceiling is the exception — a campaign can only lower it. Reset to organization policy returns the inheritance, including the choice of which calls are counted. The campaign policy is editable in a draft campaign. If the campaign’s agent leaves no voicemail, the card says so and the rules are locked.
Two honest limits.The policy works where the answering machine was detected. If the platform did not recognize one, the call counts as a conversation with a human, and the voicemail rules do not apply at all.And a call without a message is not always entirely silent: if the agent greets before the verdict arrives, the start of the greeting lands in the mailbox.

Answering-machine detection

How the platform recognizes an answering machine, which checks to turn on and why it sometimes gets it wrong is described in Answering machine detection. The voicemail policy applies only after a machine has been recognized. The voicemail message policy is independent of the frequency limits switch — they are two separate controls. Limits can be off while the policy works, and the other way round. The weekly voicemail ceiling is a frequency limit, so it follows the switch. For organizations on the US market profile, jurisdictions add their own caps on top of your policy, and the strictest wins. A sub-jurisdiction identified by ZIP prefix is resolved before the statewide rule; which edition of a rule applies is decided by its effective date in the contact’s time zone. Servicing campaigns are exempt from state restrictions — organization restrictions apply to them. Reg F applies only to Debt collection campaigns: at most 7 attempts per debt in 7 days, and a 7-day wait after a conversation about the debt. Each cap records the citation of the norm it comes from, and that citation travels with the decision into the audit trail. The exemption in the contact details. When a contact is dialed by a campaign classified as Servicing, its stored frequency decision has an Exempt from state restrictions block. It explains why the state caps were not applied, row by row:
  • Classification — the campaign classification that gave the exemption: Servicing;
  • Basis — what the exemption rests on: Product decision;
  • Decided by and Decided on — who took the decision and when; the date is shown in UTC;
  • Citation — No statutory citation found: no law exempting servicing calls from state caps has been cited.
Below the block, the reminder “Other applicable restrictions remain in force”: your organization’s limits apply to the contact.
Check the citations before you lean on them. The shipped reference includes entries marked “no statutory citation found”. They are real caps with an unverified source, and it is better to discover that here than in an audit.