You're on a customer's website. They ask a question in the embedded chat widget. Then they click to another page. The chat loads again, and the agent—or AI—has no memory of the previous question. The customer repeats themselves. Frustration spikes. This scenario plays out thousands of times a day across Intercom, Drift, and dozens of other platforms. But why does context disappear, and more importantly, which tools actually preserve it? We ran a systematic test across three platforms: Intercom, Drift, and Orin's embedded AI chat widget . We measured context retention across three critical moments: mid-page navigation, after a time gap (we tested 30 minutes and 2 hours), and during handoff from AI to live agent. The results expose a real problem that most vendors don't talk about. The three places context dies Context loss isn't random. It happens in predictable places, and understanding why helps you choose the right tool. 1. Page navigation within the same session A customer is on your pricing page. They ask, "Does this plan include API access?" in the chat. They click through to the features page. The chat widget reloads. Does the new page have access to the previous message? Most don't—not reliably. Intercom: Context persists if the customer is logged in via their identity API and the widget is configured to track visitor data. Without explicit setup, each page view is treated as a new session state. We saw context survive 7 out of 10 page transitions in our test. Drift: Drift maintains conversation history across page navigation if you've enabled the "Conversation Persistence" setting and configured Drift's tracking code correctly. When configured, it performs reliably. Unconfigured, context vanishes. We saw 9 out of 10 page transitions preserve context with proper setup, 2 out of 10 without it. Orin: Context persistence is built into the default widget behavior—no extra configuration needed. The widget stores conversation state client-side and syncs to CRM records server-side, so context follows the customer across pages. We saw 10 out of 10 page transitions preserve context. However, this advantage only matters if your CRM data is clean; if visitor records aren't linked correctly, handoff fails downstream. 2. Time gaps (30 minutes to 2 hours) A customer chats with your AI widget on mobile, then sets the phone down. They come back 90 minutes later on a desktop to continue. Does the chat widget remember the original conversation, or does it treat them as a new visitor? Intercom: If the customer is logged in (via email or custom user ID), the conversation persists across devices and time. If they're anonymous, conversation history clears after 24 hours of inactivity. In our test, an anonymous visitor lost context after 2 hours; a logged-in visitor retained full history after 72 hours offline. The gap is stark. Drift: Drift stores conversations in their database indefinitely, but retrieval depends on device fingerprinting and email recognition. We tested a scenario where a customer returned on a different device 2 hours later. The widget recognized the visitor 6 out of 10 times. Without explicit email capture on first visit, context often fails to surface. Orin: If the customer is identified in your CRM (via email or phone), context syncs instantly when they return. If they're anonymous, the conversation is tied to a temporary session ID that expires after 30 minutes of inactivity. We tested returning after 2 hours: anonymous visitors lost context; identified visitors retained full history. This mirrors Intercom's model but with a shorter anonymous window. 3. Handoff from AI to live agent This is the most critical moment—and where context loss causes real damage. A customer asks your AI a question, the AI decides it can't handle it, and hands off to a live agent. Does the agent see the full conversation, or just the current message? Intercom: Context transfers to the live agent inbox reliably. The agent sees the full conversation thread, customer attributes (name, email, company, custom fields), and previous interactions. However, if your CRM data isn't synced to Intercom via API, the agent only sees Intercom-native data. We tested a handoff with a customer who had a linked HubSpot record: Intercom displayed only Intercom fields, not HubSpot data. The sync gap forced the agent to open a separate tab. Drift: Drift's handoff transfers conversation history to live agents in their interface. We saw full message history appear 9 out of 10 times. However, Drift doesn't natively pull CRM data into the agent view—you have to manually build a Zapier integration or use Drift's limited CRM connectors. A handoff without customer context from your CRM still requires the agent to dig. In our test, a live agent received the chat history but had to ask the customer to repeat their name and company because that data wasn't passed from Drift's fields. Orin: Since the chat widget is built into a unified CRM, handoff means t