Recognize the relationship
Decide how staff will flag an existing customer and what to do when an account match is uncertain. A similar company name alone may not be enough.
Field notes / From conversation to context
A guide for account teams
How to carry event inquiries into account follow-up.
An event conversation is only useful later if its context travels with it. Build a shared route from the first note to the right person’s next action.
Explore the CRM workflow- Capture context
- Match accounts
- Assign follow-up
Fig. 01 Illustrative workflow
CaptureEvent inquiry
ContextConversation note
MatchExisting account
Next stepFollow-up owner
A shared record connects the dots.
The situation / 01
A familiar customer can still become a lost lead.
A customer stops by an event stand and asks about a new use case. Marketing captures the inquiry, but the account manager may not see the conversation note. Sales may treat the contact as new, while the customer expects the team to know their history.
The important design question is not simply where the name lands. It is how the event context, account relationship, and next action stay connected after the event.
Decision points / 02
Make the handoff explicit before the event.
Preserve the reason
Capture what the person asked about and any agreed next step. An attendance label cannot tell an account manager what prompted the conversation.
Name the next owner
Agree when an inquiry belongs with the account manager and when marketing or sales should act. Include a route for records without an obvious owner.
Implementation / 03
Put the inquiry to work in the CRM.
Use these stages to evaluate a CRM and plan the process around it. Test with a sample event inquiry, including one that does not match an account cleanly.
| Stage | Workflow to plan | What to evaluate |
|---|---|---|
| Capture | Record the event, contact details, inquiry topic, and a brief note about the conversation. | Can the fields be tailored to the information your event team actually collects? Check how event records enter the CRM. |
| Match | Connect the inquiry to an existing contact and account, or flag it for review when the match is unclear. | Explore how duplicates are identified and how a person can correct a mistaken or missing match. |
| Assign | Identify the follow-up owner and record the agreed next action. Define who reviews unassigned inquiries. | Check whether ownership, tasks, and relevant notes are visible to the people responsible for follow-up. |
| Review | Look for inquiries awaiting action and discuss exceptions between marketing and account management. | Examine whether views or reports can distinguish event inquiries by account, owner, and follow-up status. |
Field note / 04
Agree on what “followed up” means.
Marketing may count an inquiry as handed off when it is assigned. An account manager may consider it active only after reading the note and contacting the customer. That gap can leave an inquiry untouched without either team noticing.
Before the event, agree on the status that signals acceptance, the next action to record, and who checks exceptions. Afterward, review a small set of records together and adjust the process where context was missing.
Return to the decision points ↑