---
title: "How to stop two teams mailing the same account"
description: "Share one cap per person and a clear priority order, so the more important piece keeps the slot and the other moves to a later day."
canonical: https://trysincerely.com/guides/stop-two-teams-mailing-the-same-account
last_updated: 2026-10-04
---
> If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call.
> Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at
> https://trysincerely.com/auth.md. Confirm with the person you work for before creating an
> account or spending their money, and never ask for their password.
# How to stop two teams mailing the same account

> Share one cap per person and a clear priority order, so the more important piece keeps the slot and the other moves to a later day.

Source: https://trysincerely.com/guides/stop-two-teams-mailing-the-same-account

To stop two teams mailing the same account, route their sends through one system, apply one direct mail frequency cap per person, and write down which kind of touch wins when two are due together. The higher-priority touch takes the available slot. A lower-priority scheduled touch moves to a later day rather than disappearing.

That rule solves the collision only when both teams are mailing the same person. If sales writes to Maya and customer success writes to Priya at the same company, a person-level cap sees two different recipients. The account still needs one owner and one plan for total mailbox pressure.

## How the collision happens

Imagine Northstar Software has an open renewal with Acme. Three sends converge on Maya Chen, Acme's operations lead:

- An SDR wants to send Maya a one-off note after a call.
- Marketing has Maya in a list blast scheduled for Wednesday.
- Customer success has a renewal note due on Thursday.

Each send makes sense alone. Together, they tell Maya that nobody at Northstar knows what anyone else is doing. A campaign calendar will not catch this if each team owns a different campaign. Separate caps will not catch it either.

The fix is one rolling count across the shared workspace, checked when a piece is prepared, plus a stable priority order for scheduled mail. The count answers whether Maya has room. Priority answers which piece gets that room.

## Use the right rule for the problem

A cap, precedence, and suppression can all stop a piece from going out today, but they mean different things.

| Rule          | Question                                                                    | What happens                                      |
| ------------- | --------------------------------------------------------------------------- | ------------------------------------------------- |
| Frequency cap | Has this person reached the allowed number of pieces in the rolling window? | A scheduled touch waits for the next free day.    |
| Precedence    | Which scheduled touch gets the remaining slot?                              | The higher rung goes first; the lower rung waits. |
| Suppression   | Must this person receive no more mail?                                      | Sending stops rather than moving to another date. |

