
Event Follow-Up
Part of Post-event follow-up
Measuring whether follow-up helped the next buying step
Define the next buying step, track eligible follow-up records and report outcomes without treating a later sale as proof an email caused it.
Measure post-event follow-up against the next action people agreed to consider: a relevant reply, a meeting held or a requested evaluation started. Define that step and the eligible group before reading results. A sent email records activity; a later deal stage has other possible influences.
Define the step for each route
A resource message may need to complete a promise and offer a route for questions. A reply to a meeting request may need to get that meeting held. A technical answer may help an existing buying group decide what to examine next. These jobs should not share one success label.
| Follow-up route | Next step worth recording | What the record cannot show alone |
|---|---|---|
| Promised resource | Available through the agreed route; relevant question received | Whether the person read or applied it |
| Agreed meeting response | Meeting accepted and held | Whether the event caused the project |
| Technical answer for an existing account | Answer delivered and a documented next action agreed | Whether the answer alone moved a deal |
If a later opportunity is reported, use the organisation's ordinary sales-stage rules. An existing deal does not become new just because its record was updated after the event.
Match each follow-up route to the step worth recording
- Promised resourceNext step: available through the agreed route, plus a relevant question received. The record cannot show whether the person read or applied it.
- Agreed meeting responseNext step: meeting accepted and held. The record cannot show whether the event caused the project.
- Technical answer for an existing accountNext step: answer delivered and a documented next action agreed. The record cannot show whether the answer alone moved the deal.
Keep the sequence visible
A review record can include the event identifier, eligible person or account, request or promise, follow-up owner, response date, delivery status, next action and observation date. Keep the earlier account or opportunity state so a later change has context. Show cancellations, opt-outs, bounced messages and unmatched records rather than silently dropping them.
Choose the unit that fits the question. Count people for individual requests, meetings for meetings held, and opportunities under the organisation's normal opportunity definition for pipeline. Several attendees from one account may share one buying discussion; their replies are not several opportunities.
What the review record should carry
- Event identifier
- Eligible person or account
- Request or promise made
- Follow-up owner
- Response date
- Delivery status
- Next action
- Observation date
- Earlier account or opportunity state, kept for context
- Cancellations, opt-outs, bounced messages and unmatched records shown rather than silently dropped
- Unit counted to suit the questionpeople for individual requests, meetings for meetings held, opportunities under the organisation’s normal definition for pipeline
Report the denominator and gaps
For an agreed-meeting route, show eligible documented requests → owner accepted → invitation sent → meeting accepted → meeting held → next action recorded. Give the count at each stage and the review cut-off. Mark a meeting scheduled for a later date as pending, not held.
For example, meetings held ÷ eligible, documented meeting requests answers a different question from meetings held ÷ all attendees. If the eligible group is unknown, report the observed count and missing data, not a precise-looking rate. Keep different event formats and follow-up routes identifiable when reporting them together.
Agreed-meeting route: the stages to report, counted at each stage to a set cut-off
- Eligible, documented meeting requests
- Owner accepted
- Invitation sent
- Meeting accepted
- Meeting held (a meeting booked for a later date is pending, not held)
- Next action recorded
Interpret contribution carefully
A person may have considered a purchase before the event or spoken with sales afterwards. A reply or stage change after follow-up establishes sequence, not sole cause. Look for a documented connection between the event issue, what follow-up supplied and the next step the person chose. Note other known contact and earlier deal history.
Compare routes only when their eligible groups and purposes are sufficiently similar. A stronger causal question needs a separately designed evaluation with a credible comparison; an ordinary dashboard cannot answer it automatically.
If the review joins identifiable event and sales records, an organiser covered by the Australian Privacy Principles should check whether that use fits the collection purpose or an applicable exception. The report can then identify unfulfilled promises, stalled hand-offs, documented next steps and a specific change for the next event.



