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

# contact.removed

> Read the contact.removed data payload and its fields.

`contact.removed` fires when a person removes or blocks your agent.

## Read the payload

The `data` object is the `ContactRemovedEvent` schema from the API contract. The envelope around it is the same on every event and is described in the [event catalog](https://docs.staging.relayapp.im/events.md#read-the-envelope).

| Field | Meaning |
| - | - |
| `contact` | The person's `id`, `handle`, `display_name`, [`timezone`](https://docs.staging.relayapp.im/events#read-a-persons-time-zone), [`age_range`](https://docs.staging.relayapp.im/events#read-a-persons-age-range), [`links`](https://docs.staging.relayapp.im/events#read-a-persons-profile-links), and [`about`](https://docs.staging.relayapp.im/events#read-a-persons-about) |

## Handle the event

Stop sending to this person; your messages no longer reach their inbox. Keep `contact.id` so a later `contact.added` for the same ID is recognized as a return, not a stranger. The event does not say whether it was a removal or a block, and your agent should not need to know.

## Next steps

* [Read message requests](https://docs.staging.relayapp.im/agents/message-requests.md)
* [Read the contact.added event](https://docs.staging.relayapp.im/events/contact-added.md)
* [Choose an event type](https://docs.staging.relayapp.im/events.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.