Event or Business-Card Leads: Permission and Follow-Up Review
A source-context checklist for deciding how to follow up with event or business-card leads without treating an exchange as automatic consent.
Product & Engineering · September 25, 2026 · 2 min read
A business-card exchange or event conversation is not automatic proof of consent to cold-email follow-up. Review what the person was told, what they could reasonably expect, which channel was discussed, and whether the proposed message is direct marketing. The ICO distinguishes consent, soft opt-in, bought-in data, public details, and objections; the event context must be recorded rather than assumed.1 2
Reconstruct the collection context
Record the event, date, booth or meeting context, form or badge workflow, notice version, fields collected, stated purpose, and any channel preference. If the person asked for a specific resource or follow-up, separate that request from a later product promotion. If the event organizer supplied the data, document the relationship and permitted use instead of treating the organizer’s collection as your own consent.
Before sending, classify the recipient and channel under the applicable local rules. Check identity, transparency, lawful basis or consent evidence, message purpose, and opt-out. A “thanks for stopping by” subject line does not make commercial content transactional. If the facts are unclear, do not use the person’s uncertainty as permission; ask for a clear preference or route the record to review.
Keep the follow-up narrow and reversible
Use the minimum fields needed, avoid unsupported personalization, and make the objection path visible. Suppress promptly when a person says not to follow up. Preserve the collection record and the resulting decision so a later owner can understand why the contact was or was not sent.
Pair this workflow with the privacy notice placement guide, unsubscribe checklist, and data provenance checklist. RepMail can operationalize an approved segment, but it cannot infer consent from an event badge.
Implementation notes
Preserve the collection artifact: the form, badge flow, event notice, conversation note, or organizer terms. A later operator should be able to see whether the person asked for a resource, agreed to a channel, or merely exchanged contact details. If the context cannot be reconstructed, use a narrower non-marketing follow-up only when reviewed, or seek a fresh permission path.
For adjacent controls, use the broader cold-email compliance checklist.
References
Resources in this guide
- Record event, date, booth or context, and data source
- Capture what the person was told and any explicit preference
- Classify recipient and intended channel
- Review notice, lawful basis, consent or soft-opt-in conditions
- Include clear identity and objection path
- Suppress or escalate when expectations are unclear
Frequently asked questions
Does receiving a business card mean the person consented to marketing?
Not automatically. Assess what was said, the context, the expected follow-up, the channel, and applicable law before sending.
Can I send one “thanks for meeting” email?
Only after the applicable review. A personal-sounding message can still be direct marketing if it promotes a product or service.
What should be recorded at an event?
Record the source context, notice or form version, stated purpose, preferences, date, and any objection or limitation.
Continue learning
Review privacy notice placement
Make first contact match the collection context.