Managing multiple trade show contacts from the same company

A shared company name does not mean a duplicate person

Keep different people from the same company as separate contacts. Connect their shared conversation through notes, preserve each person's request, and name an owner who coordinates the company's follow-up without erasing individual context.

Several colleagues may visit together, arrive on different days, or speak to different booth staff. Their company is shared, but their contact details, questions, and expectations may be different. Merging them into one record can remove the person who asked a technical question or send a promised document to the wrong recipient. Keep the people separate and connect the conversation through factual notes.

The useful distinction is between a duplicate entry for one person and several real people connected to one organization. A person registering through QR and later handing over a business card may need record reconciliation. Two coworkers sharing a company domain do not automatically need merging. Review identity using the actual contact details and conversation before deciding what to change.

Check who each record represents

Start with the name, individual contact route, company, and the context in which the details were collected. Similar names or a shared reception phone number can be misleading. If a generic company address appears on several cards, ask which person should receive the particular follow-up rather than assuming the address identifies an individual. Keep an unresolved identity question visible until someone can check it.

When the same person revisits, search for the existing record and add the new context where appropriate. When a new colleague arrives, create or find that person's record and note the relationship to the earlier conversation. Staff should not overwrite one person's email with another person's details to make the company look like a single lead. A tidy-looking list is not worth losing a real contact.

Record roles as stated, not inferred from titles

A technical colleague may be evaluating fit, an operations colleague may describe the day-to-day problem, and a purchasing colleague may later ask about commercial terms. Ask which part each person will help assess. Their job title alone does not prove who decides. Record the role they described in this conversation, with unknown details left open.

This approach helps the next owner prepare a relevant message without turning a guessed organizational chart into a fact.

Separate the company context from individual requests

The shared context might be a project, process, or requirement mentioned by the group. Individual requests might be a checklist, a technical answer, or a meeting invitation. Record both layers, but do not make every person's note identical. A shared topic explains why the contacts are connected. The personal request explains what the owner owes each person.

Use a short shared-context sentence in the relevant notes and add a person-specific line. For example: Shared discussion about approval handoffs across two sites. This contact requested the process overview; the technical colleague asked about [condition]. The example is fictional, but the format is reusable. It distinguishes the group conversation from the promise made to this recipient.

Example: three contacts, one coordinated conversation

In a fictional exhibition conversation, an operations manager describes the current process, an engineer asks about compatibility, and a project coordinator offers to arrange the next discussion. The team keeps three contacts. It gives the resource request to the owner who can send the overview, routes the technical question to the appropriate specialist, and asks the coordinator which colleagues should join a later meeting.

A company-level working summary can say: Discussed [shared problem]. [Person A] requested [resource]. [Person B] needs [technical answer]. [Person C] will confirm meeting participants. Coordination owner: [name]. Timing: [agreed date or pending]. This summary belongs in the team's controlled working process. It should point back to the individual context rather than replace the contacts with one combined name.

Name a coordination owner without making every task theirs

A coordination owner checks that the team is not sending conflicting messages or repeatedly asking the same introductory questions. That person may still assign a technical answer to a specialist and a requested document to another colleague. The responsibility is to connect the work and clarify the next step, not to personally deliver every answer.

At handoff, agree who will send the first coordinated message, which individual promises can proceed separately, and how replies will be reflected in the records. If two booth staff spoke to the same company at different times, compare notes before deciding whose message should lead. Do not suppress a visitor's specific request just because another contact has been labeled more important.

Confirm who should be included in the next message

A group visit does not automatically mean everyone wants every follow-up email. Ask who should receive the resource, who should answer a technical question, and who should join the next meeting. Use the contact route and participants agreed with the visitors. If one person wants an individual reply first, preserve that request instead of automatically copying the whole group.

A useful opening can acknowledge the shared discussion while addressing the recipient's question: At [event], you asked about [specific point] during our conversation about [shared topic]. Here is [agreed item]. Would you like [named colleague] included in the next discussion? Keep the wording tied to what happened. Avoid implying that another colleague approved a proposal when they merely attended the booth visit.

Use company search and person-specific notes in BoothCatch

Search the lead list by company or contact details to locate related people. Keep each person's note, owner, next action, and follow-up status aligned with their own request. You can include a shared-topic reference in the note so a colleague understands the connection. The interest level should reflect the interaction with that person, supported by the recorded request rather than copied from the group.

For company coordination in a spreadsheet or CRM, export the event to CSV and build the working view there. The export includes all event leads, regardless of the screen filters. Review name variants and individual contact details before grouping rows. Company grouping is a team review step; do not assume that a search result has automatically created an account hierarchy or resolved identity.

Handle company-name variants without losing the original context

One contact may use a full legal name while another uses a brand or division name. Keep a consistent working label where your team has verified that the organizations are connected. Record a division or site when it affects the requirement. Do not force two similarly named companies into one group without checking. A shared email domain can help investigation, but it is not proof that the people are working on the same project.

For a working report, note the grouping rule and the uncertain cases. People count and company count answer different questions and should not be silently substituted. Three contacts from one company may represent one shared discussion, three separate needs, or a mixture. Explain which interpretation you used and keep the source records available to the colleagues responsible for the next action.

Check the coordinated handoff before sending

Read the company summary and the individual notes together. Can the next owner tell which question belongs to whom and who expects which response? Check for contradictory promises, missing participants, and two staff planning the same introductory contact. Resolve those issues before reaching out, but do not delay a straightforward promised resource just because a larger group meeting is still unconfirmed.

• Different people remain separate contacts.
• Identity questions and company-name variants have been reviewed.
• Shared context is distinct from each person's request.
• Confirmed roles are separated from assumptions.
• A coordination owner connects the individual tasks.
• Recipients and meeting participants follow the visitors' agreement.

Frequently asked questions