---
title: "Contacts"
url: "/contacts"
description: "The people your agents talk to — how they are identified, how their personal data is protected, and what you can do with their records."
productArea: contacts
audience: ["business-user", "admin"]
tags: ["contacts", "privacy"]
lastReviewed: 2026-08-25
---

# Contacts (/contacts)





A contact is a person who talks to one of your agents. KlicForge creates a contact record the
first time someone starts a conversation, and links their later conversations to it. Sending an
[audience message](/scheduled-tasks/audience-messages) can also create the record — a recipient
gets a contact the moment you message them, before they've said anything back.

Find them under **Developer → Contacts** in the dashboard.

## How a contact is identified [#how-a-contact-is-identified]

Identity depends on the channel:

| Channel                            | Identified by                                          |
| ---------------------------------- | ------------------------------------------------------ |
| [Web widget](/channels/web-widget) | An anonymous identifier, or an `externalId` you supply |
| [Telegram](/channels/telegram)     | Their Telegram user ID                                 |
| [WhatsApp](/channels/whatsapp)     | Their WhatsApp number                                  |

A contact starts anonymous and becomes identified when it learns something identifying — a name
or email the person gives during conversation, or an `externalId` you pass in from your own
system when you already know who they are.

## Personal data [#personal-data]

<Callout type="info">
  Contact names, email addresses, phone numbers and messaging identifiers are encrypted at rest.
  They are masked in the dashboard and revealed only through an explicit, audited action.
</Callout>

Personal fields are also redacted automatically from audit logs.

## What is on a contact record [#what-is-on-a-contact-record]

* Identity and contact details, as far as they are known
* Conversation history across every channel
* [Memory](/memory), if enabled — what the agent remembers about them
* Category and tags you assign
* Any [data table](/data-tables) records linked to them

## Controlling what an agent can see [#controlling-what-an-agent-can-see]

An agent's access to contact information is governed by the tools and
[data table permissions](/data-tables#permissions) you grant it.

For public-facing agents, the safe pattern is to let the agent **write** personal data — so it
can capture a name or email during conversation — while blocking it from **reading** those
fields back. That way a stranger cannot ask your agent to recite someone else's details.

## Data requests [#data-requests]

You can export everything held about a contact, which is what you need when someone exercises a
right of access. Deletion requests are handled the same way.

<Callout type="warn">
  A contact's exported data includes their conversation history and their memory. Review what an
  export contains before sending it.
</Callout>

## Related pages [#related-pages]

* [Memory](/memory)
* [Data tables](/data-tables)
* [Channels](/channels)
* [Security and privacy](/organization/security-and-privacy)