Memory

How an agent remembers a contact across conversations, what has to be enabled first, and how to manage what is stored.

With memory enabled, an agent remembers durable facts about a contact between conversations — preferences, stated facts, events — and uses the relevant ones on future turns. A returning customer does not have to repeat themselves.

Without memory, every conversation starts fresh.

Three things must be true

Memory only runs when all three are in place. Turning on just one is not enough.

Your plan includes it. Memory is a paid feature — check the pricing page for which plan you need.
The agent has memory enabled — the agent's Settings tab, under Intelligence Layer.
The conversation is not excluded — some channels or sessions can opt out, which is how /reset on Telegram starts a genuinely clean conversation.

Set a business domain first

Before memory can be switched on, the agent needs a business domain selected in Settings. Memory extraction is domain-aware: the domain tells KlicForge what kinds of facts, entities and events are worth remembering for your business.

Until a domain is chosen, the memory toggle stays locked.

How it works

Memory is batch-driven, not per-turn, which keeps its cost predictable:

A conversation is queued for extraction only once it ends — either explicitly, or when it goes idle long enough to expire.
A background job reads ended conversations, extracts durable facts, and marks them so they are not processed twice.
Long-lived channels like Telegram and the widget enter the queue when their conversation expires on idle.

This means a fact a customer mentions will not be available in the same conversation's later turns as a memory — it is already in the conversation history for that. It becomes memory for next time.

Scopes

Each remembered fact has a scope:

Scope	Meaning
Organization	Applies across your whole workspace
Contact	Belongs to one contact
Session	Limited to a single conversation

Managing what is stored

Admins can view and edit what an agent remembers about someone from Contacts → (contact) → Memory: individual facts, how they relate to each other, session summaries, and a searchable graph.

Memory stores what customers tell your agent. Review it before enabling memory on an agent that handles sensitive information, and remember that a contact's memory is part of what you must produce or delete if they exercise a data request.

Cost

Extraction uses a model, and that usage is billed to your organization. The per-agent toggle is the real cost control — only agents with memory on cause any extraction at all.