Participant experience and engagement
Following up meaningful connections after an event
Delegates had good conversations on the day, and a week later nobody remembers who to write to.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Meaningful connections continue when delegates have a reason, a way and a prompt. Give them a reason by recording conversation topics during the event, a way through opt-in contact sharing, and a prompt through a short follow-up message sent within a week.
Share contact details only with each person's consent, and ask your data protection contact to confirm the wording and storage before you collect anything.
What counts as a meaningful connection
It is a conversation where both sides want to talk again: a shared problem, an offer of help or a question worth continuing. A swapped card alone is not a connection.
Define it with your objectives, so the follow-up serves what the event is for. Do not count the number of contacts exchanged as a result.
Four ways to support follow-up
| Method | How it works | What to settle first |
|---|---|---|
| Opt-in delegate list | Delegates tick a box to appear in a list shared only with other delegates. | Wording, who sees it, how long it is kept, how to withdraw. Confirm with your data protection contact. |
| Topic cards or board notes | Delegates leave a card with a question or offer that others can pick up. | A moderator, a collection point, what to do with cards after the event. |
| Hosted follow-up thread | A moderated thread opened after the event, one per topic table or theme. | A moderator, a closing date, conduct rules. |
| Personal follow-up prompt | An email that reminds each delegate to write to two people, with a short suggested message. | Sender, send date, no new personal data collected. |
A timetable for the first fortnight
- On the day: ask delegates to note one person they want to speak to again and one topic.
- Next working day: send thanks, the link to opt in to a shared list if you use one, and the prompt.
- Day 5 to 7: send the list or open the thread, with a reminder of conduct and withdrawal.
- Day 14: send a short message asking whether any conversation continued, with one or two questions in the feedback questionnaire.
Keeping it voluntary and safe
Nobody should be listed or contacted because of an attendance record alone. Make every list and thread opt-in, with a clear way to leave.
Set a rule against unsolicited selling to the list, and name who handles complaints.
Reading the result honestly
Reply rates and continued conversations tell you which routes were useful. They do not prove business outcomes. Record what delegates report in the benefit evidence tracker as observed, estimated or not measured.
Use the objective-to-measure planner to decide in advance what you would accept as evidence.
Worked example · Fictional example
A conference secretariat supports follow-up after a regional forum
Fictional organisation and figures, written to show the level of detail that is useful.
A fictional professional-learning network runs a one-day forum for about 150 delegates. Registration included an opt-in tick box for a shared contact list. The wording and storage were confirmed by the network's data protection contact beforehand.
The day after, the secretariat sends thanks and a prompt. On day six it opens a moderated thread for each of five topic tables. On day fourteen it asks two questions about whether a conversation continued, and records the answers as reported, not as proven outcomes.
Use this yourself
Connection follow-up plan
Copy this and fill in each line before the event.
- Objective this follow-up serves:
- What counts as a meaningful connection for this event:
- Method chosen: opt-in list, topic cards, hosted thread, personal prompt:
- Opt-in wording approved by data protection contact (date):
- Who sees the list or thread, how long it is kept, how to withdraw:
- Conduct rule and who moderates:
- Message dates: day of, next working day, day 5 to 7, day 14:
- Questions added to the feedback form:
- Evidence recorded as observed, estimated or not measured:
- Owner of the follow-up and date it closes:
Handle it in-house, or bring in help?
Your team can usually handle this when
- A modest audience and one owner can send two or three short messages.
- No shared list is needed, only a prompt to delegates.
- Your data protection wording is already approved from a previous event.
Outside planning help earns its fee when
- You want a shared list or moderated threads across several hundred delegates.
- Several committees disagree on who owns delegate contact data.
- Sponsors or partners expect access to the list, and the terms need settling first.
Want the follow-up built into the event plan?
An Event Blueprint can place the follow-up in the timeline and responsibilities: the opt-in wording for your data protection contact to review, the moderation roles, the message dates and the questions that go into the feedback form. The rules on who may contact whom stay with your organisation.
Questions organisers ask
Can we share the attendee list with all delegates?
Only with each person's consent, and with wording confirmed by your data protection contact. Opt-in lists are simpler to defend than sharing the full registration list.
How soon should we follow up?
A thank-you and prompt the next working day, and the list or thread within a week, usually works. Conversations fade quickly after the event.
Can sponsors see the delegate list?
Treat that as a question for your data protection contact and your own terms. Delegates should know in advance who will see their details.
How do we measure whether connections mattered?
Ask delegates whether a conversation continued and what came of it, and record answers as reported. Do not infer value from the number of contacts shared.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.