> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zudo.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Contacts

> The people at your customer accounts — synced from your integrations, enriched by email and meetings, and used to tell whether anyone is actually engaging.

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

| Source                                                               | What it creates                                                   |
| -------------------------------------------------------------------- | ----------------------------------------------------------------- |
| [Vitally](/integrations/vitally)                                     | Contacts on each synced account, with their platform traits       |
| [Gmail](/integrations/gmail) / [Help Scout](/integrations/helpscout) | A contact for each external participant on a thread               |
| [Fireflies](/integrations/fireflies)                                 | Meeting attendees, matched to existing contacts by email          |
| [Segment](/integrations/segment) / [PostHog](/integrations/posthog)  | People seen in `identify` calls, linked to the account by `group` |
| Manual                                                               | Anyone you add yourself                                           |

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](/accounts/health-scoring). 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](/settings/health-score-config) 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](https://zudo.so/api/v1/docs#GET--contacts) 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.

<Note>
  A contact's email address is the identity key. Changing it is not supported — remove the contact and add the new
  address, or the history of two different people merges into one record.
</Note>