# Identity: the same customer on every channel and system | Niadra

> Phone, email, ID number, login and each system’s ID become one customer, each identifier with its own weight. Merges are reversible, and companies and partners are recognized too.

URL: https://niadra.com/en/produtos/identidade

Identity

# People, companies and partners, recognized on any channel and system.

Every identifier comes in with its source and its weight: phone, email, ID number, app login and the customer’s ID in each system. Niadra merges what belongs to the same person only on a strong signal, and every merge can be undone. The customer can also be a company: an account is the company that buys from you, and a partner is an organization that takes part without being a customer, such as the carrier. Each person is linked to the organization by their role.

[Talk to us](/en/enterprise)[Read the docs(opens docs.niadra.com)](https://docs.niadra.com/en/concepts/identity)

## How it works

### Each identifier carries a weight

example

+•• •• ••••• 0000hintthe number may have a new owner

ID number •••••6789statedthe person said it on the call

marina@•••.comverifiedconfirmed with a code sent by email

App login 88213authenticatedsigned in with a password

CRM customer 48213from a systemcame from the company’s own records

Every piece of information stays linked to the identifier it came from. If two people are merged by mistake, Niadra splits them without losing the history of either.

### People linked to organizations

example

-   Ana ReedbuyerA supermarket chainaccountsince Mar 2025 · from the CRM
-   Luis MatadriverA carrierpartnersince Jan 2026 · from the transport system
-   Luis MatadriverAnother carrierpartneruntil Dec 2025 · stated on a call

Companies never merge on their own: only through the company’s registration or a system ID. An email domain is a hint, never proof.

-   Five verification levels: the context changes with how much the conversation has proven who the person is
-   A phone number is a hint, not proof: it may have a new owner
-   Test and sample values never merge anyone
-   Each system’s ID becomes an identifier, with the system’s name attached
-   One person can be linked to several organizations at once, each link with a role and a validity period

## One memory, nine products

Connect

What goes into the memory

-   [SystemsThe events your systems already emit, tied to the right customer.](/en/produtos/sistemas)

SDK, API and MCP

Any agent connects to the memory with three calls, in Python, TypeScript, HTTP or MCP.

[See the documentation(opens docs.niadra.com)](https://docs.niadra.com/en)

Remember

What the memory knows

-   [MemoryWhat was said and done, with a date, a source and evidence.](/en/produtos/memoria)
-   IdentityYou are herePeople, companies and partners, recognized on any channel.
-   [PatternsWhat repeats, with the proof behind each signal.](/en/produtos/padroes)

Deliver

What each agent receives

-   [ContextWhat each agent needs to know before it starts.](/en/produtos/contexto)
-   [HistoryEverything that ever happened, for the agent to search.](/en/produtos/historico)
-   [AlertsA signed webhook when one of your rules fires.](/en/produtos/avisos)

Govern

What your team controls

-   [MeasurementWhether each agent used the context it received.](/en/produtos/medicao)
-   [ConsoleWho read what, review, export and erasure.](/en/produtos/console)