The first session sets the slope of the whole account: done well, it converts signup enthusiasm into a working configuration and a plan; done badly, it's a product tour with a calendar invite. Here's the anatomy of a great AI-led first session, minute by minute, and the design choices that make it work.
Minutes 0-3: The goal, not the tour
The session opens with a question, not a feature: what are you trying to get done? The user's answer sets everything, the plan, the vocabulary, what gets skipped. If the account arrived through a demo, the agent already knows the use case and confirms rather than re-asks, context carried forward is the first trust signal. The anti-pattern to design out: opening with the product's story instead of the customer's, which converts a working session into a lecture in the first minute.
Minutes 3-6: The plan, out loud
The agent proposes the shape of the first week: what today's session will accomplish, what waits for session two, where the finish line is ("by Friday your team should be running X on your own data"). Saying the plan out loud does two jobs: it sets expectations the agent will be held to, and it converts onboarding from an event into a program in the user's mind. This is the agenda made visible, and it's what separates a session from a help widget with a greeting.
Minutes 6-13: The first real configuration, together
The heart of the session is doing, not showing: the first integration connected, the workspace seeded, the first workflow run, on the user's own screen, with the agent filling what it can and asking for what it can't. One real thing completed beats five things demonstrated; the user should end this stretch with something that exists because of the session. The agent's perception carries the load here, it sees what's already configured, catches the malformed field before it fails, and never asks the user to describe what it can look at.
Minutes 13-15: The close that opens the next session
Great first sessions end with three sentences: what got done, what's next, and when, with session two proposed while momentum is warm. The plan's continuity is the promise being made: session two will begin where this ended, no recap, no re-explaining. Then the summary lands on the account record, so the whole team, human and agent, knows where this customer is. (Disclosure: this anatomy is how we designed Skippr's onboarding agent's kickoff; steal the structure regardless of what runs it.)
Questions buyers actually ask
How long should the first session be?
Around fifteen minutes: long enough to configure something real, short enough to respect signup-day attention. Depth belongs to the plan, not the first sitting.
What if the user just wants to explore alone?
The agent offers the plan and steps back, availability without insistence, and catches the stall later if exploration doesn't convert to progress.
Voice or text?
Voice-first with text fallback: setup conversations carry a lot of back-and-forth, and speech moves it faster for most users.
Watch it onboard someone
Onboarding either happens on the user's own screen or it does not happen. Fifteen minutes is enough to see which one you are buying.