Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@eventcrew

Attendee follow up

@eventcrew/attendee-follow-up

Turn badge scans and booth notes into a follow-up plan within 48 hours: sort contacts into hot, warm, and nurture, draft a personal email for each hot lead and a template for the rest, and export a CSV ready for your CRM or email tool. Drafts only; never sends.

SkillOtherv1.0.0 (latest)
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: attendee-follow-up
  3. 3description: Plan and draft event follow-ups from a badge scan or attendee export plus booth notes. Sorts contacts into hot, warm, and nurture tiers, writes a personal email for each hot lead, short templates for warm and nurture, and exports a CSV for a CRM or email tool. Never sends anything. Use after a conference, trade show, webinar, or meetup when the user says "follow up with the leads", "we have the badge scans", "draft post-event emails", or "who should sales call first?"
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# Attendee follow-up
  8. 8
  9. 9Leads go cold fast: reply rates drop sharply after the first two days. This kit turns a scan export and scribbled booth notes into a ranked follow-up plan and drafts, so the first emails go out while people still remember the conversation.
  10. 10
  11. 11## When to use
  12. 12
  13. 13- The day after an event, ideally within 48 hours.
  14. 14- "Follow up with everyone we met", "draft emails for the booth leads", "who are the hot ones?"
  15. 15- Webinar attendees and no-shows too: treat attended as warm and registered-but-missed as nurture.
  16. 16
  17. 17## Inputs
  18. 18
  19. 191. **Contacts:** `data/attendees.csv`, exported from the lead retrieval app, registration list, or webinar tool. Useful columns: name, email, company, title, notes, rating or qualifier answers, scanned by, attended (yes/no).
  20. 202. **Booth notes:** `data/booth-notes.md`, anything the team wrote down ("Dana, ops lead at a 40-clinic group, wants a pilot in Q1"). Match notes to contacts by name and company; list any you cannot match.
  21. 213. **The offer** for each tier: hot (book a call, pilot), warm (a resource, a demo video), nurture (recording, newsletter).
  22. 224. **Sender** name and role for each tier, and the event name and date.
  23. 235. **Voice:** if `brand.md` exists, follow its voice section.
  24. 24
  25. 25## Steps
  26. 26
  27. 271. **Clean the list.** Remove exact duplicate emails (keep the row with the most notes) and obvious staff or vendor scans (your own domain, exhibitors). Report the counts.
  28. 282. **Tier every contact**, with the reason in one short phrase:
  29. 29 - **Hot:** a note with a concrete need, timeline, or ask for next steps, or a top rating in the scan app. Sales calls these.
  30. 30 - **Warm:** a real conversation or matching title and company, no stated need yet.
  31. 31 - **Nurture:** scanned for swag, no notes, or outside your audience.
  32. 32 When unsure between two tiers, choose the lower one and say why.
  33. 333. **Draft hot emails one by one.** Each: subject under 7 words, first line references the actual conversation from the notes, one sentence of value, one clear ask with two time options or a booking link placeholder `<booking link>`. Under 120 words. No attachments.
  34. 344. **Draft one template each for warm and nurture** with merge fields (`{{first_name}}`, `{{company}}`). Warm: a useful resource plus a soft ask. Nurture: thanks plus the recording or a resource, no ask.
  35. 355. **Set the sequence:** hot day 1 email, day 3 call or LinkedIn note, day 7 short bump. Warm day 2, day 9. Nurture day 3, then into the newsletter.
  36. 366. **Write the outputs** (below) and show the summary: counts by tier, the top 10 hot leads, and unmatched notes.
  37. 377. **Ask before anything leaves.** The user reviews drafts and sends them from their own tools.
  38. 38
  39. 39## Output files
  40. 40
  41. 41- `out/follow-up/plan.md`: summary, tiers with reasons, sequence, unmatched notes.
  42. 42- `out/follow-up/hot-emails.md`: one draft per hot contact.
  43. 43- `out/follow-up/templates.md`: warm and nurture templates.
  44. 44- `out/follow-up/import.csv`: `email,first_name,last_name,company,title,tier,reason,owner,next_step,next_step_date,event` for a CRM or email tool import.
  45. 45
  46. 46```markdown
  47. 47# Follow-up plan: <Event>, <date>
  48. 48
  49. 49212 contacts: 18 hot, 64 warm, 121 nurture, 9 removed (duplicates or staff).
  50. 50
  51. 51## Hot (sales calls first)
  52. 52| Name | Company | Why hot | Owner | Next step |
  53. 53| Dana R. | Clinic group (40 sites) | Wants a Q1 pilot | AE 1 | Email day 1, call day 3 |
  54. 54
  55. 55## Unmatched notes
  56. 56- "Guy with the red jacket, wants pricing" (no match; ask the team)
  57. 57```
  58. 58
  59. 59## Guardrails
  60. 60
  61. 61- Never send emails, connect to an email tool, or add anyone to a list. Drafts and a CSV only.
  62. 62- Only email people who gave their details at the event or opted in. Mark contacts from regions with stricter consent rules (EU, UK, Canada) in the CSV so the user can check consent before a marketing send.
  63. 63- Never invent details about a conversation. If notes are thin, the email stays general and says nothing it cannot back up.
  64. 64- Keep contact data in `data/` and `out/follow-up/`. Show names and companies in chat, not full email lists.
Sign in to comment on a line