Skip to main content

Overview

A Contact is one record from one source: an email address from your sequencer, a LinkedIn profile from HeyReach, a record synced in from Close CRM. A Person is the human behind those records. When the same person shows up through more than one channel, for example their work email from an email campaign and their LinkedIn profile from a LinkedIn campaign, RevyOps links those contact records together under a single person. You see one person with their email contact and their LinkedIn contact grouped together, instead of two separate, disconnected records for the same human.

What You See

On the People page, each row is a person, not a single contact. Opening a person shows:
  • Every identifier attached to them (email addresses, LinkedIn URLs, phone numbers), each carrying its own status, company, job title, and campaign history
  • A combined Timeline of activity across every one of their contact records
  • Custom field values from all of their contact records, unified into one list
Fields that repeat across contact records (like a title or company) show the most recent value first in list views, with older values available in a popover. Click any field to edit it in place, the same as on a Contact record. A LinkedIn URL opens directly when clicked.

Adding and Removing Identifiers

A contact holds exactly one identifier, so a person with an email and a LinkedIn profile has two contacts. On a person’s page:
  • Add identifier under Standard fields adds an email, LinkedIn URL, or phone number. It is saved as another contact on the same person, with the same name and company. If the person is on the do-not-contact list, the new contact is too, and RevyOps sends the person’s identifiers to your connected tools again. Formats are checked as described in Identifier Formats.
  • The trash can appears when you hover an identifier and removes it. It is grey with a tooltip when the person has only one identifier, because a person always keeps at least one. Removing deletes the contact that holds it, with its emails, LinkedIn messages, calls, activities, and custom field values. The dialog counts them, says if the contact is linked to HubSpot or Close, and asks you to type DELETE.
  • A value that already belongs to another record is never duplicated. If it is already on this person, the message says so. If it belongs to another person, the dialog names them, links to their page, and offers to Merge the two people, which opens the same merge dialog as the People page: you compare the two side by side and confirm a Final name. The merge keeps every identifier from both, combines their custom fields, and leaves you on the same page. Merging deletes the other person’s score history and recalculates the score. A contact can be detached into its own record again later. Example: adding jo@acme.com to Jo Lee’s page when a different Jo already has it offers to merge the two.
On a Contact page the identifier can be edited but not removed, and its trash can is always grey. Changing an email sets its verification status back to unchecked, since the old result described the old address. On a Company page the domain can be edited but not removed, because every company has one. It is stored without https:// or www., so https://www.Acme.com/about becomes acme.com. The LinkedIn URL can be removed after a confirmation.

Merging People

If RevyOps hasn’t automatically linked two people who are actually the same human, you can merge them yourself from the People page. Merging combines every contact record from the people you select into one person.
  • You choose which people to merge and confirm a Final name, which replaces the first and last name on every contact record in the unified person.
  • No data is lost in a merge. Every other value from every contact is kept. Where the same field has multiple values, the most recent shows first, with the rest available in a popover.

When Contacts Stay Separate

RevyOps also links contacts to the right person automatically as new activity comes in. When two contacts have different names filled in, RevyOps keeps them as separate people. If they are the same human, merge them yourself. Merges you start yourself from the People page are not subject to this check, since you’re confirming the merge and choosing the final name directly.

Splitting People

If two different humans were merged into one person by mistake, you can split their contact records back apart. Splitting moves the contact records you choose off of the existing person and onto a newly created person, leaving at least one contact record behind on the original person.

People API

The People endpoints under /public/people let you search, look up, merge, and split people programmatically: A person response includes their name, and their emails, LinkedIn URLs, phones, and custom fields, each carrying the company, job title, status, and campaign dates from the contact record it came from.
The merge and split endpoints require a master-level API key.