Turn Booth Notes Into Lead Records

Turns reps' Slack messages, voice memos and business card photos from the show floor into structured lead notes with intent level and next step, matched to your badge-scan list.

Example prompts

Once the skill is added, start a chat with one of these and attach your file if you have one.

  • Here's our #booth-leads Slack channel from the last three days. Turn it into a table and match it to the scan list.

  • Structure these 12 voice-note transcripts from the reps into lead notes with next steps.

  • These business card photos are from the dinner. Pull out the contacts and what we talked about.

What this skill does

The best follow-up material rarely makes it into the lead retrieval app. It's in a Slack channel, a voice memo recorded in a taxi or a stack of business cards from the dinner. This skill reads all of it, splits it into one row per conversation and pulls out who it was, what they asked about, their pain, timeline, budget, intent level and the next step that was actually agreed.

It matches each conversation to your badge-scan list, shows the evidence for every likely match and never merges a guess without your say-so. Personal remarks are dropped, every row links back to its source message, and the result is a notes column ready for lead scoring and personalized follow-up.

When to use it

  • Reps posted booth conversations in a Slack channel instead of the scanner app
  • You have voice-memo transcripts or phone notes from the show floor
  • You collected business cards at a dinner or hallway meeting with no badge scan
  • You want notes attached to event leads before follow-up emails go out
  • Sales asked what was actually discussed with a lead at the booth

How it works

  1. 1IntakeReads your event context file and asks once for the notes, the scan list and the event dates.
  2. 2Split conversationsBreaks messages, transcripts and cards into one row per person, merging later updates into the original row.
  3. 3Extract fieldsPulls out contact details, topic, pain, timeline, budget, intent level and the agreed next step, without inventing anything.
  4. 4Clean out personal remarksDrops comments that don't belong in a CRM and keeps only what helps follow-up.
  5. 5Match to scansMatches each row to the badge-scan list as matched, likely, ambiguous or unmatched, with the evidence shown.
  6. 6Hand offReturns the notes table, a question list for each rep and a merged file for lead scoring.

What you'll need

  • Slack messages or export, voice-note transcripts, text notes or business card photos
  • Optional: the badge-scan list to match against
  • Event name, dates and time zone

What you get

A structured notes table with one row per conversation: rep, timestamps, contact details, topic, pain, current solution, timeline, budget, decision role, competitors mentioned, intent level, next step with owner and due date, match status with evidence and a source reference. It comes with ready-to-append CRM note text, a follow-up question list for each rep and an optional merged scan list for the lead scoring skill.

Tips

  • Ask reps to post one message per conversation with name and company first. It makes matching almost automatic.
  • Run the badge scan cleanup skill on the scan list first so matching works on clean names and companies.
  • Send each rep their question list the same day, while they still remember who "Tom from IT" was.
  • Notes don't create marketing consent. Dinner contacts without a scan get one-to-one follow-up only.
  • Keep the source reference column. It's how anyone can check where a note came from.

What's in the download

  • booth-notes-to-crm/SKILL.md7.2 KB
  • booth-notes-to-crm/assets/sample-scan-list.csv4.9 KB
  • booth-notes-to-crm/assets/sample-slack-notes.txt2.3 KB
  • booth-notes-to-crm/references/examples.md2.6 KB
  • booth-notes-to-crm/references/extraction-rules.md2.9 KB
  • booth-notes-to-crm/references/shared-terms.md6.6 KB
Read the SKILL.md
---
name: booth-notes-to-crm
description: Converts unstructured show-floor notes (Slack threads, voice-note transcripts, phone notes, emails to self, photos of business cards or notebook pages) into structured lead notes with name, company, topic, pain, timeline, intent level and agreed next step, matched to the badge-scan list when available. Use when reps captured booth conversations outside the lead retrieval app, when notes need attaching to event leads before follow-up, or when someone pastes a booth leads Slack channel and asks for a table.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: leads-and-follow-up
  source: https://eventmarketingsoftware.com/skills/booth-notes-to-crm
---

# Booth notes to CRM

The context that makes follow-up work often lives outside the scanner app: a Slack message typed between conversations, a voice memo in the taxi, a business card from the dinner. This skill turns that into one structured row per conversation, matched to the badge-scan list, ready to attach to the lead.

Terms (intent level, badge scan, lead tier, flags) follow [references/shared-terms.md](references/shared-terms.md). The output `notes` text feeds event-lead-scoring and event-follow-up-sequences.

## Intake

1. Read `event-context.md` (or `event-program-context.md`) if present: event name and dates, rep names, product areas, qualifying questions.
2. Ask for anything missing, in one message:
   - The notes: pasted Slack messages or an export, transcripts, text notes, photos.
   - The badge-scan list to match against (clean file from badge-scan-cleanup is best). Optional.
   - Event name and dates, and the time zone the timestamps use.
   - Rep names if the notes only have handles or initials.

## Connectors (optional)

- **Slack connector**: read the named channel or thread for the event dates only. Read only.
- **HubSpot or Salesforce connector**: look up people by email or name and company to match notes to existing records. Write notes only after the approval gate.
- **Google Sheets connector**: read the scan list or write the table to a new tab.
- **Otherwise**: work from pasted text, uploaded files and images, and return a CSV plus a Markdown table.

## Method

### 1. Split into conversations
- One row per person talked to. A single Slack message can cover two people ("Met Dana and her ops lead Priya"): make two rows and link them with the same `conversation_id`.
- Thread replies that add to an earlier message ("update: she booked Thursday") belong to the original row; keep the later timestamp in `updated_at`.
- Ignore chatter that isn't about a contact (lunch plans, booth logistics) and count what you skipped.

