Delegate acquisition: finding the gaps between invitation and attendance

Check who the programme is useful for

Start with a specific discussion on the agenda. For an illustrative manufacturing roundtable about replacing production equipment, a plant manager may have a different reason to attend from a finance director. Write that reason beside the role in the audience brief. Ask the organiser to confirm whether suppliers qualify and whether a complimentary place needs approval.

Review a small selection of researched records together before extending the list. Examine the company, current role and evidence of relevance. Resolve disagreements about eligibility at this point. Otherwise, the invitation team and the registration team can end up applying different rules to the same person.

Separate sending problems from audience problems

Record rejected messages separately from messages accepted by the receiving service. Acceptance does not establish that a person saw the invitation. Google's sender guidance also says that it cannot verify third-party open-rate measurements and that low open rates alone do not reliably identify delivery problems.

Ask the sending provider for the actual rejection reason before changing the copy or increasing volume. For messages that reached interested people, read the replies. Questions about eligibility, travel or the programme tell the team what information to clarify. A percentage in a dashboard will not explain which question is holding up a decision.

Give replies somewhere to go

Agree who answers questions and who can approve exceptions. If someone asks whether a colleague may take their place, the reply handler needs the organiser's substitution rule. Keep the answer with the campaign record so that another team member can pick it up without sending the person back to the beginning.

A follow-up should reflect the latest response. Remove registered people from invitations asking them to register. Stop marketing follow-ups after an objection, and route attendance or booking questions to the appropriate owner. Decide the follow-up schedule with the organiser before sending, including when the team will stop.

Test registration and agree attendance evidence

Use an approved test record to follow the invitation link on a phone. Check that the pass conditions match and that the confirmation arrives with usable event details. If approval is required, make the waiting status clear. Someone who has submitted a form should be able to tell whether they actually have a place.

Before the event, agree which check-in record will establish attendance and how replacements will be matched. Cvent's OnArrival documentation, for example, reports event check-ins separately from registrations and supports session attendance records. These are different measures; a conference arrival does not prove attendance at every session.

The closing report should identify the reporting period, count unique people at each agreed stage and explain unresolved matches. Keep the organiser's verified attendance file as evidence. Where fees depend on attendance, apply the written qualifying rules and settle disputed records before invoicing. This gives the next campaign a useful record of what needs changing.