A product tour points at things and asks the customer to do them. A co-browse tour does them: it clicks through the interface and fills in fields while the person watches, with each click marked so it's clear what just happened. It's the closest thing to sitting next to someone and taking the mouse. Co-browse tours run on websites and web apps with the Gleap JavaScript SDK. Outreach is available on the Team plan and up.
Go to Outreach → Co-browse and click Create co-browse tour.
Pick Blank co-browse tour or a starter such as Guided setup.
Under Visual editor, enter the Website where the tour starts and click Open editor.
Go to the starting page and click Start tour here.
Add steps with Add pointer (click the element on your page) or Centered message, and choose how each step moves on.
For a click step, choose Click on the element: the editor's Save step & trigger click performs the click so you can carry on to the next screen.
For a field, choose Text input, then Automatically fill in the text and enter the Text to fill in.
Click Save & close, set the Co-browse options, then Continue, Targeting and Launch.
Allow dismiss: lets the customer stop the tour.
Background glow: a glow around the page while the tour runs, so it's clear something is happening.
Read text aloud: narrates each step with the Voice you pick. Browsers often start muted, so Unmute modal offers to turn the sound on.
Joined indicator position: where the “joined” indicator sits on the page.
Like product tours, a co-browse tour can be offered by Kai: keep Kai Support suggestions on under Use in AI bot and write a clear Description. See Let Kai start a product tour.
Use a co-browse tour when the doing is the hard part: a configuration across several screens, a setting buried three levels down, a form whose fields need particular values. Use a normal tour when the point is for the customer to learn where things are. A co-browse tour completes the task; it doesn't necessarily teach anyone to repeat it.
Each step finds its element by a selector. Interfaces that generate element identifiers fresh on each render can leave a step unable to find its target later. Give the elements a tour depends on stable identifiers of your own, such as a data- attribute, and re-run your co-browse tours after frontend changes. If the editor never connects, the causes are the same as for a product tour: see Build a product tour.
One task per tour. It should run when someone is stuck on exactly that, not as a general introduction.
