The copy and pacing standard that lets someone else send outbound in your name

A standard is only needed when more than one person sends, or when one person sends on more than one account. At that point the rules that lived in an operator's head have to become checkable, because the failure modes are silent: copy drifts toward template language one message at a time, and pacing drifts upward whenever somebody is behind. Neither produces an alert until the account is restricted or the replies stop.

Two banned openers, ten banned words, a 60-word ceiling on first-degree messages and a 400-character ceiling on InMail. The standard is short because it has to be followed by someone in a hurry.

1. 01

   A banned-word list beats a style guide

   A style guide asks the writer to have taste and to have it consistently at five in the afternoon. A banned-word list is checkable in ten seconds by someone who is not the writer. The list covers 'platform', 'dashboard', 'pipeline', 'solution', 'leverage', 'streamline', 'seamless', 'robust', 'unlock' and 'empower', plus the two openers that identify a template on sight — 'Hope you're well' and 'I wanted to reach out'.

2. 02

   A subject line that makes an offer is a subject line the recipient has already read

   The rule is that an InMail subject is an observation about the recipient and never an offer. It is the single rule in the standard that cannot be automated or checked by a script, which is exactly why it is written down rather than assumed.

3. 03

   Word ceilings do the editing that reviewers will not

   Under 60 words for a first-degree message, under 400 characters for an InMail. The published platform guidance on short InMails is four years old and directional at best, so the ceiling here is set by what a person will read on a phone between meetings, not by a benchmark.

4. 04

   The pacing rules protect the asset, not the metric

   Twenty messages a session, 45 to 90 seconds varied between sends, three sessions at least an hour apart or spread across two days. The stop condition — any captcha, any limit notice — is unconditional on purpose, because an operator who is behind on volume will always be able to construct a reason to keep going.

Across 13.2M requests, the connection-note reply rate **fell 37% in twelve months** to ~2.2%, while follow-up replies hold at **10.4%** (Expandi 2026). The persuasion has to move out of the note and into the follow-up — which is precisely what the copy standard enforces.

The standard is one document with four sections and no appendix. Section one is the routing rule: which brand, which conversation, which two markets. Section two is copy: the word ceiling per track, the banned words, the banned openers, and the observation-only subject-line rule. Section three is pacing: session cap, interval range, session spacing, and the unconditional stop condition. Section four is the send log, which records sender, track, count, start and end time per session, so that a pacing breach is visible the next morning rather than three weeks later when the account is restricted. Copy and pacing live in the same document because they fail together.

1. 1

   Week 1

   Draft the standard

   Four sections, one page, no appendix; routing rule agreed with brand owners

   Owner: OmniFlow

2. 2

   Week 1

   Template set

   One template per track per brand, each inside the word ceiling

   Owner: OmniFlow

3. 3

   Week 2

   Send log

   Per-session log: sender, track, count, start and end time

   Owner: OmniFlow

4. 4

   Ongoing

   Weekly read

   Send log reviewed against the pacing rules; breaches discussed, not counted

   Owner: OmniFlow

This entry makes no performance claim. It documents an operating standard and the two failure modes it was written against: copy that drifts toward template language, and pacing that drifts upward under pressure.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

The first version put the copy rules and the pacing rules in two separate documents on the reasonable-sounding grounds that different people cared about each. Operators read one and not the other, which is how the first pacing breach happened on an account whose copy was excellent. They are one document now, and the send log sits inside it rather than in a separate workbook.

Real client work that shipped. No performance figures are published, because none have been verified and approved for release. See all our work