Customer memory in voice AI: scope, corrections and identity

Remembering a detail can save a caller repetition. Remembering the wrong detail, or revealing it to the wrong person, can make the experience worse. A memory feature needs scope, identity, correction and retention rules as well as retrieval.

Distinguish three sources of context

An assistant may use the current conversation, permitted historical context or an authoritative business-system lookup. These sources can disagree. A caller's earlier preference is not necessarily current, and a transcript summary is not the same as a verified account record.

Burki's LiveKit context restoration is scoped and bounded. Depending on configuration and budget, some historical information may not be restored. Do not promise perfect recall or that every previous call and message will be present.

Test who the memory belongs to

Use fictional callers and verify that a detail saved for one caller does not appear for another or another workspace. Shared or reassigned telephone numbers need careful handling. Caller ID alone should not authorize sensitive disclosure.

Ask how a caller can correct a detail and how the next conversation distinguishes the current statement from an older one. If the value is uncertain, the assistant should confirm it instead of presenting it as established fact.

Keep remembered facts proportionate

Store only information justified by the intended service and configured policy. Do not infer personal circumstances from voice, emotion or incidental remarks. A larger memory history is not automatically better; stale or irrelevant context can distract the assistant.

Review who can inspect or change records and how applicable retention/deletion processes affect future retrieval. A deleted transcript and a removed derived memory may be separate operations that need verification.

Evaluate the caller experience

A useful test is: state a fictional callback preference, correct it, begin an eligible later session and inspect the restored context and response. Add a different caller and an unavailable-memory case. The assistant should still handle the current request when historical context is absent.

Use the knowledge guide to keep customer statements separate from approved business facts. Memory helps continuity only when the information is appropriate, accurate and actually available for the selected session.