Handle Business Cards Without Assuming Broad Consent

Preserve the context of a business-card exchange, distinguish requested information from marketing, and keep uncertain follow-up outside active lists.

10/23/20263 min read

Morgan’s fictional card accompanies a checklist request, not an unlimited marketing subscription.
Morgan’s fictional card accompanies a checklist request, not an unlimited marketing subscription.

“Here is my card” can accompany a request for a quotation, an agreement to exchange technical information, or a polite end to a conversation. The card supplies contact details. The surrounding conversation supplies context. Losing that context during intake can turn a modest exchange into an unjustified marketing subscription.

Use a card-intake checklist that records what was actually discussed without inventing a broader permission. The goal is to fulfill a clear request where appropriate and route uncertain follow-up through the applicable rules review. Owning a stack of business cards is not a contact strategy.

Capture the interaction, not a retrospective story

Record when and where the exchange occurred, who participated, the business topic, and any specific next step. Distinguish a direct request from your own suggestion. “Asked for a maintenance checklist” is different from “might like our newsletter.”

Keep only necessary details. Photographing or scanning a card through an external service may introduce another data destination that needs approval. Use the organization's authorized intake method and avoid storing extra personal commentary about the meeting.

For US commercial email, the FTC's CAN-SPAM guide makes clear that B2B messages are not exempt. That is a US federal requirement, not a worldwide permission rule. Other jurisdictions, channels, source restrictions, and recipient preferences require their own assessment.

Work through a fictional card intake

At a synthetic facilities conference, Morgan from fictional Pine Facilities gives a consultant a business card after discussing a scheduling checklist. Morgan says, “Please send the checklist we discussed to this work address.” The intake record should remain narrow.

  • Source: direct card exchange at the named event, with date.

  • Requested action: send the discussed checklist once by work email.

  • Sender: the consultant's identified business.

  • Relevant context: scheduling process discussion; no claim of a buying project.

  • Not established: newsletter subscription, telephone calls, partner sharing, or unrelated product promotion.

  • Next step: check existing restrictions and the approved sending route, then fulfill the bounded request if permitted.

The example is fictional. It does not demonstrate that every spoken request satisfies every applicable legal condition. It shows the level of factual detail a reviewer needs.

Compare a genuinely ambiguous exchange

Now imagine a second person hands over a card after saying, “Interesting to meet you.” No deliverable, channel preference, or next step is discussed. Mark that record as an unreviewed contact exchange. Do not rewrite it as “requested information” to fit an import field.

A reviewer may consider whether a limited follow-up is appropriate under the actual context and applicable rules. The salesperson should not resolve the uncertainty by sending a broad campaign first and interpreting silence as acceptance. If there is no justified action, retaining less information or closing the contact record may be the right outcome.

A generic company card creates another distinction. A shared reception address does not identify the individual who handed it over. Do not attach personal preferences or a guessed name to the shared route without evidence.

Keep the promised follow-up bounded

Where the requested checklist can appropriately be sent, provide that checklist and the context necessary to recognize it. Avoid adding unrelated promotions merely because the email is already being composed. If the message's purpose materially changes, review it as the new communication it has become.

Record completion separately from future eligibility. “Checklist sent” means a promise was fulfilled; it does not mean the recipient is now subscribed. Preserve any response or stop instruction through the normal preference process.

Review unresolved card records before they accumulate into a historical list. Define who owns the decision, what evidence is missing, and when continued retention should be reconsidered. Do not use an indefinite research status to keep cards available for eventual marketing.

The finished checklist should let another teammate reconstruct the exchange without overstating it: source, actual request, sender, channel, purpose, restrictions, action, and review decision. That makes a business-card handoff useful while respecting the difference between sharing contact details and agreeing to unlimited future promotion.

If you are also choosing research access, ask about Leads Automation’s independent Sales Navigator offer at US$15/month on WhatsApp. Confirm the available plan, eligibility and terms before ordering; this is not LinkedIn’s official price or an assurance that any particular integration is included.

Sources and scope

Related guides