How to get sales to follow up on event leads

Why doesn’t sales follow up on event leads?

Because marketing owns the metric and other teams do the work. Your events leader answers for what the show produced. SDRs, AEs, executives, and customer success do the follow-up, and none of them report to her. Events operators describe the same setup at company after company.

Your reps follow up on event leads when their sales manager can see the follow-up. That takes a named owner per lead, a clock, and an unworked-lead queue your sales manager sees at the same time as your events leader. The FieldXM thesis argues that the industry has filed this coordination problem under marketing by mistake.

Every quote here comes from people who run in-person GTM, operators to CMOs at companies from $5M to $500M ARR. The advice draws on 300+ events the FieldXM founder has operated.

Start by taking your reps’ side. Your rep gets the post-show list the week she’s closing the quarter. It’s 200 names, most with a company, a title, and nothing else. Opening with “great meeting you at the booth” to someone she never met is a cold call with a worse excuse. So the rational move is to work her open opportunities and let the list age.

“Please follow up” has been the policy for as long as anyone has run a booth. To fix it, change what your reps get and who sees what they do with it.

Why do reps ignore the kickoff doc?

Because it can’t track anything. Marketing writes a kickoff doc once, before the show. It holds the travel, the target accounts, the messaging, and the follow-up expectations, and it sits outside the tools your reps work in. The doc reads the same whether a rep acts or not. So you can’t enforce any of it, and reps learn fast that reading it is optional.

Mature programs show the same pattern. A director of marketing events at a software company above $200M ARR runs roughly 275 events a year. She has the same information in a master spreadsheet, a project management tool, creative briefs, chat channels, and a kickoff doc. Reps there ignore the doc, then message marketing with the questions it answers.

A director of events at an enterprise software company running about 200 events a year described sending sales a spreadsheet of target accounts and watching it go unread. The doc fails for small programs and large ones for the same reason: follow-up is a workflow, and a document can’t track who did what.

What does an enforceable follow-up workflow look like?

It has 4 elements. Each one replaces a sentence in the policy with something both teams can see.

Element	The policy version	The enforceable version
Owner	“Sales will follow up on their leads”	Every lead has a named owner: CRM ownership sets it, a fallback rule covers the rest, and marketing and sales both see it
Clock	“Within a few days of the show”	A first-touch window that starts at show close, a timestamp on the first activity, and a state per lead: not contacted, engaged, booked, meeting held
Queue	A hunch that your reps never touched some leads	A list of leads past the window with no activity, in priority order, by owner
Escalation	Marketing sends a reminder	The sales leader reviews the queue in an existing sales meeting, on screen

The queue works because of who sees it. Reps answer to the sales manager, so build the queue as a sales management view first and a marketing report second. When your head of events can walk into the sales standup with a list of leads untouched past the window, rep by rep, the sales leader takes over the follow-up conversation. That conversation rarely happens today, because the list doesn’t exist.

Give every lead an owner and a first-touch deadline in FieldXM. It flags each miss while the lead is still warm, and FieldXM’s accountability reports list the misses by rep for your sales standup. Run the loop in a spreadsheet if you must, as long as both leaders look at the same queue.

What about leads reps work outside the process?

They disappear from the event’s record, and they’re the most dangerous kind, because you don’t know how many there are. Your rep skips the scanner, types the prospect’s name into the CRM, finds a record that already exists from some other source, and creates the opportunity off it. The deal may close, and the event that produced it is gone from the story.

“I’ll never see it.”

A director of marketing events at a software company above $200M ARR, running roughly 275 events a year, on leads reps work outside the capture process

She catches a handful every week and never learns how many she misses.

The same loss happens 2 other ways. At another company, reps skip the scanner on purpose, to dodge round-robin assignment and keep the lead.

And where your sales team has a lead-claim rule, another rep eventually claims the unworked event lead, works it as new, and drops it from the event’s record. At one company, any SDR can claim a lead untouched for 30 days, and the events leader finds them months later.

Run an attribution leak check after each event. Compare the CRM records your reps created or advanced in the event’s date window against the event’s account plan and its scans. Review anything that touches an account on the plan and didn’t come through the capture path. The check catches part of the leak and turns “I’ll never see it” into a list.

How do you get sales leadership to agree to this?

Bring the number and ask for a meeting slot, since you’ve already tried asking for a policy.

Agree the window and the states with the sales leader before the show, in writing. Handle the reps’ objection at the same time: leads will arrive with a pain point, a product interest, a next step, and a tier.
Put the review into a meeting that already exists. Reps will skip a new meeting that marketing owns, for the same reason they skipped the doc.
Report attempt rate by owner, weekly, to both leaders. A director of events at a company running about 200 events a year treats anything under 90% as unacceptable and names the gaps.
Share the off-process list too. Attribution that leaks from the event leaks from the sales forecast as well.

Expect this to feel unnecessary at larger companies, where headcount and habit have covered up the pain.

“The pain is like scabbed over.”

A VP of product marketing at an enterprise software company above $400M ARR

Go deeper

The FieldXM thesis: the coordination failure in 3 acts, and why your teams leave the after-show act unowned.
Attribution leak: the definition and the detection check.
Attempt rate: the metric and the 90% bar.