← Latest news
Voice AI3 min read

Retell AI adds memory between conversations for voice agents

Retell Memory retains context across repeat contacts. We examine how to test a new-order scenario when a customer changes delivery instructions.

Abstract illustration showing two systems. The left system processes a blue bar with a building icon and emits sound waves. The right system processes wavy blue data, interacts with a document icon, and stores data in a database cube.
Editorial illustration

Context for the next call

On October 8, 2026, Retell AI introduced Memory for voice agents. It maintains a brief for each contact, with separate settings for saving and using that context. Completed phone calls and SMS chats update the brief when saving is enabled. Web calls and web chats do not update it automatically.

EDITORIAL PERSPECTIVES

What this means in practice

A practical scenario: two orders from one customer

An online store could begin by testing a repeat inquiry. Suppose a customer asked for their first order to be delivered to the office yesterday and calls about a second order today. In this scenario, the stored preference should prompt an address check, rather than being carried over to another purchase without confirmation.

The team needs to distinguish order-specific instructions from a customer's general preferences. A request for an evening callback, for example, may apply only once. The acceptance criterion is concrete: the agent confirms the current preference for the correct order, and the integration records the agreed response.

How to test the integration

Create a test customer with two different orders. Change the delivery instructions in the first conversation, then provide a different address in the second and check which order receives the change. Compare what the customer said, the conversation brief, and the record in the store's test system. This can reveal an old preference being carried over to a new order.

Define the source of current status separately: the workflow should query the order system during the inquiry. Before confirmation is complete, irreversible actions should not rely solely on a previous conversation. Assess the pilot by whether it selects the right order and records the correct changes, separately from how smoothly the agent speaks.

Checks for a repeat inquiry

  1. Separate lasting preferences from instructions for a single order.
  2. Test a new address after an earlier request for office delivery.
  3. Compare the customer's confirmation with the update in the test system.
  4. Test what happens when a customer cancels an earlier preference.

Questions and answers

Is a previous conversation enough to change delivery?

In the proposed workflow, the team should require confirmation of the current order and new instructions before recording changes.

How should the pilot be assessed?

Check whether it selects the correct order and whether the recorded change matches the customer's latest confirmation. Evaluate conversational fluency separately.

Sources

VOICEIP / INTECRACY GROUP

From an update to a working scenario

Voice agents, telephony and integration with your business systems — using your own infrastructure or international platforms.

Explore our services ↗

Continue reading

All news ↗
VoiceIP · AI assistant

Let’s talk.

Ask about VoiceIP services and agents. Answers come from this website.

Ready when you are

Speak after the greeting. Your microphone stays on during the call. Up to 3 minutes.

You can speak or type. We can switch between Ukrainian and English.

Contact our team ↗

Google Gemini processes your messages and voice to respond. Privacy policy