SMS and Email Cadence Template
Three documents and four sheets that price a text against an email using your own opt-out rates, then set one cap across both channels.
Free download · No account needed
Cadence Map · one ordinary week, both channels, per person
Two caps summing to 8 a week, and a cohort receiving 13
Bramble & Rye · 62,000 on email, 14,800 with SMS consent, 13,100 on both
| Cohort | People | Emails | Texts | Messages | Attrition units |
|---|---|---|---|---|---|
| VIP, bought, abandoned, browsed, due | 118 | 10 | 3 | 13 | 23.11 |
| VIP, abandoned, browsed | 604 | 7 | 3 | 10 | 20.11 |
| VIP, browsed | 1,834 | 4 | 2 | 6 | 12.74 |
| Same activity, email only | 214 | 10 | 0 | 10 | 10.00 |
| Not engaged, email only | 32,346 | 2 | 0 | 2 | 2.00 |
Counted as messages the top cohort is 1.30x the email-only cohort doing the same things. Counted in attrition units it is 2.31x.
Where 4.37 comes from
Email unsubscribes run 0.19% per send here and SMS opt-outs 0.83%, both from the same quarter. So one text costs 4.37 emails of list attrition, and that quotient is the only assumption on this page. SMS is 11.1% of the week's messages and 35.3% of the week's attrition.
Why neither cap is wrong
The email cap is 5 a week and the SMS cap is 3. Both are configured on campaigns, both programmes' flows are excluded from them, and neither platform can read the other. Nobody chose 13 for anybody; 13 is what two reasonable caps produce when they are set in two places.
The distribution, both ways
Median 2 messages and 2.00 units. p90 is 5 and 8.37. p99 is 10 and 20.11. The two orderings disagree, and the one every dashboard reports is the one that understates the load.
Transactional messages are excluded. An offer inside an order confirmation is not transactional and belongs in this table.
Bramble & Rye caps email at five messages a week and SMS at three. The two caps sum to eight, both are configured on campaigns with every flow excluded, and neither platform can read the other one. In an ordinary week the heaviest cohort receives thirteen messages: 118 people who happen to be loyal, browsing and due to reorder, so they qualify for almost everything. Nobody chose thirteen for anybody. Thirteen is what two reasonable caps produce when they are set in two places that cannot see each other.
Counting messages is the mistake, and it is the one every cross-channel cadence guide makes. Email unsubscribes here run 0.19% per send and SMS opt-outs 0.83%, so one text costs 4.37 emails of list attrition. Price the week that way and the top cohort carries 23.11 attrition units against the 10.00 borne by the email-only cohort doing exactly the same things. Counted as messages it looked 1.30 times heavier. Counted in attrition it is 2.31 times heavier.
So the cap is one budget across both channels, denominated in units and enforced on the person rather than the channel. Sweep it from two units a week to twenty-four and the cost per saved contact barely moves, $38.00 at three units and $36.08 at sixteen, because the cut always lands on the marginal message. The level is a bet on subscriber tenure instead. Pair this with the customer segmentation model template and the lifecycle email programme pack, or take the files blank from the template library.
What's in the pack
Cadence Map
One ordinary week per cohort across both channels, with the message count and the attrition-unit count side by side so the gap between them is visible.
Channel Value
Revenue and attrition per send for each channel, and the one column that decides an allocation: net revenue per unit of list attrition.
Frequency Cap
The budget swept from two units a week to twenty-four, with cost per saved contact, what that contact returns, and the tenure each level needs to break even.
Consent Register
One row per consent event per channel, with the disclosure and signature records that a consent claim actually rests on, and an audit column. Where the choice is offered rather than revoked, the email preference centre template builds that page from real unsubscribe reasons.
Channel Strategy
What each channel is for, who is really on the SMS list, and the three things SMS carries. The test is whether the message expires.
The Attrition Unit Method
How to derive your own exchange rate, why the cap is a bet on tenure rather than a preference, and why the allocation rule matters more than the level.
Consent and Compliance Note
Consent is per channel and per seller, revocation is not the STOP keyword, and an imported list is not a consented list. With the reasoning, not just the rules.
One budget across both channels
A space rule that stops River reasoning about frequency one channel at a time, which is the habit that produced two caps in the first place.
How to use it
- 1
Open in River, or take it blank
Hand River the exports and let it derive your exchange rate and build the map, or download the three documents and four sheets and do the division yourself.
- 2
Send four figures and the flow definitions
Email sends, email unsubscribes, SMS sends and SMS opt-outs from one quarter, plus every sending programme in both platforms. Flow definitions, not last week's send report.
- 3
Read your exchange rate first
One division, and it reframes everything after it. Then the Cadence Map, where the comparison worth seeing is the dual-channel cohort against its email-only twin.
- 4
Sweep the budget, then set it
The sweep gives a break-even tenure for every level. Put your retention curve beside that column and the row picks itself, which is not the same as picking a round number.
Frequently asked questions
Is this template free?
Yes. Download the Word documents and CSV sheets with no account, no card and no email gate. Edit with AI is the optional half: River derives your exchange rate, builds the cohort map and runs the sweep. Every pack sits in the template library.
How often should I text customers?
The question has no answer on its own, because a text is not a unit of anything. Ask instead how much a person receives from you across every channel, priced by what each message costs in list attrition. Here that made one text worth 4.37 emails.
Why not just cap email at five and SMS at three?
Because that is two caps, and their sum is a number nobody chose. Bramble & Rye's two caps sum to eight and its heaviest cohort receives thirteen, since both caps are configured on campaigns and both programmes' flows are excluded from them.
Is an email opt-in enough to send someone a text?
No. SMS marketing needs prior express written consent, defined in 47 CFR 64.1200(f)(9) as an agreement in writing bearing the signature of the person called that clearly authorises the seller. Consent is per channel and per seller, so it does not carry over.
Do I have to honour anything other than STOP?
Yes. A called party may revoke by any reasonable method, a sender may not designate an exclusive means, and requests must be honoured within a reasonable time not to exceed ten business days. A reply reading "no more texts please" is a revocation.
Does adding SMS increase revenue or just move it?
It depends entirely on whether the person is at budget. For the 91.4% of this base under ten units a week SMS is additive. For the rest it is a substitution, and since a text is 0.77x an email per unit of attrition, it is the message that should be cut.
Why does one emoji make a text cost three times as much?
Because carriers bill per segment. Twilio documents that GSM-7 fits 160 characters in one segment and 153 in a concatenated one, while a single UCS-2 character drops those to 70 and 67. A 140-character text goes from one segment to three.
Find out what a text actually costs you
Take the Word documents and CSV sheets blank, or open this exact pack in River and send it one quarter of send-and-attrition figures.
Edit with AI