Audience acquisition and invitation performance
Stop conditions for event outreach
Invitations keep going out, and nobody has said when they should stop.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Write stop rules before the first send. Decide when a person leaves the sequence, when a whole segment is paused, and when the campaign itself is closed, and name who can make each call.
Stop rules protect your members and your reputation as much as your workload. They also give the committee a clear moment to move effort from inviting to preparing.
Three levels of stopping
Person level: someone registers, declines, asks to stop, or turns out to be ineligible. Segment level: a group is not responding, or the message does not fit them. Campaign level: the purpose has been met, or the date has passed the point where registration is practical.
Keeping the levels separate avoids the common mistake of pausing a whole list because of one complaint, or continuing for everyone because one segment is going well.
Person-level rules that should never be optional
- Registered: remove from every later reminder that asks them to register.
- Declined or no longer interested: remove, and record the reason if given.
- Asked not to be contacted: remove at once and keep that record where the next sender will see it. Ask your data contact how opt-outs must be kept.
- Ineligible or already handled by someone else, such as a confirmed speaker or a partner contact.
Segment and campaign rules to agree with the committee
| Level | Trigger to discuss | Decision | Who decides |
|---|---|---|---|
| Segment | Replies show the message does not suit the group | Pause, rewrite, or drop the segment | Event owner |
| Segment | Complaints or reply-to-stop requests from the group | Pause and review the list source | Event owner and data contact |
| Campaign | Capacity or the registration target set at the start is reached | Close or move to waitlist wording | Committee |
| Campaign | Registration deadline passed with no extension agreed | Stop sending; move to attendee preparation | Event owner |
| Campaign | Date or programme has changed materially | Pause, correct, then resume with the new facts | Committee |
Make the rules usable on send day
- Put the rules in the sequence sheet from the invitation sequence planner, beside each wave.
- Name who checks suppression and who can pause a send.
- Agree a pause route that works the same day, for example one message to the event owner.
- After a campaign stops, record what the stop rule was and what you would change next time.
Worked example · Fictional example
A secretariat closes a campaign deliberately
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Perunding Alam Sekitar plans two reminders after the first invitation. A member replies that he is travelling and asks to stop receiving messages, and the secretariat removes him within the day and logs the request.
Later the committee reviews registrations against the target it wrote in its brief. The target is met two weeks before the deadline, so it stops invitations, switches the page wording to waitlist, and moves the saved time to speaker and delegate preparation.
Use this yourself
Outreach stop-rule list
Copy and complete before the first send. Write your own thresholds; leave blank any trigger that does not apply.
- Person level: registered, declined, asked to stop, ineligible. Who removes them and by when:
- Where opt-outs are recorded and who checks the list on send day:
- Segment level: triggers that pause a segment and who decides:
- Campaign level: registration target or capacity that closes invitations:
- Campaign level: date after which no further invitations go out:
- Change trigger: what facts, if altered, pause all sends:
- Pause route: who can stop a send, and how fast they can be reached:
- After closing: where the final list and reason are recorded:
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person sends and the same person can pause.
- You have one suppression list and one place for opt-outs.
- The committee has agreed a target in writing.
Outside planning help earns its fee when
- Invitations go out from several people or chapters and a stop needs to reach them all.
- Opt-outs and registrations sit in different systems.
- Committee members disagree about when enough is enough.
Want stop rules that are actually followed?
A conference project lead can draft the stop rules with your committee, keep one suppression view across senders, and call the review point when a trigger is reached. Sending authority and final approval stay with your organisation.
Questions organisers ask
How many reminders are too many?
There is no safe general number. Set a limit for your audience in the sequence sheet, vary the message, and check complaints and opt-outs after each wave.
Can we keep inviting people who did not reply?
Often yes, within the limit you set, unless they were told they could stop and chose to. Record any request to stop immediately.
Who has the final say to stop a campaign?
Name one decision-maker at the start, usually the event owner or committee chair, and write it in the sheet.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.