Why do I need Atlas for my proactive visual copilot?
Your copilot is only as good as the data behind it. At every moment, it needs to know exactly what each user has done, what they haven't, and where they're likely to need guidance next.
Atlas provides that foundation. It continuously labels each user's sessions by workflow and completion rate — giving your copilot the real-time signal it needs to understand intent, avoid telling users what they already know, and surface the workflows they haven't discovered yet.
This is why real-time events alone aren't enough. Events tell your copilot what a user is doing right now — but without the history of what they've already mastered, your copilot risks suggesting something they've long since figured out. Atlas gives it the full picture: not just the present moment, but everything that came before it.
Your copilot also needs to know where in the product the user currently is. That's why, alongside Atlas, you'll need the Autoplay SDK — it pulls in contextual user memory based on the user's current location in the product, so your copilot can respond to the right moment with the right guidance.
Without both, your copilot is guessing. With them, every interaction is grounded in who that specific user is and what they've actually done.
Atlas also gives you the tool to evaluate your copilot over time. As it guides users, you can measure its impact by tracking how workflow completion rates change — if users are completing more of your key workflows at a higher rate, your copilot is working.
The goal is to move every user closer to the golden path: the sequence of workflows that defines a fully activated, high-value user of your product.