Use [suppression](https://trysincerely.com/guides/direct-mail-suppression) for a do-not-mail request, not for a crowded week. Use a cap when the person may still receive useful mail later. The [frequency cap guide](https://trysincerely.com/guides/direct-mail-frequency-caps) covers how to choose the rolling window and ceiling. This guide deals with the harder operating question: what wins when teams collide.

## How Sincerely orders competing mail

Sincerely starts each workspace at three pieces per contact in a rolling 30-day window. An owner or admin can set the ceiling from one to ten. Every Sincerely piece for that contact uses the same count, whichever campaign created it.

Scheduled touches are evaluated from rung 5 down to rung 1:

| Rung | Reason for the touch   | Examples                                                                      |
| ---- | ---------------------- | ----------------------------------------------------------------------------- |
| 5    | A person clicked Send  | One-off note or postcard                                                      |
| 4    | A relationship moment  | Meeting follow-up, revival, deal acceleration, renewal, or keep-in-touch mail |
| 3    | A CRM or API event     | Outbound air cover or closed-lost win-back                                    |
| 2    | A list blast           | One campaign to a chosen list                                                 |
| 1    | Drip and sourced leads | First Send, Enterprise Drip, or Find & Mail New Leads                         |

If two live campaigns share a rung, the older campaign runs first. That tie rule matters because a priority label without a stable tie rule still leaves the result to timing.

Suppose Maya already has two counted pieces when the renewal note and list blast become due. The renewal note is rung 4, so it takes the third slot before the rung 2 list blast. The list touch moves to the next eligible non-blackout day. Its campaign log records the new date, the frequency-cap reason, the playbook, and its precedence rung. Sent mail's Upcoming view shows the priority, reason, and next eligible date, so the account owner can see the delay without reading application logs.

A one-off send behaves differently because a person clicked Send expecting an immediate result. If Maya is already at the cap, Sincerely refuses the send and names the next eligible date. It does not quietly reschedule the note. If a one-off has already taken the last slot, a lower scheduled touch can slip instead.

The final check is inside the database transaction. It locks the frequency decision to the workspace and contact before counting the last 30 days. Two concurrent sends cannot both claim Maya's last slot. A queued piece holds a slot; after submission, the first vendor-submission time anchors the count.

## Work a real collision before launch

Write a small decision table with the people who own sales, marketing, and customer mail. Use an actual account rather than labels such as "high priority."

For Acme, the team might decide:

1. A renewal note tied to the current contract gets the slot before broad prospecting.
2. A list blast may move, but the account owner must see the new date.
3. A rep's one-off is refused when the cap is full, so the rep chooses another channel or waits.
4. A reply or do-not-mail request triggers the appropriate exit or suppression rule instead of another priority debate.

Then inspect the next 30 days for Maya and the other people at Acme. A rule that protects Maya does not protect her colleagues from four separate teams mailing them on adjacent days. The [contacts-per-account guide](https://trysincerely.com/guides/how-many-contacts-per-account) explains how to choose recipients with distinct roles rather than sending the same idea to a whole buying committee.

## Know what the cap cannot see

Sincerely's rolling count reads Sincerely piece records. It does not count email, calls, ad impressions, or a sequence running in another tool. A CRM event can start a mail campaign, but the event itself is not a piece and does not consume a slot.

The count is keyed to a contact ID, not an email address or account ID. If Maya exists once from Salesforce and again from a CSV, those records have separate counts. Merge duplicates before launch rather than assuming the cap will recognize the same person across records.

There is no workspace-wide account cap spanning campaigns. A campaign can carry its own limit of one to 25 contacts per account, and Enterprise Drip defaults to three, but that limit governs entry to that campaign. It does not total the mail that other campaigns send to the same company. Use one account plan and review total pressure across every recipient.

The same boundary applies to systems and workspaces. A cap in one system cannot reserve a slot in another. If separate teams cannot share the dispatch system, appoint one source of truth and require every planned physical touch to be recorded there before it is approved.

## Where HubSpot and Sendoso are better

[HubSpot sequences](https://knowledge.hubspot.com/sequences/unenroll-from-sequence) can unenroll all contacts at a company when one contact replies or books a meeting, if that option is enabled. That is better for coordinating email follow-up across a company. Sincerely does not read email or call activity into its physical-mail cap, so the account owner must connect those channel decisions.

[Sendoso Recipient Limits](https://www.sendoso.com/whats-new) go further for gift-only controls. On its Enterprise Policy Center, an admin can cap gifts to one person over a rolling 30-day window by number of sends, total dollar value, or both, across the team. Sincerely's frequency cap is based on piece count, so Sendoso is the stronger choice when the main risk is cumulative gift value rather than total physical-mail volume.

## Related questions

- [What is a direct mail frequency cap?](https://trysincerely.com/guides/direct-mail-frequency-caps): A direct mail frequency cap limits how many physical pieces one person receives in a rolling period. Set it across campaigns, triggers, and one-off sends.
- [How many people should you mail at one B2B account?](https://trysincerely.com/guides/how-many-contacts-per-account): Mail one person for a timely personal signal and two or three distinct buying-committee roles for a strategic account, with one coordinated account plan.
- [Account-based direct mail: mail by account, not contact](https://trysincerely.com/guides/account-based-direct-mail): Coordinate direct mail across a buying committee and measure it with whole-account holdouts. A guide to account-based mail.
- [How to manage direct mail suppression across campaigns](https://trysincerely.com/guides/direct-mail-suppression): Keep one durable do-not-mail decision per contact, check it at dispatch time, and cancel every queued piece that has not reached the print vendor.

---

Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout.

Contact Sincerely: https://trysincerely.com/contact

Agent routing index: https://trysincerely.com/llms.txt