Loading
A contact record is the single entry for one person your company deals with. It holds their role, contact details, the company or companies they work for, consent for each kind of email, and a timeline of every interaction any team has had with them — sales calls, support tickets, quotes, invoices and meetings. Every Treepie product reads and writes the same record, so there is no second copy to fall out of date.
Because a support desk, a billing system and a CRM each create their own copy. The same person then has three email preferences, two job titles and one very confused experience of your company.
A contact is one person: name, role, contact details, the company they belong to, what they have consented to, and every interaction recorded against them.
There is one contact row, referenced by every product rather than copied into it. A change of role or email is made once and is immediately true everywhere it is read.
A procurement lead at Kanaka Foods moves to Bexley Group. Reassigning the contact keeps their history against Kanaka Foods where it belongs, and starts a clean relationship at Bexley with the same person recognised.
It is not a personnel record. Employees live in Nest, and a person who is both a customer contact and an employee is deliberately two records with two different purposes.
Desk reads it to see who is raising a ticket, Books to address an invoice, Loop to name a client approver, and Growth to attribute a form fill to a known person.
| Inboxes & spreadsheets | Sales-only CRM | Treepie Flow | |
|---|---|---|---|
| Who can see the history | Whoever was copied in | Sales only | Every team with access |
| Support and billing activity | In other tools | In other tools | On the same timeline |
| Job changes | Lost when they leave | Old record goes stale | Old role ended, history kept on both companies |
| Consent | A column someone updates | One opt-in checkbox | Per purpose, dated, with source |
| Duplicates | Everywhere | Common after imports | Matched on entry, merged with both histories |
One primary company, with a recorded history of previous ones. Dual current roles are held as a relationship, not by duplicating the person.
Whoever has visibility of the records that history sits on. Permission is per record, not per product.
Mark them inactive. History stays, and sequences and marketing stop targeting them.
Name, role, email addresses, phone numbers, address, company links, owner, consent per purpose and any custom fields you add.
Email and calendar sync match messages and meetings to contacts by address and log them on the timeline automatically.
Yes. Every timeline item shows the product and person it came from, and the timeline can be filtered by team.
Anyone with access to the contact’s company, subject to your roles and record permissions. Sensitive fields can be restricted separately.
Yes. Contacts are imported into a sandbox, matched to companies and to each other, and checked before anyone logs in.
No. Flow is priced per user; the number of contacts you keep doesn’t change the price.
They can change their email preferences through the preference centre. Other details are updated by your team or by sync.
An admin can erase the person, removing their personal details while keeping anonymised activity so reports stay correct.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.