Riven Contact Graph

The unified view of people and organizations across the platform: one identity for a contact, whether they appear in Mail, Comms, Commerce, or ERP.

The same person shows up as an email sender, a chat participant, a customer record, and a supplier contact. Contact Graph resolves those into one entity, so a question about a customer does not require knowing which system to ask.

What it resolves#

• People — matched across email addresses, phone numbers, and account identities, with a confidence score rather than a blind merge.
• Organizations — companies and their domains, with the people affiliated to them.
• Relationships — who works where, who talks to whom, and how recently.
• Provenance — every attribute keeps its source, so a merge can be explained and reversed.

Who reads it#

• Riven Mail and Comms — sender context, so a thread shows who this is and what else is open with them.
• Riven Commerce — customer identity across quotes, orders, and support.
• Riven ERP — partner records shared across modules instead of duplicated per module.
• Riven Exec — the entity resolution behind "draft a reply to the buyer at that supplier".

Merging safely#

Automatic merges require strong evidence — a shared verified email, not a shared surname. Ambiguous matches are surfaced as suggestions for a human to confirm. Because provenance is retained per attribute, an incorrect merge can be split back apart without data loss.