---
title: "Direct mail for RevOps teams"
description: "What RevOps owns when direct mail enters the stack, from CRM sync and send permissions to spend limits, frequency caps, suppression, and measurement."
canonical: https://trysincerely.com/for/revops-teams
last_updated: 2026-10-11
---
> 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.
# Direct mail for RevOps teams

> What RevOps owns when direct mail enters the stack, from CRM sync and send permissions to spend limits, frequency caps, suppression, and measurement.

Source: https://trysincerely.com/for/revops-teams

When direct mail joins the revenue stack, RevOps owns the rules around it. Sales and marketing decide what to say. You decide which CRM records feed it, who may send and who approves, how much it can spend, how often one person can get mail from any team, and how anyone will know whether it created pipeline. Settle those before the first campaign. A sequence step can be paused in a minute. A letter the printer already accepted cannot be pulled back.

![A settings card with six rows: Salesforce sync every 15 min, approved designs only, spend stops before print, a frequency cap of 3 in 30 days, suppression for every team, and one print on retry.](https://trysincerely.com/images/for/revops-teams.webp)

*Direct mail for RevOps teams comes down to rules set before the first campaign, because a sequence step can be paused and a printed letter cannot.*

This page walks through the questions a RevOps lead should ask before approving a mail tool, with what Sincerely does for each one. Sales leaders deciding where mail fits in the motion should read [direct mail for sales leaders](https://trysincerely.com/for/sales-leaders) instead.

## What to ask before you approve a mail tool

| Question                                                | What a good answer looks like                                       |
| ------------------------------------------------------- | ------------------------------------------------------------------- |
| What does it read from the CRM, and what does it write? | A fixed field list, a sync schedule, and writeback you can turn off |
| Can a rep send without an approver?                     | Yes, but only designs someone already approved                      |
| Where does spend stop?                                  | Before the piece prints, not on next month's invoice                |
| How often can one person get mail?                      | One cap per person, across every team and campaign                  |
| What happens when someone opts out?                     | Mail the printer has not accepted cancels everywhere at once        |
| Can a retry print a second letter?                      | No, and the vendor sees the same key on every retry                 |
| How will we know it worked?                             | A randomized holdout by account, with the outcome fixed at launch   |

The [enterprise platform guide](https://trysincerely.com/guides/enterprise-direct-mail-platform) turns most of these into six tests you can run in a pilot. The rest of this page covers what RevOps has to configure.

## CRM sync and field mapping

Start by asking what the tool reads and what it writes, field by field. Sincerely connects to Salesforce and HubSpot over OAuth, and the two connections behave differently.

Salesforce syncs about every 15 minutes. You choose the scope before the first import: every contact, chosen list views, contact owners, or filters on title, state or country, and whether a mailing address exists. It reads Contacts, not Leads, so convert leads first or bring them in by CSV. Writeback is off until an admin turns it on. When it is on, each confirmed delivery creates one Task on the contact, in every campaign or only the ones you pick. The Task belongs to the contact owner, the connected user, or one user you name. Sincerely writes only Tasks. It never edits contacts, accounts, or opportunities.

HubSpot syncs once a day, reads the whole portal, and writes nothing back. If the audience has to be decided inside HubSpot, export it and import a CSV.

Email is the field that matters most. Sincerely matches records on it for suppression and the frequency cap. A person who sits in the CRM twice under two different emails counts as two people for both checks, so merge those records before you connect. The full field tables are on the [Salesforce](https://trysincerely.com/integrations/salesforce) and [HubSpot](https://trysincerely.com/integrations/hubspot) integration pages.

## Who may send and who approves

Sincerely has four roles. A member can send one piece, close follow-ups, and record outcomes. An approver can also approve designs, held copy, and launches. Admins and the owner have the same permissions, which add campaign building and workspace settings.

A member can send only a design that already has approved status. Sending a draft counts as approving it, so a member who tries is refused.

Three switches on each member adjust that without changing the role. You can turn off one person's one-off sends and keep their history, let one senior rep build campaigns without making them an admin, or set a monthly gift budget for that person.

Some sends wait for a second person. Any gift worth more than $2.50 a piece raises an approval request. The cheapest catalog gift is $49, so every gift waits for an approver, one-off or campaign. A campaign also waits when its gifts total more than $1,000, or when it would push the person launching it past their monthly gift budget. No workspace setting changes these thresholds, and they apply to admins and owners too.

A campaign that mails on its own, from a CRM event, an API call, a signal, or a schedule, needs an approver to activate it. It also needs a credit envelope, the most credits it may spend. The person who launched a campaign over $1,000 or over their budget cannot approve that request. The gift and activation requests have no such rule, so name a second approver anyway. The guide on [letting reps send without losing control](https://trysincerely.com/guides/let-reps-send-mail-without-losing-control) has a role setup for a ten-person team.

## Budget limits

Postcards, letters, and handwritten pieces draw from prepaid credits and stay under the plan's piece cap. Gifts are different. Their catalog price comes out of a prepaid gift balance, and three dollar limits can sit on top of it: one per campaign, one for the workspace each month, and one per member.

Sincerely reserves credits and gift funds for each piece before it prints, and it checks one rep's gift budget one send at a time. Two sends from the same rep at the same moment cannot both spend the last $50 of her budget. If any check fails, the piece does not print. Nothing goes out on credit to be reconciled later. The [budget controls guide](https://trysincerely.com/guides/direct-mail-budget-controls) walks through each check in order.

## Frequency caps and suppression across teams

The default cap is three pieces per person in any 30 days, and an owner or admin can set it from 1 to 10. It counts every contact record that shares the email address, across every campaign and every one-off send. Marketing's event postcard and a rep's personal note draw on the same allowance. Field marketing teams that run event mail from the same workspace live under this cap too; [direct mail for field marketing teams](https://trysincerely.com/for/field-marketing-teams) covers their side.

When two scheduled touches are due for a person with one slot left, the higher-precedence campaign takes it. The other moves to the next eligible day, and the move is logged. A piece already queued keeps its slot. A rep's one-off send outranks scheduled mail, but it never slips. If it would break the cap, the rep sees the reason and the date it becomes possible. The [two-teams guide](https://trysincerely.com/guides/stop-two-teams-mailing-the-same-account) shows the precedence order.

Suppression overrides all of it. Suppressing a contact exits every active enrollment and cancels each queued piece the print vendor has not accepted. An opt-out or other decision about the person follows their email to their other records. You can also suppress whole domains, such as a competitor's, and see how many contacts the list will catch before you save it. [Stopping mail across teams](https://trysincerely.com/guides/stop-mailing-someone-across-teams) covers the details.

## Duplicate prevention

The database refuses a second piece for the same enrollment and step. Each piece also sends Lob or PostGrid an idempotency key, a fixed ID the vendor checks, so a retry after a timeout does not buy a second print. A step does not advance until the vendor acknowledges the piece.

That covers retries. It does not merge two CRM records for the same person under different emails. Those count as two people. The [duplicate guide](https://trysincerely.com/guides/prevent-duplicate-direct-mail) explains the rest.

## Address quality

A piece prints only when postal data confirms its address and the contact is marked mailable. An address with a specific problem, such as a missing suite number or a vacant building, goes to a person for review. A workspace can also choose to review every verified address.

Addresses Sincerely finds by research also go to review, and they never overwrite one you already verified. Run the mailability audit on Contacts before you plan volume. A synced list of 2,000 contacts might hold 1,300 that can take mail today, and that number belongs in the campaign plan.

A deliverable address is not always the right one. A verified headquarters can still be the wrong place for someone who works from home. The [B2B address guide](https://trysincerely.com/guides/b2b-mailing-addresses) covers that gap.

## Attribution versus holdout measurement

Sincerely reads deal stages from the CRM as outcomes, lets reps record meetings by hand, and keeps the source on each one. On their own those are matchback. The meeting happened after the mail. That does not show the mail caused it.

To show cause, a campaign needs a holdout. Sincerely assigns whole accounts to mail or holdout from a hash of the account, the campaign, and a salt locked at launch, so the split is stable and you can audit it. The primary outcome and window lock at launch too. Holdouts are optional per campaign. A team that wants to mail everyone on a list can choose no holdout, and that campaign reports response rates with no lift claim. When too few accounts have finished their window to support a lift number, the readout says so and shows none.

Set this expectation with leadership before the first campaign. A list of 150 named accounts will not produce a firm lift estimate in one quarter. The [pipeline proof guide](https://trysincerely.com/guides/how-to-prove-outbound-created-pipeline) shows how to size the test and pool comparable cohorts.

## The data that comes back

Only standard US postcards and letters printed through Lob report delivery events. Canadian mail, handwritten pieces, and gifts do not report them automatically, so reps need a different follow-up rule for those. A confirmed delivery creates a follow-up task for the next day, and a Salesforce Task too if writeback is on. When the rep closes that Task in Salesforce, the follow-up in Sincerely closes with it.

Admins can download the audit log as CSV from Settings, and the measurement breakdown downloads as CSV from the page that shows it. Delivery confirms a piece reached a delivery point. It does not mean anyone read it. See [direct mail tracking](https://trysincerely.com/guides/direct-mail-tracking).

## What Sincerely does not do

Sincerely mails to the United States and Canada only. There is no SAML single sign-on, and there is no SOC 2 report to hand your security team. If your review requires either, stop here and pick another platform.

Two CRM gaps matter for planning. HubSpot gets nothing written back, so follow-up tasks for HubSpot teams live in Sincerely. Salesforce Leads never sync, so an org that works mostly from Leads has to convert them or import a CSV before mail can reach those people.

## Related questions

- [What makes a direct mail platform enterprise-ready?](https://trysincerely.com/guides/enterprise-direct-mail-platform): Enterprise direct mail fails on duplicates, runaway spend, and missing proof, not features. Six tests to run in a pilot, and which platforms fit which program.
- [How to let reps send mail without losing control](https://trysincerely.com/guides/let-reps-send-mail-without-losing-control): Let reps send approved mail on their own while approvers control new designs, campaign copy, gift budgets, and higher-risk launches.
- [How to stop two teams mailing the same account](https://trysincerely.com/guides/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.
- [How to prove outbound actually created pipeline](https://trysincerely.com/guides/how-to-prove-outbound-created-pipeline): Use an account-level randomized holdout, a fixed pipeline outcome, and intention-to-treat analysis to separate outbound attribution from causal lift.
- [Salesforce direct mail and handwritten notes integration](https://trysincerely.com/integrations/salesforce): Send printed mail or handwritten notes when a Salesforce deal closes lost, goes quiet, or nears renewal, with follow-up Tasks written back to Salesforce.
- [HubSpot direct mail and handwritten notes integration](https://trysincerely.com/integrations/hubspot): Start printed or handwritten mail from HubSpot deals and renewal dates. Trigger recipes, the field mapping, setup steps, and what the read-only sync leaves out.

---

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