A conference badge rests beside conversation notes and organized account folders.
By

A conference badge scan needs context before sales follow-up

Estimated reading time: 5 minutes

Before sending trade show lead follow-up, separate the scan, the company fit, and the conversation. A badge scan alone does not establish a need, buying authority, or permission for sales outreach.

For a B2B seller, the useful decision is whether the next action should fulfill a promise, investigate an account, continue an existing relationship, or stop. A working email address cannot make that decision.

This guide starts after capture. It adds an account and conversation check before a record becomes a sales task. Your team still needs to verify the event's data terms and the rules that apply to the proposed contact.

Preserve what happened at the event

Record the event edition and the source of the contact. Distinguish a badge scanned during a conversation from a badge scanned for a giveaway or an organizer-supplied attendee record. These circumstances support different wording.

Keep the person's words separate from the rep's interpretation. “Asked whether the software works with our ERP” records a question. “Ready to replace the current system” adds an unsupported purchase conclusion.

When the original rep cannot recall the discussion, mark the conversation as unknown. Do not manufacture familiarity to make an automated message sound personal. “Good to meet you” needs a meeting that the sender can substantiate.

Use this template to prepare the decision:

Event / edition / date:
Contact / company / matched account reference:
Capture source and original record:
Rep who spoke with the person, or unknown:
Exact question, request, or clear paraphrase:
Promised material / owner / due date:
Account fit evidence / source / checked date:
Person's role evidence / unknown responsibilities:
Existing customer, deal, owner, or restriction:
Contact preference and applicable outreach checks:
Next decision / owner / unresolved question:

The template preserves evidence. Completing every field does not qualify an opportunity; “unknown” is a valid result.

Research the account against the offer

Review the account using the same criteria you would apply outside the conference. The event explains where the record came from. It does not replace the company's fit requirements.

Suppose you sell production scheduling software. A manufacturer's exhibitor listing can help identify the business. To decide whether your offer fits, check the relevant operation, production environment, supported geography, and any essential integration constraints. A company selling to manufacturers may exhibit at the same show while having no manufacturing operation of its own.

Then check the person's responsibilities. Someone can understand the problem without choosing a supplier or approving expenditure. Preserve the unanswered questions for the conversation instead of upgrading a job title into authority.

Quantonica's research methodology includes checking company context and purchasing responsibilities. Its offer concerns research and outreach; it does not supply a badge scanner or run the conference.

Choose an action from the evidence

Use this proposed decision table before assigning a sequence. The examples concern B2B sales, not consumer event registration.

What the record supportsAction to considerWording to avoid
Relevant account and requested documentSend the requested document through the agreed route“You are ready to buy”
Relevant account and a recorded problem, without a next-step agreementContinue the recorded discussion with a bounded question, if contact is appropriate“Following up on our agreed demo”
Relevant account, scan onlyInvestigate fit and contact conditions; hold sales follow-up until resolved“As we discussed”
Existing customer or open opportunityGive the note to the current account ownerA new cold introduction from another rep
Poor account fitFulfill any valid promise separately, then close the prospecting taskA sequence justified only by attendance
Objection, opt-out, or unresolved restrictionApply the restriction and stop the affected activityAn assumption that scanning cancels the restriction

A promised action and a prospecting action can have different owners and purposes. Sending a document someone requested does not create permission for an unrelated continuing sequence. Resolve the applicable contact conditions before adding that activity.

Test campaign admission with three records

These are illustrative records for a fictional scheduling software seller. The company facts and conversations are assumed, not observed results. Each test concerns admission to a campaign, rather than how to capture a conversation or book a meeting.

Record A: a requested document. The operations manager of Example Components asks for the ERP integration guide. Account research confirms a production operation inside the seller's supported market. Budget and supplier authority remain unknown.

Create a task to send the guide through the agreed route. Keep sequence admission undecided until the contact conditions, proposed purpose, and account restrictions have been checked. The document request supports fulfilling that request. It does not, by itself, support an ongoing sequence.

Record B: a scan without a discussion. A consultant enters a booth prize draw. The export contains a name and email but no conversation. Research shows that the company advises manufacturers rather than operating factories.

The record fails the assumed customer criteria. Adding a relevant industry keyword to a message would leave that mismatch unresolved. Close the new-customer admission request. Assess a partner use case separately only if it has its own criteria and appropriate contact conditions.

Record C: an account in another campaign. A manufacturer fits the offer, and the contact has a relevant responsibility. A different rep already has an active conversation at the account.

Hold the new sequence and route the event evidence to the current owner. Record the outcome as an ownership decision. Do not mark the contact as a poor fit merely because this campaign should not send.

Use this admission receipt for the proposed campaign:

Campaign / purpose / proposed channel:
Contact and matched buying account:
Account criterion passed, with evidence:
Conversation claim permitted by the original note:
Requested task handled separately, if any:
Contact conditions and restrictions checked by:
Existing owner / active campaign check:
Decision: admit / hold / exclude
Reason, deciding owner, and time:
Fact that would change this decision:
Recheck required before sending:

A record marked “admit” has passed this proposed campaign check. It is not an opportunity stage, a purchase signal, or an authorization for unrelated future campaigns. Recheck facts that can change before the message sends.

Leave uncertainty with the person who can resolve it

A sales task should state the action and the evidence behind it. “Conference lead: follow up” makes the receiving rep reconstruct both.

For each record, name the unresolved question. The research owner can check the production location. The original rep can clarify a promised document. The account owner can decide how to continue an existing deal. Only the buyer can confirm some purchasing details.

Before releasing the follow-up file, compare one admitted, one held, and one excluded record. Confirm that each decision has evidence and that fulfilling a promise did not silently enroll the person in a sequence.

Don't miss out

How to ask for a small next step without hiding the sales intent
2026-11-18

How to ask for a small next step without hiding the sales intent

Commitment decision ladder plus a worked resource request, fulfillment and separately agreed transition to discussion.

Continue reading
Which AI BDR decisions should a person approve?
2026-11-16

Which AI BDR decisions should a person approve?

Assign AI BDR approval rights with a decision matrix, evidence requirements, expiry conditions, and tests that rejected actions stay blocked.

Continue reading
Founder-led sales and founder-dependent sales need different fixes
2026-11-13

Founder-led sales and founder-dependent sales need different fixes

Separate founder judgment from repeatable sales tasks. Use a delegation boundary map, task brief, and exception review for B2B sales.

Continue reading
A LinkedIn message should have one useful job
2026-11-11

A LinkedIn message should have one useful job

Purpose-selection table and four labelled fictional messages with purpose-specific reply interpretation.

Continue reading