
Event Follow-Up
Part of Post-event follow-up
Routing high-interest conversations to the right owner
Assign event follow-up from the attendee's stated issue, check existing account ownership and confirm each promised action has an owner.
Route an event conversation by the issue the person raised and the next step they accepted. Give an owner enough context to continue that discussion, then confirm the task was accepted. A 'high-interest' label without a request, responsible person or appropriate contact route is not a workable handoff.
Identify the action behind the signal
Start with what was observed. A request for technical detail, a question about an existing service and an explicit meeting request call for different responses. A thoughtful public question may simply reflect learning.
If the note is unclear, ask the staff member who spoke with the person what was requested before creating a sales task.
| Recorded conversation | Possible owner | First action to confirm |
|---|---|---|
| Asked for a named document or answer | Person responsible for that material | Send or arrange the requested item. |
| Raised an issue with an existing service | Current account or service owner | Check the account history and respond through the agreed route. |
| Asked to discuss a possible project | Relevant sales or specialist owner | Continue the stated issue and arrange the agreed next step. |
| Discussed a topic but requested no contact | No automatic individual owner | Keep the note out of a sales queue unless an appropriate basis and purpose are established. |
This is a routing guide, not a lead score. If several teams could help, assign one accountable owner and identify any specialist who should support them.
Check the existing relationship
Before creating a new task, look for an existing account, open request or opportunity. A current customer may already have a named contact. Attach a discussion about an existing deal to its history rather than reporting it as a new opportunity.
If identity or account matching is uncertain, leave it for review instead of merging records on a guess.
A short handoff can carry the event and conversation date, stated issue, material promised, agreed action and timing, contact route, recorder and proposed owner. Keep the person's statement distinct from staff interpretation. 'Asked how two teams would review a request' records a question; 'ready to purchase' needs separate evidence.
Confirm ownership and resolve exceptions
The proposed owner should accept the task, reassign it with a reason or ask for missing context. Record that response. A task placed in a queue but never accepted has no confirmed working owner.
Give unclear requests, unavailable owners and commitments the team cannot yet meet a named person to resolve them. Update the attendee about a material delay where appropriate.
Track resource delivery separately. A specialist may need to answer a technical question before a commercial discussion is useful. The promised answer still needs delivery if that discussion does not proceed.
Keep the record and contact appropriate
Identifiable event notes should contain only what the response needs. Limit access to people handling the request and correct obvious errors before handoff.
For organisers covered by the Australian Privacy Principles, solicited collection must meet the applicable necessity requirements; secondary use or disclosure may require an exception, and information held must be protected through reasonable steps. Direct marketing has its own applicable rules.
An agreed response to a request does not itself enrol the person in future promotional emails. Assess the proposed message and its contact basis separately. The handoff succeeds when someone can honour the agreed next step.
Key compliance considerations under APPs and ACMA guidelines
- Solicited collection necessityMust meet APP 3 requirements
- Secondary use/disclosureRequires exception under APP 6
- Direct marketing rulesSubject to APP 7 and ACMA spam regulations
- Data security obligationsReasonable steps required under APP 11
- Spam preventionFollow ACMA’s guidelines to avoid sending unsolicited messages



