chest, suitcase, send mail, travel, lap, box, closure, chest, chest, suitcase, suitcase, suitcase, suitcase, suitcase, box, box, box, box, box
Photo by Alexas_Fotos on Pixabay

Event Follow-Up

Part of Post-event follow-up

Sending promised resources before a sales request

Track event resource promises, deliver checked materials clearly and decide separately whether a sales request is appropriate.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Event Operations Desk.

If an event promised slides, a worksheet or an answer, deliver the item through an appropriate route without making access depend on a sales meeting. A separately agreed business discussion can proceed on its own timetable. Keep the resource promise and any new commercial request as separate decisions.

Build a promise list

Review the event page, invitations, closing remarks and staff notes. For each resource, record what was promised, to whom, which version is approved, who may share it and who will send it.

Speaker's draft slides may differ from the version cleared for attendees. A recording may contain participant contributions or material that cannot be distributed. Check the actual file before saying it is ready.

Distinguish a resource promised to the event group from a document requested by one person. The group resource can go to appropriate recipients. An individual request needs its own task and owner. A general slide link does not complete a specific unanswered question.

Make delivery useful on its own

Name the event and item near the start of the message. Explain what the material contains, any important limit and what to do if access fails. Use a route the intended recipients can access.

If a recording cannot be released, explain that and offer a suitable recap where possible; do not call a recap the promised full recording.

For a session that promised a worksheet, a fulfilment message could say: 'Here is the worksheet mentioned during the session. It uses the example from the exercise. If you cannot open it, reply and we will help.' The message completes the stated task without requiring a meeting request.

If delivery is delayed, tell affected recipients what changed and what the next realistic step is. Do not invent a release date to complete the email.

Check the basis for a commercial message

A meeting request may fit when the person asked for one or agreed to continue a business discussion. Record that agreement and give the relevant owner the context. For other recipients, a route for questions may be enough.

Before adding a product offer or meeting invitation to a resource email, assess the whole message: promotional content can make an otherwise factual email commercial.

Verify fulfilment

Check the final file and recipient group before sending. Record the version delivered, access route, known failures and individual promises still open. Sending an email does not establish that its attachment or link worked for the recipient. Close the task when the item is available through the stated route and known access problems have an owner.

More in Event Follow-Up