> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/inbox-and-leads/contacts.md).

# Contacts

The people who contact you, and what LimeCall knows about them.

Open **Contacts**.

A contact is a person. Every call, message and form submission attaches to one, so history follows the person rather than the channel.

## How contacts are created

Automatically, whenever someone new contacts you — a call to one of your numbers, an inbound message, or a widget submission. Matching is on phone number.

You can also add them manually, or import a list.

## What is stored

Name, phone, email, company, plus fields collected by your widget or assistant.

LimeCall also records behavioural detail: first seen, last seen, last call, which channels they use, and the campaign or source that brought them in.

## Enrichment

Optional lookups fill in what the caller did not tell you — name, company, line type, carrier, and rough location.

**Line type** is the most immediately useful. Knowing a number is a mobile, a landline or a VoIP number tells you whether texting will work and is a reasonable spam signal.

Enable providers under **Settings → Enrichment**. Enrichment is an add-on with its own costs — see [Usage & credits](/account/usage-and-credits.md).

{% hint style="info" %}
Enrichment is a lookup against third-party data, so it is neither complete nor always current. Treat it as a hint, not a fact — and check whether your privacy notice covers it.
{% endhint %}

## Caller memory

Enrichment and history are what let the AI receptionist recognise a returning caller. See [Caller memory](/ai-receptionist/caller-memory.md).

## Importing

Import contacts from CSV. Match your columns to LimeCall's fields during the import.

Before importing:

* **Normalise phone numbers** to international format where you can. It substantially improves matching.
* **Deduplicate** first — cleaning a list before import is far easier than merging afterwards.
* **Check your legal basis** for the data, particularly if you intend to message them.

## Duplicates

Contacts are matched on phone number, so the same person contacting from two different numbers creates two records. Merge them to keep one history.

## Blocking

Block a contact from their record. Blocked contacts do not reach your AI receptionist. See [Spam & blocking](/ai-receptionist/spam-and-blocking.md).

## Contacts and leads

A contact is a person; a lead is an opportunity. The same contact can generate several leads over time — someone who enquired last year and again this year is one contact with two leads.

See [Leads & scoring](/inbox-and-leads/leads-and-scoring.md).

## Syncing to your CRM

Where a CRM is connected, contacts sync to it. See [Integrations](/integrations.md).

## Deleting

You can delete a contact and its associated data. If you are subject to GDPR or similar, this is how you honour an erasure request — note it also removes the call history and recordings attached to that person.