How RevSure Associates Meetings and Chats with Leads, Accounts, and Opportunities

Prev Next

RevSure connects meeting and chat activities with the appropriate CRM records so that engagement can be analyzed across the customer journey.

For each activity, RevSure attempts to identify:

  1. The Lead or Contact associated with the activity

  2. The corresponding Account

  3. The relevant Opportunity, when a reliable association is available

RevSure primarily relies on existing CRM identifiers, email addresses, and trusted CRM relationships rather than interpreting conversation transcripts to determine these associations.

How Association Works

The association method depends on the source system and the information available from that source.

GoodMeetings

For GoodMeetings, RevSure uses meeting attendee email addresses to identify the corresponding CRM Lead or Contact.

Once a person is identified:

  • The Account is taken from the Account associated with that Lead or Contact.

  • RevSure evaluates the Account's opportunities to identify an opportunity whose lifecycle overlaps with the meeting date.

  • If multiple opportunities match, the most recently created applicable opportunity is selected.

  • A matching Salesforce meeting or task can also be used to identify the Opportunity.

Associations are maintained at the individual attendee level. This allows a single meeting to represent multiple participants or companies when applicable.

Gong

Gong provides CRM identifiers directly on the call, giving RevSure a stronger association signal.

RevSure uses these CRM identifiers to determine:

  • Lead or Contact — from the CRM person associated with the Gong call

  • Opportunity — from the CRM Opportunity associated with the call, when available

  • Account — from the associated Lead/Contact or Opportunity

When both a person and an Opportunity are available, the Account associated with the Opportunity takes precedence.

Note: If the Lead ID or Contact ID is not available, we use the participant’s email address to associate the engagement with the corresponding Lead or Contact in RevSure, similar to the association logic used for GoodMeetings.

Slack

For Slack activity, RevSure uses the message author's email address to identify the corresponding CRM person.

The Account can then be determined using available signals such as:

  • Customer or Account information represented in the Slack channel

  • The author's email domain

  • The Account associated with the matched CRM person

For Opportunity association, RevSure prioritizes an applicable open Opportunity associated with the person. If no open Opportunity is available, existing closed opportunities may be considered.

Drift and Intercom

For Drift and Intercom conversations, RevSure uses the visitor's email address to match the activity with a Lead or Contact in the CRM.

The associated Account is then derived from that CRM person.

RevSure does not automatically associate an Opportunity based only on the timing of the chat.

Qualified

For Qualified conversations, RevSure uses CRM identifiers supplied by Qualified to identify the corresponding Lead or Contact.

The Account is then derived from the matched CRM record.

As with other chat sources, RevSure does not infer an Opportunity solely from the timing of the conversation.

Account and Opportunity Association Rules

When RevSure identifies a Lead or Contact, the Account associated with that CRM record is used.

When an Opportunity has also been identified, the Account associated with the Opportunity takes precedence. This ensures that reporting remains aligned with the deal being analyzed.

Opportunity association is performed only when RevSure has a reliable signal, such as:

  • An Opportunity ID provided by the source

  • A meeting occurring during an applicable Opportunity lifecycle

  • A matching CRM activity associated with an Opportunity

RevSure does not assign an Opportunity simply because the conversation content appears related to a deal.

Source-Level Summary

Source

Lead / Contact Association

Account Association

Opportunity Association

GoodMeetings

Meeting attendee email matched to CRM

Account associated with the matched person

Opportunity lifecycle overlapping with meeting date or matching Salesforce activity

Gong

CRM Lead/Contact ID provided on the call

Account from the person or Opportunity

CRM Opportunity ID provided on the call

Slack

Message author email matched to CRM

Channel, email domain, or matched person's Account

Applicable Opportunity associated with the person

Drift / Intercom

Visitor email matched to CRM

Account associated with the matched person

Not inferred from conversation timing

Qualified

CRM identifiers provided by Qualified

Account associated with the matched person

Not inferred from conversation timing

What This Means in RevSure

  • Meeting and chat engagement is included in Lead, Account, or Opportunity analysis only when RevSure can establish an appropriate CRM association.

  • An activity may have a known Lead or Contact but no Account if the corresponding CRM record does not have an Account association.

  • GoodMeetings can associate multiple attendees from the same meeting independently, supporting buying-group and multi-company conversations.

  • Gong primarily relies on the CRM identifiers already associated with the call.

  • Opportunity associations are based on trusted CRM relationships and activity metadata rather than conversation transcript interpretation.

This approach helps keep RevSure's engagement and attribution reporting aligned with the relationships already maintained in your CRM.