Keep Customer Conversation History Inside the Right Identity Boundaries

Voice assistant customer history identity needs more precision than “we recognize this number.” A shared phone can represent several people, and the same person may contact different business units or use different numbers.

Useful continuity begins with clear record boundaries. It should help the right conversation resume without treating every matching detail as permission to reveal everything the business knows.

Distinguish the thread from shared context

Burki's SMS threads are scoped to the assistant, business sender and customer phone within the tenant. This helps keep separate business conversations from collapsing into one inbox thread.

Optional later-call continuity has its own bounded rule: eligible recent committed history for the same tenant, assistant and customer phone. Do not assume that thread grouping and restored context are identical concepts or that changing a sender is an identity-verification mechanism.

The voice/SMS guide explains the broader continuity goal. Current settings and implementation boundaries determine the exact history available to a particular assistant.

Normalize a number without overinterpreting it

International formatting helps systems compare telephone destinations consistently. Twilio's E.164 reference explains the format. Consistent formatting does not prove that the current caller is the person who used the number previously.

A business line may be shared. A family member may answer a phone. A caller may give a different number for follow-up. Keep number normalization separate from the business's procedure for verifying identity or disclosing sensitive information.

Do not infer that a changed number belongs to the same person simply because the caller gives a familiar name. Likewise, do not expose past details to help an unknown caller guess which record they want.

A hypothetical shared office phone

Imagine two employees calling from the same office number about different service requests. The second caller should not automatically hear a detailed recap of the first person's conversation.

A neutral opening such as “How can I help today?” may be more appropriate than volunteering the previous issue. If context is relevant, ask a limited clarifying question without disclosing unnecessary details.

This hypothetical example shows why personalization should be proportionate to the task. Recognizing a phone number can reduce repetition, but it should not turn into an announcement of every recent interaction associated with that number.

Preserve assistant and workspace boundaries

Different assistants may serve different business purposes. A scheduling assistant and a general-information assistant should not be assumed to share all context merely because they belong to the same organization.

The same applies more strongly across tenants. A person calling two businesses on the platform should not carry one business's private conversation into the other. Treat tenant ownership as a fundamental boundary, not a display filter.

When reviewing a configuration change, ask which assistant owns the history and whether the new workflow should use it. Moving a phone number or changing an assistant assignment is not a reason to rewrite historical ownership casually.

Make stale or absent history a normal case

Burki's current shared continuity is limited to recent committed turns, and WhatsApp history remains separate. An assistant may legitimately have no eligible context even when staff can find an older record elsewhere.

The assistant should ask the caller for the information it needs rather than pretend to remember. It should also accept corrections to restored context. A recent request can become outdated without any system failure.

Current retention and redaction settings apply. Do not promise permanent memory or automatic reconstruction of historical gaps. The AI receptionist guide can help frame a useful conversation without relying on those claims.

Before enabling context-aware greetings, review a shared number, a different assistant, an older conversation and a caller changing their request. Ask whether the assistant reveals only what is needed and whether the caller can redirect it easily. The goal is appropriate continuity inside clear boundaries, not maximum recall.