Contacts Graph
Contacts give Nexus a canonical people-and-company layer so conversations, meetings, messages, and workflows resolve back to shared relationship records instead of scattered copies.
Audience: Revenue teams, operators, and anyone needing a single view of a relationship.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
Revenue teams, operators, and anyone needing a single view of a relationship.
Contacts Graph
Contacts give Nexus a canonical people-and-company layer so conversations, meetings, messages, and workflows resolve back to shared relationship records instead of scattered copies.
Philosophy
Relationships should not be fragmented across inboxes, CRMs, calendars, and notes. Nexus treats a contact as a canonical operating object that other parts of the system can reliably reference.
Technically Managed By
- Contacts unify source identities from connected systems into canonical person and company records.
- Timeline events, merge candidates, sync jobs, and linked records create the relationship graph.
- Other surfaces can use contacts as shared context rather than storing disconnected copies of relationship state.
How Users Should Use and Manage It
- 1Use Contacts to review and manage the canonical record for a person or company.
- 2Resolve duplicates and check linked identities when records come from multiple systems.
- 3Treat Contacts as the shared relationship layer for communication, workflows, and follow-up.
How It Fits in Nexus
- Contacts are the identity and relationship layer of Nexus.
- Inbox, Calendar, Integrations, and Automations all become more useful when they resolve back to canonical contacts.
- This is one of the core systems that makes Nexus feel unified rather than app-by-app.
What Matters
- Contacts unify relationship context across systems.
- Timeline history and linked identities make other app surfaces more useful.
- This is the layer that helps Nexus feel like one operating system instead of many disconnected apps.
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.