A guided hand on your own website
Autopilot is Shinobi driving the visitor's browser like a patient guide: it moves to the real control on whatever page they are on, points, narrates the step and walks them through. Page-aware, and fully customizable per tenant. It is in build now, and this page will say so until the day it ships.
Show, not tell, on any page
Most help explains where the button is. Autopilot goes to the button.
It knows the page
Autopilot works from a map of your site's real controls, so it points at the actual button, field or link in front of the visitor, not a screenshot of one.
It moves, points and narrates
An on-screen guide travels to the control, spotlights it and explains the step, walking the visitor through the flow end to end, across page navigations.
Customizable per tenant
The flows, the wording and the look of the guide are defined per workspace, so it behaves like part of your site, not a plugin bolted on top of it.
Built careful before it was built clever
The engine enforces a hard rule: anything that creates, deletes or spends is point-only. Autopilot can point at those controls and explain them, but it never clicks them and never fills them. The person does. That rule is enforced by the engine at run time, not by authoring convention.
Where it is and where it goes
Autopilot is on the Workspace roadmap with the same rule as everything else there: named, scoped, no fake toggles. This page updates the day each piece ships, not before.
The first surface: Autopilot walks a new workspace owner through setup, pointing at the real fields and letting them commit the steps that matter. Typing is never consent. The button is. Built and rolling out in stages; it goes LIVE here the day the stages are done.
The same guide across the whole console, so anyone on your team can ask to be shown instead of told.
A map of your storefront, so Autopilot can guide your visitors through your pages: finding the right product, starting a return, checking an order.