# Patterns: signals that repeat, with the proof behind each one | Niadra

> Repetitions across conversations, events and actions, found by a written rule, with the evidence, an expiry date and the same access rule as facts. Sensitive categories never become a pattern.

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

Patterns

# What repeats becomes a signal, with the proof behind each one.

A pattern is not something the customer said. It is a repetition across conversations, events and actions, found by a written rule, with the parameters you set. Every pattern points to the records that support it, applies for a set period and goes through the same access rule as the facts. The agent adjusts what it offers before the first word, and your company can explain where each signal came from.

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

## How it works

Pattern foundexample

Third complaint about a technician visit in 90 days

Rule

Recurring complaint, version 3: three complaints on the same subject in 90 days

Evidence

-   Aug 4, 2026 · AppThe technician visit ran three hours late.
-   Aug 29, 2026 · WhatsAppThe technician came without the part. Visit rescheduled.
-   Sep 22, 2026 · PhoneThe technician never showed up.

Valid until

Nov 2, 2026

Reaches

-   Support receives it
-   Billing does not: its purpose does not allow it

-   A written rule, never a model’s guess: subject, count and window, with the parameters you set
-   Every pattern points to the records that support it
-   It expires at the end of its period and leaves the context on its own
-   Same access rule as the facts: each agent receives only what its purpose allows
-   A sensitive category never becomes a pattern: health, religion, politics, origin, sex life, union membership, biometrics and genetics
-   Before a rule goes live, you see how many customers it would have flagged in the last 90 days. A wrong pattern comes off in one click

## 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)
-   [IdentityPeople, companies and partners, recognized on any channel.](/en/produtos/identidade)
-   PatternsYou are hereWhat repeats, with the proof behind each signal.

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)