
Event Follow-Up
Part of Lead capture at business events
Qualifying event interest without treating every attendee as a lead
Use what attendees say and request to choose a suitable next step, without turning attendance into a sales lead.
Qualify a conversation by what the person asks for, the problem they describe and the next step they accept. Attendance alone is too broad a signal. Someone may attend to learn, support a colleague, compare ideas or speak, without wanting a sales approach.
Ask before assigning a label
Give staff a few prompts they can use naturally. 'What brought you to this session?' can reveal a topic of interest. 'Is this something you are working on now, or exploring for later?' can distinguish an active project from general learning. 'Would a technical discussion help?' offers a next step without assuming one is wanted.
Record the answer in the person's terms. Do not turn silence into a 'no budget' label or a polite exchange into a firm buying timeframe. If someone is there for education, let the event experience stand on its own.
Match the response to the evidence
| What the person has said or done | Working interpretation | Suitable response |
|---|---|---|
| Attended a talk, with no individual request | Attendance is known; business need is not | No automatic sales task |
| Asked for a named resource | A specific information need is known | Send the promised resource through the agreed route |
| Described a relevant problem but no next step | Potential fit needs clarification | Ask whether they want another conversation |
| Requested a meeting about a defined issue | A follow-up is agreed | Record the issue, owner and agreed contact method |
Adapt these distinctions to the event objective and sales process. Staff should be able to explain why a record enters the sales queue and what the assigned person is expected to do.
Keep fit, timing and permission distinct
A useful note separates three questions. Fit: is the stated issue one your team can address? Timing: did the person give a timeframe, or is it unknown? Contact: what did they ask your team to do?
Someone may have an urgent problem but prefer information first. Another may welcome a conversation about a longer-term project. Neither case is captured reliably by a badge colour or a single score.
Collect only detail needed for the intended response. Identifiable notes about a person's work can be personal information. An organisation covered by the Australian Privacy Principles must assess whether solicited collection is reasonably necessary for its activities. Avoid speculative comments about personal traits or sensitive matters.
A qualification label is not marketing consent. A requested one-to-one response and a future promotional email program have different purposes. Check the basis for the proposed message before sending it. The sales queue should contain records with a stated reason for follow-up and a clear task.
Key Privacy and Compliance Considerations
- Australian Privacy Principle (APP) 3
- Solicited collection must be reasonably necessary for your activities
- Spam Prevention
- Follow ACMA guidelines to avoid sending unsolicited messages
- Personal Information Definition
- Includes identifiable details about work or role



