A recurring live-session programme for educators, scoped to exactly what the campaign record supports

A recurring programme is a different marketing object from a series of events, and it is usually run as the second while being described as the first. Each session gets an invitation campaign, the campaign goes out, the session happens, and the next session starts again from a list that has learned nothing from the last one. This programme sat in that shape: real content, a real audience of educators, campaigns that went out and replies that came back positive. What it did not have was a record built to be read afterwards. Reply sentiment was observed by the people clearing the inbox rather than counted against a denominator, and there was no written definition of what counted as a positive reply, which means the impression is real and the number is not yet available.

The replies were positive. Nobody had written down what positive meant, so there is an impression where a number should be.

1. 01

   A positive reply is a metric only after somebody defines it

   An out-of-office, a not-me-try-this-person, a send-me-the-recording and a we-would-like-to-talk are all replies and only some are signals. Without a written classification agreed before the campaign, the reply rate is a count of email volume and the positive rate is a memory.

2. 02

   The denominator is the number that goes missing first

   A reply rate quoted without its send count is not a rate. In a recurring programme where list size changes between sessions, the same number of replies can be a doubling or a halving, and only the denominator tells you which.

3. 03

   Recurring programmes either accumulate an asset or they do not, and it shows in the second campaign

   The people who registered and did not attend, and the people who replied and did not register, are the highest-value list any session produces. If they are not tagged at the time, the next session's campaign gets built at full cost from the same cold source as the first one.

4. 04

   Scoping an entry to the record is a decision, not a limitation

   This engagement covered campaign management. Session design, content and delivery sat with the publisher, and writing about them here would mean inventing detail. The entry is narrow on purpose, and its metrics carry instructions for what to pull rather than figures nobody has checked.

The work was campaign management for a recurring live-session programme: audience segmentation, invitation copy, sending schedule and reply handling, session after session. The corrections that matter are structural rather than creative. Reply classification is written down before the send, with four categories and a named owner, so a positive reply becomes a defined object rather than an impression formed while clearing an inbox. Send counts are recorded per campaign so every rate has its denominator attached to it. Registrants who do not attend and repliers who do not register are tagged at the time and carried into the next session's list rather than rebuilt from cold. Session content, structure and delivery remained with the publisher throughout, and this entry does not describe them.

1. 1

   Per cycle, week 1

   Segmentation

   Educator segments defined for the topic of that session

   Owner: OmniFlow

2. 2

   Per cycle, weeks 1–2

   Invitation campaign

   Copy written per segment, send count recorded at dispatch

   Owner: OmniFlow

3. 3

   Per cycle, ongoing

   Reply handling

   Replies classified into the four written categories as they arrive

   Owner: OmniFlow

4. 4

   Per cycle

   Session

   Live delivery; content and structure owned by the publisher

   Owner: Publisher

5. 5

   Per cycle, after the session

   Carry-forward

   Non-attendees and repliers tagged into the next cycle's list

   Owner: OmniFlow

Nothing in this entry should be published as a figure until it has been pulled from the sending tool and the webinar platform directly. Report the reply rate with its denominator in the same sentence, and report a positive-reply rate only after the written classification has been applied retrospectively to the stored reply text, so the number and the definition ship together. Where the platform did not record attendance for a session, report registrations only and say so rather than estimating the gap. The narrow scope of this entry is itself part of the reporting instruction: publish the campaign mechanics now, and add each figure only once it carries a source and a denominator.

Measured in the sending tool and the webinar platform, window to be confirmed at publication. Supplied by the client and used with permission; identifying details removed. Cited: ON24 *2025 / 2026 Webinar Benchmarks*. ---.

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.

5 of the figures on this engagement are not published yet. Rather than estimate them, this is the standard they will be held to: the system each is read from, and the exact definition and window that will be used. Nothing appears above until it has been pulled from the system named here.

We ran several cycles before writing down what a positive reply was, which means the earliest campaigns produced a genuine signal that cannot now be reported as a rate without re-reading the inbox. The classification should have been a one-page definition agreed in the first week, before the first send. It costs an hour at the start and it is the difference between a programme with a record and a programme with an impression.

Real client work. Every figure is measured in a named system and carries the window it was measured over. See all our work