### 2. Extract fields
Use the field rules in [references/extraction-rules.md](references/extraction-rules.md). For each row:
- **Who**: first name, last name, company, title, email, phone, exactly as stated. Don't guess an email pattern.
- **What**: `topic` (what they asked about), `pain` (problem in their words), `current_solution`, `timeline`, `budget`, `decision_role` (decision maker, influencer, user, unknown), `competitors_mentioned`.
- **Next step**: what was agreed, who owns it, and when ("demo Thursday 10am", "send case study"). If nothing was agreed, leave it blank; don't invent one.
- **Intent level**: `high`, `medium`, `low` or `unknown`, using the rules in the reference file.
- **Business cards and photos**: read the card text. If a field is unreadable, leave it blank and mark `confidence = low`. If you can't read images in this environment, ask the user to paste the text.
- Keep a short `source_ref` (channel and timestamp, file name, card number) so every row can be traced back.

### 3. Remove what doesn't belong in a CRM
Leave out personal remarks unrelated to business (health, family, appearance, gossip, opinions about the person). Keep only what helps follow-up. Note how many items you dropped, without repeating them.

### 4. Match to the badge-scan list
In this order:
1. Email exact match: `matched`.
2. Full name plus company (cleaned, case-insensitive): `matched`.
3. First name plus company, or full name plus a scan by the same rep within about 30 minutes: `likely`. Show the evidence in `match_basis`.
4. Nothing: `unmatched`. These are often dinner or hallway conversations with no scan; they need a rep to confirm the email before they can be imported.
Never merge a `likely` match without the user confirming. Two possible matches: list both and mark `ambiguous`.

### 5. Write the CRM note text
For each row, build `notes` in one consistent format so it can be appended to the lead's notes or description:

```
[Example Expo 2027, Mar 10, Sam Ortiz] Asked about lead routing when two reps scan the same person. Pain: duplicates in CRM after every show. Current: spreadsheets. Timeline: Q3. Next: demo Thu 10am (Sam).
```

Keep it under 400 characters; no personal remarks; facts only.

## Output

**1. Summary**: messages or files read, conversations found, matched / likely / ambiguous / unmatched counts, items skipped as chatter, personal remarks removed (count only), and any rep who needs to fill gaps.

**2. Structured notes table** (CSV and, if short, Markdown) with columns:
`note_id`, `conversation_id`, `rep`, `captured_at`, `updated_at`, `first_name`, `last_name`, `company`, `title`, `email`, `phone`, `topic`, `pain`, `current_solution`, `timeline`, `budget`, `decision_role`, `competitors_mentioned`, `intent_level`, `next_step`, `next_step_owner`, `next_step_due`, `match_status`, `matched_record_id`, `match_basis`, `confidence`, `notes`, `source_ref`.

**3. Rep follow-up list**: unmatched and ambiguous rows grouped by rep, each with the question to answer ("What's Kwame's email? Card photo was blurry").

**4. Optional merged file**: the badge-scan list with the new `notes` appended (separated by ` / `) and an `intent_level` column, ready for event-lead-scoring.

An example, built from `assets/sample-slack-notes.txt` and `assets/sample-scan-list.csv`, is in [references/examples.md](references/examples.md).

## Validation checklist

- [ ] Every input message about a contact maps to at least one row or is listed as skipped with a reason.
- [ ] Every row has a `source_ref`.
- [ ] No field contains information that wasn't in the source.
- [ ] `likely` and `ambiguous` matches aren't merged without confirmation.
- [ ] Next steps have an owner; due dates are real dates, not "soon".
- [ ] No personal remarks in `notes`.

## Approval gates

- Before writing notes, tasks or field updates to HubSpot or Salesforce, show a preview (record, field, text to add) and get an explicit yes. Append; never overwrite existing notes.
- Don't post summaries back into Slack without showing the message and channel and getting a yes.
- Default to returning files.

## Privacy

- Booth notes are personal data. Keep them in the user's tools; don't search the web for people or enrich them.
- If notes mention EU or UK contacts, carry the consent flag from the scan list; notes don't create consent.
- Unmatched contacts from business cards are fine to follow up one-to-one, but don't add them to marketing lists without consent.

## Related skills

badge-scan-cleanup (clean the scan list first), event-lead-scoring (uses notes and intent level for the lead tier), event-follow-up-sequences (uses notes for personalized first lines), crm-event-import.

FAQ

How do I get booth conversation notes into my CRM?
Collect the notes from wherever reps put them, split them into one entry per person, extract the topic, timeline and next step, and match each entry to the badge-scan record by email or name and company. Then append the note to the lead. This skill does the splitting, extraction and matching and gives you a file to import or a preview to approve.
Can the skill read business card photos?
Yes, if your AI can read images. It extracts the name, title, company, email and phone from each card and marks unreadable fields as low confidence instead of guessing. If your setup can't read images, paste the card text and it works the same way.
What happens when a note could match two people?
The skill marks it as ambiguous, lists both possible records and adds a question for the rep who wrote the note. Likely matches show the evidence, such as first name, company and scan time. Nothing is merged until you or the rep confirm it.
Does it keep everything the rep wrote?
No. It keeps business-relevant facts and drops personal remarks about health, family, appearance and similar topics, because they don't belong in a CRM and create privacy risk for you and the contact. It reports how many remarks it removed without repeating them, so you know something was left out and why.
Do I need a Slack connector?
No. You can paste messages, upload an export or a transcript, or share photos. If your AI has a Slack connector, it can read the channel directly for the event dates, read-only. It never posts back to Slack without showing you the message and getting a yes.