Share contacts and see what your team is doing
See shared contact profiles, who owns each relationship, and when anyone on your team last spoke to someone.
Once you're on a team, contacts and spheres can be shared so everyone works from the same picture of a relationship, instead of five separate ones.
Why it matters
The worst version of a shared contact is the one nobody actually shares: you have your notes, a teammate has theirs, and neither of you knows what the other has said or done. Shared profiles and cross-team visibility fix that. You always know who last spoke to someone on your team, so you stop guessing and stop duplicating outreach.
How it works
Any sphere, or any collection, can be shared with your whole team at once, or with one specific person. Shared spheres can be read-only or open for teammates to add and edit contacts. When a contact is shared, every team member sees the same profile: the same notes, interactions, events, and reminders. You can also assign a contact to a specific teammate as its owner, so it's clear who's driving that relationship. Because each team member's own email and calendar stay connected, the team can see when anyone last spoke to a shared contact, not just you. And if two team members independently know the same person, Relatable resolves that automatically into one shared contact instead of two separate ones.
How to use it
- On the web: open a sphere and choose the option to share it.
- Choose which team(s) to share it wirth, and pick read or write access. Write access lets teammates add and edit contacts in that sphere.
- Once shared, open any shared contact's profile. You'll see the full history teammates have logged, and, where available, who last reached out and when.
- To assign a contact to a specific teammate, open the contact and set its owner.
- Ownership shows up as a column in the database view and in your CSV exports, so you can filter or report by who owns what.
Good to know
- Sharing a sphere and sharing a single contact both go through the same sharing flow, at the collection level.
- Duplicate contacts across team members are resolved into one shared profile automatically. Ambiguous cases still show up for you to review, the same as duplicate detection on an individual account.
- Team-managed CSV import exists for bringing in contacts on behalf of the team.
- Cross-member "who last spoke to them" only works for contacts that are actually shared. Contacts you haven't shared stay private to you.
- Write access lets a teammate edit or move a contact, so agree on who owns what before opening a sphere up broadly.