Contacts

A contact is a person at one of your accounts. Contacts arrive from your connected platforms, from the email threads Zudo reads, and from meeting attendee lists — and they are how Zudo answers the question behind most churn: is anyone still talking to us?

​

Where contacts come from

Contacts are matched on email address, so the same person arriving from two sources stays one contact rather than becoming two.

​

Last seen

Each contact carries a last seen date — the most recent time Zudo saw evidence of them: an email, a meeting, or a product event. This matters more than it looks. The newest last-seen date across an account’s contacts becomes that account’s contact activity, which is one of the factors in its health score. An account where every contact went quiet three months ago scores worse than one where someone replied yesterday, without anyone having to notice and log it. You can override the date on an account directly — see health score configuration for when that is the right move.

​

Contacts on an account

An account page lists its contacts with their role, email, last-seen date, and any traits their source supplied. From there you can:

• Add a contact manually, when someone joins the account mid-relationship
• Remove a contact from an account when they leave, without deleting the person record
• See their product traits — anything a product event carried about that individual, as opposed to the account

​

Contacts and the API

Contacts are fully available over the API and MCP: list and filter them, create them, and update a contact’s last-seen date. Updating last seen is the one write that changes a health score, so it is the one worth wiring into an integration if your product knows about activity Zudo cannot see.