The problem with live onboarding calls
Scheduled onboarding calls have two problems. The first is that they do not scale. Every new customer needs a slot on someone's calendar, and the CS team's capacity is the ceiling on how many customers can activate in any given week.
The second problem is timing. A 30-minute call scheduled for Tuesday does not help the customer who signed up on Friday evening and is trying to figure out the product right now. By Tuesday, they have either figured it out themselves or lost interest.
Why a video bubble works
A video bubble is a short, narrated walkthrough that appears inside your product at the moment the customer needs it. It fires on first login, on a specific page visit, or when a product event indicates the user is stuck. The video shows a real person (or AI avatar) narrating over the actual UI, with a cursor pointing at the elements being discussed.
This works because it combines the human quality of a live call with the availability of documentation. The customer gets guidance that feels personal and contextual, at the exact moment they need it, without waiting for a calendar slot.
What to measure
The metrics that matter are not views or completion rates in isolation. What you want to know is whether the bubble changed behavior. Did users who watched the onboarding video activate faster than those who did not? Did they complete more key actions in their first session? Did they retain better at day 7 and day 30?
The right way to evaluate this is to track bubble engagement alongside product analytics. They can attribute a specific onboarding video to a measurable lift in activation, and use that data to decide which videos to create next.
Getting it right
Keep each video under 60 seconds. Focus on one action per video rather than trying to cover the entire product. Trigger based on context (first session, specific page, specific event) rather than showing every user the same sequence.
The goal is not to replace all human interaction. It is to handle the repeatable explanations so your CS team can spend their time on the conversations that actually require a human: expansion strategy, technical integration, and account planning.