Contacts that hold the whole relationship.
In TAO a contact is a living operational record: every thread, every job, every invoice, every workflow run. Your team sees the same record. The next conversation starts where the last one ended.
What lives on a contact record
A TAO contact is more than a name and email. It is the customer’s history with your business, kept tidy by everyone who touches it.
- Threads, tasks, calendar events, invoices, workflow runs — all in one place.
- Multiple people per company; relationships modelled honestly.
- Provider sync with Google Contacts and Microsoft 365 contacts.
- Each contact has explicit consent and data-retention controls.
How Andy uses contact context
Andy reads the contact’s full record before drafting anything that involves them. No more “sorry, who is this?” moments when a colleague picks up the thread.
- Drafts that reference past commitments without re-asking.
- Surfaces the right historical detail for each new conversation.
- Recommends the right person on your team for the next step.
How the company brain feeds it
Every interaction enriches the contact record automatically — without anyone having to remember to update a CRM. The brain is the CRM, and it updates itself.
- Each thread and meeting updates the relationship state.
- Preferences and constraints accumulate without manual entry.
- Disconnect any provider and the local record stays with you.
For technical readers
The contacts module exposes the same operational record to every other module — so a change here ripples into the relevant workflow, contact, and Andy context automatically. All writes back to providers (where applicable) go through the Approvals queue unless an operator-defined auto-approve rule applies.
Want to see this running on the apps you already use? Apply for the beta, or tell us what your team is trying to run from one place.

