Set Contact Frequency from Recipient Context
Coordinate messages across teams with a recipient-level frequency and stop worksheet, separating requested exchanges from unsupported repeated outreach.
10/23/20263 min read
A recipient can receive three reasonable-looking messages from three colleagues in the same week and experience the combined result as excessive. Each sender may believe they stayed within their own sequence limit. A frequency policy that counts only campaigns or salespeople misses the burden on the person receiving them.
Set limits from recipient context and coordinate them across the organization. The artifact is a frequency-and-stop worksheet that distinguishes requested exchanges from unsolicited attempts, includes pending messages, and makes stopping a normal outcome. No universal number of touches guarantees a reply or makes unwanted contact acceptable.
Establish eligibility before cadence
A frequency limit answers how much contact may occur within an already justified scope. It does not create that scope. Check the applicable rules, source permissions, channel, purpose, and current preferences before considering timing.
ICO preference guidance explains that applicable objections must be honored. A cadence cap cannot override that boundary. For other jurisdictions and channels, have the responsible owner apply current requirements and platform rules separately.
Do not treat silence as an instruction to escalate from email to phone or personal messaging. A new channel introduces another permission and expectation question. The fact that a sequence has remaining steps does not answer it.
Build a recipient-centered worksheet
Record the specific relationship context and the total planned burden across relevant senders and channels.
Situation: requested deliverable, agreed future discussion, active service exchange, or unrequested approach.
Recipient instruction: exact timing, channel, purpose, and restrictions where provided.
Useful reason for the next message: the question answered or commitment fulfilled.
Recent contact: relevant messages and calls from all involved teams, not only the current owner.
Pending contact: scheduled campaigns, manual tasks, and partner activity within authorized visibility.
Limit and review point: a conservative internal rule appropriate to the context, with no claim that it is a legal safe harbor.
Stop conditions: objection, decline, lost relevance, conflicting ownership, unreliable evidence, or the agreed endpoint.
Keep necessary service communications distinguishable so a promotional limit does not accidentally block a critical agreed update. That distinction needs genuine purpose review, not a convenient label.
Work through a fictional collision
Synthetic contact F16 asked a consultant to send one comparison on Friday. Meanwhile, marketing has a newsletter scheduled for Thursday and another salesperson has a Monday check-in task. The worksheet reveals the combined contact rather than presenting each action in isolation.
The account owner fulfills the specifically requested comparison through the approved route. The unrelated check-in is closed because it adds no distinct value. The newsletter is assessed against its separate eligibility and the organization's recipient-level cap. The example does not establish a universal spacing rule; it shows why coordination can change the decision.
A second synthetic contact, F17, has not responded to an initial unrequested approach. The reviewer finds no new relevant information and closes the attempt under the internal stop policy. The team does not invent a deadline or switch channels to manufacture another reason to contact.
Make limits enforceable at the last decision point
Count queued actions as well as sent ones. Two teams can independently approve messages before either is logged as sent. A shared owner or coordinated pre-send check helps detect that collision. Use a supported control and test its behavior rather than assuming a dashboard count prevents races.
Record exceptions narrowly. A recipient asking for several answers in a live exchange is different from an operator overriding the cap to meet a sales target. An exception should have a reason and owner, and it must not override a stop instruction or missing authority.
Review qualitative feedback alongside volumes. Complaints about repetition, confused references, or multiple representatives may reveal a coordination defect even when counts look low. Avoid collecting unnecessary behavioral tracking merely to optimize persistence.
The completed worksheet should produce a clear action: send the justified message, delay within an agreed context, combine necessary information, or stop. A good frequency policy protects the recipient's attention and the team's promises rather than maximizing how many reminders a person can be made to receive.
If you are also choosing research access, ask about Leads Automation’s independent Sales Navigator offer at US$15/month on WhatsApp. Confirm the available plan, eligibility and terms before ordering; this is not LinkedIn’s official price or an assurance that any particular integration is included.