Can I send a calendar link after a conference chat?

Only if they asked for time. Unsolicited holds make the drinks feel like a trap. Send the page you promised. Offer ten minutes as optional. If they want a meeting, they'll propose it. Department heads compare notes on vendors who booked them from a badge scan.

What if I promised an intro and also want a meeting?

Make the intro first. Do not hold the intro hostage for a demo. That's how you spend their political capital without permission. After the intro lands, they can decide whether to continue. Mixing favors with a funnel is how hallway chats become warnings in Slack.

Should I connect on LinkedIn and skip email?

You can do both if the note stays short. Don't paste the pitch into LinkedIn. Two sentences plus the page is enough. Email files better when they need to forward to a deputy. LinkedIn-only threads die in notification noise after a conference week.

What topic is safe to repeat from a noisy hallway?

Stick to operational toil they volunteered: tickets, SSO, go-live load. Don't repeat gossip about a VP, a layoff, or a competitor they roasted. If you're unsure it was public, leave it out. SaaS is a small town at the director layer. Discretion is the follow-up.

Do I follow up if the chat was 90 seconds at a booth?

Only if there was a real sentence to continue. A polite nod is not a thread. If all you have is a badge scan, you're writing cold mail with extra steps. Wait until you have a useful page that matches something they actually said. Otherwise don't send.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · Department Head · After Networking

Follow-Up Email After Networking with a SaaS Department Head

A follow-up after you met a SaaS department head in a hallway should continue the implementation chat, not convert it into a pitch. Remind them of the ticket pile, the SSO stall, or the go-live they actually named. Then one optional next step. Long bios are homework. They don't owe you a funnel.

Copy-ready template

Subject

The CS ticket comment after [Event]

Body

Hi [First Name],

Good running into you at [Event]. I've been thinking about what you said on the [CS queue / SSO review / week-three go-live] still eating the team after the last tool.

Here's the 1-page I mentioned on week-one touches vs. on-call. No need to reply. If a 10-minute continuation would help before [Planning Date], I'm around. If not, I'll leave this here.

[Your Name]
[Your Title]

Why this follow-up works

It uses a shared moment instead of writing like a stranger.
The promised page arrives without a hostage calendar link.
Optional language respects that a hallway is not a discovery call.
You named their toil, not your category.
A no-need-to-reply line makes silence socially cheap.

When should I send this to a SaaS Department Head?

Within two days. After that you're a vague name from a badge. Mention where you met and the topic, send anything you promised, and keep the ask optional. Don't write during the keynote they said they were skipping to take a Sev. Don't drip a three-email sequence that pretends the hallway was a qualified opportunity. If they don't answer, one archive line a week later is the ceiling. Event weeks are loud. Tuesday after they fly home beats the Uber on the way to the airport. If they asked you to wait until after a GA, wait.

What this Department Head actually cares about

A department head at a conference is protecting time and not looking reckless in front of peers. They will read you on a phone in an airport line. The first two lines have to name the toil you both stood on. A long origin story is how you become the person they dodge at the next booth. Offer a page they can refuse. Don't CC their VP because you found the email on the badge. Don't quote a complaint they made about their stack in a way that would embarrass them. Hallway candor is not a case study. Keep it human. Keep it short. Their standing with the team they flew with is the real product.

How SaaS changes the note

SaaS events are full of people who treat a hallway as a pipeline. Department heads notice. The follow-up that earns a look continues a real sentence about implementation toil: tickets after go-live, an IdP review that parked a project, a CS team still supporting a tool that demoed well. Time-to-first-value is a metric. A beer is not a buying signal. If you dump a Calendly as the first move, you retroactively made the chat feel extractive. Local proof here is operational proof: a page they can use this week. Vague growth language gets archived with the other 40 vendor emails from the same badge scan. Quiet after networking often means they were being polite in public. Reward honesty with a small artifact and an easy ignore.

Customization tips

Name the event and the room. A SaaS conference is not specific enough.
If you promised an intro, make the intro. Don't swap it for a pitch.
Don't BCC a nurture list. They will find out.
If they were with a team lead, don't write as if you cornered them.
Send the next morning, not Sunday night after drinks.

Common mistakes

Dumping a calendar link as the entire follow-up.
Re-introducing a bio they already heard.
Pitching as if the drinks were a demo.
Writing a note that still works if you swap the event name.

How this scenario compares

Dimension	For this template
Best send window	1-2 days after the event, not the Uber ride
Ideal length	Under 90 words plus the promised page
Primary ask	Optional continuation, or nothing
Unlike a cold email	You have a shared moment. Use the toil they named.
Unlike an introduction email	You already met. Don't restart the bio.

Questions people ask before they hit send

Within two days. After that you're a vague name from a badge. Mention where you met and the toil topic, send anything you promised, and keep the ask optional. If they wanted a pitch, they would have asked. A hallway is not a qualified stage in your CRM.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1040.