Identical bodies across a bulk send fingerprint the campaign

The requirementstatement

Message body wording should vary across a bulk send rather than being byte-identical to every recipient.

Severityseverity
LowLOWBest practice. Worth fixing, rarely fatal on its own.
When it bitesphase
After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject
body variance across a bulk send
Where it liveslayer
OperationalOPERATIONAL
How Ekas settles itdetectability
Post-submissionUNDETECTABLE_PRE_SUBMISSION
The subject does not exist yet at submission time: a reply window, an expiring PIN, a queue position. Reported with its deadline.
What the fix involvesfailureClass
Wait on someone elseTERMINAL_EXTERNAL
Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities
PlivoVonage
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Filters fingerprint exact bodies, so a million identical messages are one signature seen a million times and a single spam report can suppress the lot. Varying the wording is not evasion — it is the difference between a campaign that degrades gracefully under a complaint and one that stops entirely.

How to fix itremediation

Personalise at least one element per message — the recipient name, the item, the store — so bodies differ while the offer does not. Done when no two messages in a send are byte-identical.

A compliant exampleexample

Acme Coffee: {{first_name}}, 20% off {{last_bought}} this weekend at {{store}}. Reply STOP to opt out.

Common mistakespitfalls

  • Random character insertion or deliberate misspelling is evasion rather than variance, and it is prohibited outright — vary the content, not the spelling. OPS-072 covers that line.

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Does your template contain any per-recipient field at all?

  1. 1Open the template and look for a merge field — the recipient name, the item, the store.
  2. 2A template with none produces byte-identical bodies however sophisticated the platform is.
  3. 3Vary the content, never the spelling: random characters or deliberate misspellings are evasion and prohibited outright.

What wrong looks like: A million identical messages are one signature seen a million times, so a single spam report suppresses the lot rather than degrading the campaign gracefully.

Notesnotes

A property of a real send. What the user has to check is whether their template has any per-recipient field at all — a template with none produces identical bodies however sophisticated the platform is.

Rules you will hit next

Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.

All operational rules

OPS-146 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.