Conference Follow Up Email Template That Actually Works

You're back from the event. Your bag smells faintly of convention-center carpet, your phone is at 4 percent, and you have seventeen business cards in your jacket pocket. Three of them have notes on the back. The other fourteen are people you shook hands with while waiting for the coffee line to move.

Here is the uncomfortable truth about a conference follow up email template: it only works when the template has a specific conversation to draw from. A badge scan and a company name do not give you a sentence to open with. A note that says "Sarah — supply chain software, mentioned Q4 budget pressure, said send the case study" gives you three sentences.

This guide walks through a fictional event, assigns contacts to four types, and shows exactly which note fact goes into which part of each email. It also covers a two-colleague ownership table (so you and your co-worker don't send contradictory emails to the same person) and the suppression step that protects both your relationship and your sending reputation.

---

The Event Notes We're Working From

The event is fictional. The logic is the one you'd apply to real notes.

NorCal Ops Summit — illustrative example; fictional attendees and conversations

That last row is not a failure of ambition — it is the correct decision. Sending a personal-sounding networking email template to someone whose name you recognized from a scan, but whose face you cannot place, produces the kind of message that gets marked as spam. If a badge was scanned with no note, add them to a general event newsletter list only if your booth sign-up process obtained consent for that specific use.

---

The Four Templates

Template 1 — Promised Resource

Use when: you told someone you'd send something specific, and they asked you to.

Subject: The case study I mentioned at NorCal Ops Summit

Hi Sarah,

It was great talking through the Q4 pressure you're navigating with your ops team. As promised, here's the AI in operations case study I mentioned — [link].

The section on audit trails in section three tends to be the one that resonates most with teams managing approvals across finance and logistics.

Happy to walk through it on a short call if that's useful, or you can just read it and ignore me. Either is fine.

[Your name]

---

P.S. If you'd rather not hear from me again, just reply "unsubscribe" and I'll take care of it.

What came from the notes: "send the case study" → the subject line promise and the attachment. "Q4 budget pressure" → the opening sentence. "She asked for it" → the tone is confident, not apologetic.

Optional next action: offer a call, but make it low-pressure. One ask.

Second follow-up (bounded): If no reply after seven business days, one short note: "Just checking this didn't land in spam — happy to resend if useful." After that, stop.

---

Template 2 — Potential Customer

Use when: you had a real conversation about a problem they're trying to solve and they didn't push back on the idea of talking more.

Subject: Following up from NorCal Ops Summit — inventory visibility

Hi Marcus,

Enjoyed the conversation about the gaps in your current inventory visibility setup. You mentioned you're evaluating options before end of year, so I wanted to stay on your radar without being the vendor who sends the same deck three times.

We work specifically with wholesale distributors on [specific problem area]. Worth a thirty-minute call to see if the fit is there?

Here's a link to grab time: [calendar link]

[Your name]

---

What came from the notes: "evaluating vendors now" → the timing reference. "Inventory visibility" → the subject line and the opening sentence. "Good conversation" → the tone is peer-to-peer, not a pitch.

Optional next action: calendar link is appropriate here because Marcus indicated active evaluation. Don't include a calendar link if the conversation was more exploratory.

Second follow-up (bounded): One follow-up after five to seven business days if no reply. Reference the first email. Then stop.

---

Template 3 — Referral Partner

Use when: you discussed mutual clients or complementary services and both sides showed genuine interest in exploring referrals.

Subject: Good to meet at NorCal — next step on referrals

Hi Priya,

Really enjoyed the conversation at the summit. You'd mentioned that Relay Dispatch occasionally works with clients who need the kind of operations layer we provide, and I think the overlap is real.

Would it make sense to set up a quick call this week to see if there's a referral arrangement worth putting together? I'm thinking something informal to start — just enough to know when to mention each other.

[Calendar link or time suggestion]

[Your name]

---

What came from the notes: "complementary client base" → the framing. "Wants to explore referrals" → the specific ask. "Connected on LinkedIn already" → no need to introduce yourself from scratch.

Optional next action: calendar link, or just a "does Tuesday work?" — keep it light because the relationship is peer-to-peer, not vendor-to-prospect.

Second follow-up (bounded): One follow-up if no reply. After that, let it rest; referral relationships work on mutual enthusiasm, not pressure.

---

Template 4 — Speaker Thank-You

Use when: a speaker delivered something genuinely useful and you want to open a door without making it transactional.

Subject: Your NorCal keynote on sustainable logistics

Hi Dev,

I attended your keynote at NorCal Ops Summit and wanted to say it was one of the most practically useful sessions of the day. The reframe around supplier lead time versus internal variability is something I'm already using in a client conversation.

No ask here — just wanted to put a real name to the follow on LinkedIn request I sent. If you ever want to talk through the ops side of what your keynote covered, I'd be glad to.

[Your name]

---

What came from the notes: The keynote topic came from the event app, not a personal conversation — so the email does not pretend a conversation happened. No card was exchanged, so the ask is minimal. The email is a genuine thank-you with a soft door-opening.

Optional next action: LinkedIn connection. No calendar link. No pitch.

Second follow-up: None. One message is appropriate when no conversation occurred.

---

The Ownership Table (So Two of You Don't Both Send)

If two colleagues attended the same event and each met Marcus Webb, you need to decide before either person sends anything.

One person sends. The other does not. If Marcus has already replied to Casey, Jordan does not send a separate email introducing themselves. The reply-suppression column exists precisely for this case.

This table does not need to live in a CRM to work. A shared Google Sheet updated before anyone presses send is enough. The important thing is that it's checked, not where it lives.

---

Suppression Before You Send

Two situations require you to hold the email entirely:

1. They already replied. If a contact replied to any previous message — even from a different colleague — check before sending. Sending a "nice to meet you" email to someone who already emailed you last week looks careless.

2. They asked to be removed. The FTC's CAN-SPAM compliance guide requires that opt-out requests be honored within ten business days, and any opt-out mechanism must remain active for at least thirty days after a message is sent (FTC CAN-SPAM Compliance Guide for Business). CAN-SPAM applies to commercial email specifically, so the personal follow-up to one person who handed you their card is governed more by common sense than by statute — but the principle applies to any list-based send from your event.

If you're sending to ten or more contacts from a single event in a batch, treat the suppression step as non-negotiable. Anyone who asked to come off a previous list from your company should not receive this one.

---

The Approval Step Before Sending

The templates above are drafts until a person reviews them. For a handful of contacts, that review is just reading the email before you hit send. For a structured post-event campaign — say, twenty contacts from a conference with a mix of all four types — the review step becomes more important because the chance of sending the wrong variant to the wrong person increases.

The post on drafting, approving, and escalating AI email replies covers the decision that separates a useful draft from an expensive mistake: when to send, when to edit, and when to hand the message to a person who has the authority to make a promise. The same logic applies here. A draft built from your notes still needs a human to confirm the facts are right and the tone fits the relationship before it goes out.

---

When the List Gets Longer: How Beep Beep Fits In

The manual process above works well for a handful of contacts. When the list grows — say, you leave a three-day conference with forty contacts who need different types of outreach, each needing a specific first message and one bounded follow-up if there's no reply — the manual version starts to slip. Follow-ups get forgotten. Two colleagues send to the same person. Replies sit unread for two days.

Beep Beep, Splice Work's email follow-up agent, handles the structured sequence after contacts are loaded and the outreach is approved. According to the product page, it asks in Slack before starting any campaign — no lead search, no credit spend, no CRM write, and no email until you confirm. After approval, it runs up to three waves, writing each message fresh rather than resending the first one. When a reply sounds like genuine interest, it surfaces the conversation in Slack and hands it to a person. It does not negotiate, price, or book on your behalf.

The manual skill this article teaches — reading your notes, assigning a contact type, writing the sentence that could only have been written to that person — is still yours. Beep Beep handles the sequence, the timing, the suppression on reply, and the write-back to Salesforce. The human-in-the-loop approval before sending is the same step whether you're doing it yourself for five contacts or reviewing a campaign card in Slack for forty.

If that describes a problem you're working through after your next event, the Beep Beep product page has the specifics.

---

Before You Send: A Review Checklist

Run through this before any conference follow-up email leaves your outbox.

• The email references a specific conversation, not just the event name
• Every sentence is supported by a note, not inferred from a badge scan
• Subject line matches the specific follow-up type (resource / meeting recap / referral / thank-you)
• One clear next action — not three options
• Second follow-up is bounded (once, with a stop after no reply)
• Contact is not on a suppression list and has not already replied
• If two colleagues met this person, one owner is confirmed in the shared table
• Opt-out path is present for any batch or commercial send
• A person reviewed the draft before it was sent

---

An Exercise You Can Try Now

Pull out the cards or notes from your last event — or invent a fictional one with three contacts.

For each contact:

1. Write down the one sentence you remember from the conversation.
2. Assign a type: promised resource, potential customer, referral partner, speaker, or do-not-email.
3. Write the subject line using only that sentence.
4. Draft the opening line using only the note fact.

If you cannot write the opening line without inventing something, that contact goes in the do-not-email column — not because you failed, but because the networking email template you write to them would be worse than no email at all.

The Salesforce blog on sales follow-up emails puts it plainly: jot down notes about your conversation on their business cards right after a meeting, then continue the conversation within a week (Salesforce: Sales Follow-Up Email Templates). The note is the email. If the note doesn't exist, neither does the reason to write.