Relationship Maps

InsightSquared tracks account engagement using a highly intelligent algorithm based on your real relationships. We call this our "relationship map" and it produces a list of contacts "account.contactAddresses" that we track activity against.

This relationship map understands who you are engaged with, and can then identify related contacts to be auto-generated in the CRM, as well as the activity with those contacts over time.

The relationship map is different than traditional approaches:

• It's not domain based (it's using actual relationships)

  • This means accounts can have multiple domains / overlapping domains (quite common in large enterprise)

• It can ignore non-corporate domains

• It ignores internal team members (team domains)

• It correctly handles partners (indirect channel)

• It can automatically create contacts in the CRM based on gaps it identifies

Now that we've talked about all the things it can handle, how does it work?

First, it takes a full list of all account contacts. This full list can be quite "dirty" as it includes all kinds of things it shouldn't.

• We remove all contacts matching the team domain

• We remove all contacts matching partner domains

Now that we have a cleaner list of contacts, we can look at recent engagement with those contacts (emails and meetings loaded by InsightSquared).

It then identifies any contacts that are "missing" from the relationship map, and either auto-creates them, or prompts the account owner to create them (OOTB configuration)

Activity is only tracked for active contacts in the contact addresses list.

Opportunity relationship maps are similar, but looking at the account (if no roles exist) or the role itself (if roles exist). All the rest of the logic remains the same.

If you run into any issues, please contact support.