Retell adds evolving contact memory for voice agents

Retell has introduced native Memory for its AI agents, replacing a workflow in which builders had to extract, store, and retrieve information between conversations. Turning the feature on creates an evolving brief for each contact, covering relevant preferences, past discussion, and unresolved follow-up. As new conversations take place, the brief is revised to carry forward useful context and remove resolved action items. Retell says the goal is to help a returning conversation continue from prior context rather than begin again.

Memory is linked to a contact in a Retell workspace. For agents configured to save it, an LLM analyzes completed phone calls or SMS chats associated with the contact’s phone number, using the transcript, existing Memory, and contact fields. A workspace prompt guides the system as it rewrites the running brief after each conversation. Retell distinguishes this from simply looking up stored fields or adding another call summary. Web calls and web chats do not automatically update contact Memory.

An agent can receive the brief at the start of a later conversation with the same contact, without loading the full transcript into its context. The settings for saving and using Memory are separate, so teams can choose whether an agent contributes to a brief, uses it, or does both. For AI builders, one important boundary is that Memory provides conversational history, not live information from connected systems; a retailer’s agent would still need an order lookup to confirm a package’s shipment status. In conversation flows, selected nodes can be set to skip when information in Memory or the current call meets the node’s transition condition. If required information is missing, the agent asks for it, and steps requiring confirmation during the current call should remain in the flow.

Builders can configure which agents save Memory and which receive it when a contact returns, as well as which flow nodes may be skipped. The brief can be reviewed, edited, or cleared in Contacts, while a workspace-wide prompt controls what future updates retain. Retell says access to that prompt is governed by workspace permissions, with CRM view permission needed to read it and CRM edit permission plus permission to edit the agent needed to change it. Memory also works with configured storage and PII redaction settings; when storage excludes PII, the brief is generated from a redacted transcript. For builders, these controls define how contact context can carry across conversations while leaving teams in charge of what is saved and used.