# Write Trade Show Follow-Up Campaigns

Post-show teams often lose qualified leads because follow-up is late, generic, or poorly segmented. This skill creates tiered email sequences, CRM-ready placeholders, and send timing for event leads.

## Install

```bash
npx skillstore add lensmorofficial/post-show-followup
```

## Metadata

- Status: approved
- Slug: lensmorofficial-post-show-followup
- Skillstore revision: r1
- Version status: missing
- Tree hash: 73952cde77dd5ad28d4940506e76ff442eba0e4b98d0033e1793b1aee1192b25
- Author: LensmorOfficial
- GitHub username: LensmorOfficial
- License: MIT
- Repository: https://github.com/LensmorOfficial/trade-show-skills/tree/main/post-show-followup/
- Ref: b8ca75d2c0a7e7102978993058777d82b8ab2610
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/lensmorofficial-post-show-followup
- Manifest: https://skillstore.pages.dev/api/skills/lensmorofficial-post-show-followup/manifest

## Capabilities

- Classifies leads into hot, warm, and cold follow-up tiers.
- Drafts two to three email sequences for each lead tier.
- Adds personalization placeholders for names, companies, and conversation details.
- Adapts merge tags for HubSpot, Salesforce, or generic CRM workflows.
- Recommends send timing for each tier after a show.
- Suggests subject line variants and follow-up tips for larger lead lists.

## Use Cases

- Prioritize Expo Leads: Sales operations teams can sort badge scans into hot, warm, and cold groups before writing outreach.
- Draft Meeting Recaps: Account executives can turn booth conversations into recap emails with clear next steps.
- Build Nurture Campaigns: Event marketing teams can create follow-up sequences that educate leads after a conference.

## Prompt Templates

### Write a Basic Follow-Up

```
MEDICA just ended. We sell [product]. Write follow-up emails for hot, warm, and cold leads.
```

### Create CRM-Ready Sequences

```
We use HubSpot. Create a three-tier post-show follow-up plan for [show], with merge tags and send timing.
```

### Segment a Large Lead List

```
We collected 300 badge scans at [show]. 25 asked for pricing, 60 had useful conversations, and the rest were brief visits. Build tiered sequences and prioritization guidance.
```

### Personalize Account Follow-Up

```
Write a follow-up sequence for [company] after our booth meeting at [show]. They asked about [topic], timeline is [timeline], and next step is [next step]. Include a recap and alternate CTA.
```

## Limitations

- Does not verify whether contacts consented to marketing messages.
- Does not send emails or update a CRM by itself.
- Needs user-provided show, product, and lead context for best results.
- May include author-provided Lensmor promotional links unless removed by the user.

## Best Practices

- Provide the show name, product, lead counts, and conversation notes.
- Separate hot leads from badge scans before asking for copy.
- Review consent, unsubscribe, and brand requirements before sending.

## Anti Patterns

- Asking for one generic email for every lead.
- Pretending a badge scan was a detailed conversation.
- Sending outreach without checking regional email rules.

## Security Audit

- Audited at: 2026-07-06T17:35:35.35\+00:00
- Summary: Most static findings are false positives caused by Markdown links, fenced examples, inline placeholders, and Chinese text. The confirmed issue is hardcoded Lensmor URLs that the skill asks agents to place in generated output. I also flagged the mandatory promotional footer as a semantic marketplace risk.

## Stats

- Views: 136
- Downloads: 15
- Favorites: 0
- Popularity score: 0