> ## Documentation Index > Fetch the complete documentation index at: https://developers.autoplay.ai/llms.txt > Use this file to discover all available pages before exploring further. # Proactive onboarding with Autoplay > Help users reach value, recover from stalled workflows, and continue learning your product without replacing the tools already in your stack. Most onboarding gives every user the same tour and waits for them to ask for help. When someone gets stuck, they search through the product, open support, and explain what they already tried. Autoplay gives that journey context. It understands what the user is doing, compares their progress with the onboarding objective your team defines, and offers relevant help when progress stops. ## What changes for the user | Without Autoplay | With Autoplay | | --------------------------------------------- | --------------------------------------------------------------------- | | The user gets stuck without anyone noticing | Autoplay recognizes that progress has stopped | | The user explains what they already attempted | Their support agent can read the recent activity through Autoplay MCP | | Support shares generic documentation | The user receives help for the workflow they are completing | | The user searches around the interface | The relevant visual tour can open after the user accepts help | | Every visit starts from zero | Previous workflow progress informs what they can learn next | A user becomes stalled, Autoplay understands the onboarding objective, the user accepts help, completes the workflow, and can continue learning the product. ## What Autoplay enables Autoplay does not react to every click. It understands live activity in the context of the workflows users should learn and the segment they belong to. Turn recent product activity into context about what the user is trying to accomplish and what they already attempted. Compare behavior with successful and unsuccessful workflow signals to recognize completion, normal progress, stalls, and unfinished work. Stay quiet while the user progresses, then offer support at a configured moment while keeping the user in control. This can support a new customer completing initial setup, an existing user returning to an unfinished task, or a more experienced user learning an advanced capability. ## How you build the experience The four steps describe what your team provides, what Autoplay handles automatically, and how the experience improves over time. Connect the session replay provider that already captures what users do inside your product. Define what each segment should learn, what success looks like, and how the experience will be measured. Configure exploration gates, cooldowns, triggers, and the user-controlled path from a nudge to useful guidance. Use observed outcomes to improve onboarding and extend the same model into continual adoption. ## Autoplay works with your existing stack You do not need to replace the tools your team already uses. Each one keeps doing the job it is good at, while Autoplay provides the shared understanding and coordinates when help should be offered. | Tool | What it does | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | Session replay provider | Captures live user activity | | Autoplay MCP | Understands workflow progress, applies the proactive framework, and gives the support agent recent activity, next steps, and tour actions | | In-product prompt | Offers help and opens the existing support agent after the user clicks | | Existing support agent | Continues the conversation with context the user would otherwise repeat | | Existing tour provider | Delivers visual guidance after the user accepts it | Autoplay MCP sits between these tools as the intelligence layer. Your analytics platform still captures and measures behavior, your support agent still handles the conversation, and your tour provider still delivers visual guidance. ## Beyond initial onboarding The same workflows can help users keep learning after setup. Your team can define recurring tasks, advanced features, newly released capabilities, and role-specific journeys as additional adoption objectives. Autoplay remembers completed workflows, avoids repeating what users already know, and focuses guidance on unfinished or newly relevant outcomes. Over time, observed completion, stalls, segment performance, and accepted or dismissed offers can help your team refine the experience. See how Autoplay develops an up-to-date understanding of what each user is doing.