Why This Step?

1 min read

Why this step?

Your copilot needs two things to personalise effectively: a live feed of what the user is doing right now, and a memory of what they've done before. This step connects both.

Autoplay integrates with any copilot — whether you're using Intercom, Dify, Botpress, or your own custom-built solution. See the setup recipes to get connected.

What you're connecting

Real-time events — stream live user actions into your copilot via the SDK, so it always knows where the user is and what they're doing in the product right now.

User memory — structured per-user memory built from Atlas session labels, giving your copilot the full history of what each user has and hasn't completed. Currently in beta — request access to connect it alongside real-time events.

Did this answer your question?