Records
People do not sit in one box, and the ones worth knowing least of all.
A consultant sits across four of your clients. A board member appears at two. The person who ran the evaluation at their last company just arrived at your biggest prospect.
A contact record that permits one employer loses all three relationships, and loses them silently.
Belonging
Many accounts, one of them primary, and the primary never dangles.
A contact links to as many accounts as the truth requires, with one marked primary for the sake of everything that needs a single answer.
The behaviours around that are the part that usually breaks. The first link becomes primary automatically, even if nobody asked. Setting a new primary clears the old one first. And unlinking the primary promotes the oldest remaining link rather than leaving a contact whose primary account points at nothing.
- A duplicate email refusal hands you the record —
Not a message. The existing contact's name, email, account and owner come back with the refusal, so the screen offers to open that one instead of making you go and search for it.
- And it can be overridden on purpose —
Because the same person with a second card at a second company is a real thing, not a mistake to be prevented.
- A name derives from its parts —
Give a first and last name and the full name is built. Give neither and the refusal says exactly that.
- Two statuses are excluded from bulk —
Do-not-contact, because it is consent-loaded and belongs in the consent flow rather than on a checkbox; and invalid, because it is a data-quality judgement made one record at a time.
Underneath
Every contact resolves to the same person the rest of the platform knows.
The same human who applied for a role two years ago, who is a contact at a client today, and who joins you as an employee next quarter is one record with three roles — not three records that happen to share a name.
Which is why enriching a contact, or capturing one from a profile page, tends to find something rather than create something.
- Applied for a roleMar 2024matched on priya.n@gmail.com
- Saved from a company profileNov 2024matched on profile URL, locale stripped
- Arrived on an inbound formFeb 2025matched on p.r.i.y.a.n@gmail.com — same address
- Became an employeeJun 2025matched on +44 7700 900 481
- Changes to a contact are marked as personal data —
In the audit trail, distinctly, so a privacy request can find what it needs to find rather than trawling everything.
- Enrichment fills gaps and never overwrites —
Every filled field is guarded on being empty first. A provider that returns something you already had does not win, and the search continues.
- Bulk reassignment tells you what it skipped —
Per contact, with the reason — not found, not permitted, already theirs. And every row is permission-checked again, so a bulk action cannot reach a record you could not open on your own.
- Capturing somebody from a profile page is idempotent —
Save the same person twice and you get the record you already had, told that it existed — rather than a second card to merge next quarter.
›What happens to a contact's timeline when they change company?
The contact keeps its history and gains a link to the new account. The person underneath is the same record, so what you knew about them does not restart.
›Does do-not-contact stop email being sent?
It marks the contact, and the marketing side of the platform enforces suppression properly. A rep-driven, one-to-one email is deliberately a different lane. If you need a hard block across every channel, set it through consent rather than relying on the status alone.
›Can a contact exist without an account?
Yes. A contact with no account is fine — though a deal needs one, so the new-deal button on an unlinked contact tells you to link it first.