The people you talk to, already in one place
Every person you deal with, with your history attached: when you last spoke, what it was about, and who said they would do what. It assembles itself from the accounts you have already connected. You never fill it in.
Get startedIt fills itself from what you already connected
Address books go stale because they ask to be maintained, and maintenance is the first thing to go. So this one is not something you keep up. It is assembled from the accounts you connected for your inbox anyway, and it stays current as those accounts change.
Every channel feeds it
Google Contacts, Outlook, Slack, Google Chat, Teams, Telegram, and your this+that teammates all flow in. Names, email addresses, phone numbers, job titles, and each platform’s avatar come across with them.
One person, not four half-people
The same human arrives as a work address, an invoicing address, and a Slack handle that know nothing about each other. We resolve them into a single record that carries every origin it came from, and anything the sync gets wrong you can merge yourself.
Your edits survive the sync
Correct a job title that is two roles out of date and the next sync leaves it alone. Delete an address that person stopped using and it does not come back an hour later. Sync-backed address books usually get this wrong, and getting it wrong is what teaches people to stop editing.
Add someone by hand when you need to
The person you met at a conference is not in any connected account yet. Create the record, add what you have, and it lives alongside the synced ones without being overwritten by them.
Open a person and see your correspondence
A card with a phone number on it answers a narrow question, and often not the one you came in with. More of the time you want to know what your history with this person looks like: when you last spoke, what it was about, and who said they would do what.
So each person carries their thread history. As mail and messages arrive they attach themselves to the people involved, across every channel you have connected, with the subject, the direction, and when it happened. Nothing gets filed by hand. That history has been sitting in your accounts the whole time, split across apps that each hold a slice of it and none of which will show you the whole thing.
The list itself is searchable, and you can filter it down to the accounts a person came from when you only want the people you email rather than everyone in a Slack workspace.
Stop searching your inbox for an address
Connect an account and the list builds itself from what is already there.
Get startedHand off a relationship with the history attached
Share a person with your team and they appear in a separate team view alongside your personal list. What your teammates get is the record: every address that person actually uses, the phone number that works, the job title that is current, and the notes you kept on them. When somebody goes on vacation or hands off an account, the next person starts from identity work that is already done.
What they do not get is your inbox. Activity on a shared contact is always read from the viewer’s own mail, so a teammate sees their history with that person and never yours. Sharing a contact does not share your threads with them. Notes are encrypted under dedicated keys in AWS KMS that only the application’s service roles can use, the same protection your message content gets.
A small proof of how the Brain is supposed to work
The Brain is built on a bet that knowledge which depends on people to maintain it will not stay current, so the maintenance has to come from the communication your team is already producing. Contacts is that bet running at small scale, on the easiest slice of it. Nobody keeps this list up. It follows the accounts, and when you correct something by hand your correction is the version that survives.
It also answers a problem every knowledge layer has on day one, which is that an empty one is worth nothing and filling it is a chore nobody signed up for. Contacts never starts empty. The people are already in the accounts you connected, so the list is populated before you have done anything, and the correspondence history arrives with them. Starting from something real and letting it correct itself is a very different proposition from starting from a blank page and promising to keep it fed.
A new contact can start an automation
Contacts is not a page you have to visit. A new person arriving is something your workflows can act on, and people are something they can read, write, and hand to an agent mid-run.
New contact as a trigger
A workflow can start the moment a person is created, whether you added them or a sync did. From there it branches on whatever you like, the same as any other trigger.
Write to the Brain
That trigger can create or update a page in the Brain for the person or the account they belong to, so a new name in your contacts becomes a place your team keeps what it knows about them.
Push into your system of record
Since workflows can call any connected MCP server, a new contact can be written straight into Salesforce, HubSpot, or whatever you actually run, without anyone retyping it.
Read, note, and share
Workflows can search your people or load a team’s, append a dated note to someone, and share a person with a team. Agent steps get the same abilities, and every change an agent makes is recorded so you can see what it did.
Where this is going
Contacts is worth having the day you connect an account, before you build a single workflow. Workflows are where it compounds, and that is the part we are extending now. Further out is a Brain that maintains itself from your communications without being told to, so an account page is current because your team talked to the customer and not because somebody built an automation for it. The people layer already works that way, and it is the first piece of this running in production. The rest is underway.
This is not a system of record
There are no deals here, no pipeline stages, no forecast, and no close dates, and we are not planning to add them. Salesforce and HubSpot keep their job. The way to think about Contacts is what your address book would be if it kept itself current and remembered your conversations. That sounds modest right up until you notice you do not have one.
Questions about Contacts
Do I have to import anything?
What happens when the same person is in two of my accounts?
Will syncing overwrite the edits I make?
Where does the activity history come from?
Is this a CRM?
Can a workflow do something when a contact is added?
Can my team see my contacts?
Stop searching your inbox for an address
Connect the accounts you already read your mail in, and the people you talk to arrive with their history attached. Free during beta, no credit card required.
Get started