Business

SaaS Customer Education Playbook: Onboarding, Activation, Support, and Expansion

Turn product knowledge into an explanation customers can act on. Golpo drafts from a help article or a recording, you review the script, and the video shows the concept in the real interface.

Golpo TeamJuly 18, 202611 min read

Turn your product knowledge into an explanation customers can act on. Show the concept, show it in the real interface, and point to the next task in one video. Golpo is built to be the complete AI explainer workflow for that job. Start from an idea, a help article, an approved script, or a recording of the flow. In Prompt Mode, Golpo drafts the narration, plans the scenes, designs the visuals, narrates, and syncs a finished video. Edit script before creating video is where you approve the words. Script Mode is how the click-path stays in the exact wording support already approved.

Quick answer

Pick one behavior the next onboarding cohort still fails: finish setup, invite a teammate, publish a first workflow, or recover from one error.
Bring the approved documentation page and a real screenshot or a short recording of that flow. Golpo drafts the mental model; your media shows the interface.
Approve the script, give each state change its own scene, and render. Then make one troubleshooting or role variant with the same saved style and voice.
Publish it in the product surface you already use, and measure task success, activation, or CSM reuse there.

Who it is for

This playbook is for product education, support, and customer success teams that already know which behavior predicts value. The obstacle is the gap between a correct help article and a customer who still cannot do the next step. A video earns its place when it explains the idea, shows the real screen, and names the action to take now.

Organize the program by lifecycle outcome. A library of polished tutorials is a catalog. The strategy is the behavior.

Map education to the lifecycle

Stage	Customer question	Useful asset	Measure
Onboarding	What should I do first?	Role-specific quick start	Setup completion
Activation	How do I reach first value?	Just-in-time explainer	Activation event
Support	How do I recover?	Issue-specific answer	Assisted resolution
Adoption	What should I use next?	Workflow explainer	Qualified feature use
Expansion	How can my team scale?	Admin and governance guide	Team adoption

Who owns the program

Product owns product truth. Support owns recurring friction. Customer success owns account context. Product education owns instructional design and governance. Marketing owns acquisition claims. One accountable program owner governs priorities, assets, measurement, and maintenance. For each asset, record source version, product area, audience, placement, owner, review date, and replacement status.

The feedback loop stays the same: ticket tags, search queries, onboarding drop-off, interviews, and product analytics; then one approved answer for a high-friction moment; then the smallest asset that can sit at that moment; then a look at exposure, behavior, resolution, and side effects. Unclear or inaccurate lines go back to the source owner.

Workflow: one doc and one recording

Follow this path for the next cohort’s stalled behavior. Use the documentation and the product media you already have.

Source. One approved documentation page for one job, plus a screenshot or a raw recording of the real flow. Paste or upload the page so Prompt Mode can draft from it. Uploading a source does not certify that the draft is accurate. Read it against the page.
Settings. Save a Custom Style from your product illustration, a brand frame, or a written description, and reuse it for every variant. Choose the voice. Insert the screenshot or UI clip with Own Media so the explanation is anchored to the interface customers actually see. A generated picture of a button is an illustration. Put layout notes in Video Instructions so they are not spoken. Select a duration that fits one job. Two minutes is a practical selection for a single workflow.
Script review. Turn on Edit script before creating video. Keep Prompt Mode for the first draft of the mental model: what the feature is for, and why the next click matters. Switch the task-critical steps to Script Mode so the spoken path matches the approved doc. Script Mode allows about 1,050 characters per selected minute. In the API, custom_script supplies that narration. enable_script_only_mode generates a script without a video, which is a different switch. With Custom Scenes, move sentence boundaries so each state transition has its own scene: invite sent, permission granted, workflow published. The map does not rewrite the narration.
Result. Render the onboarding video and review the frames against the documentation page and the screenshot. Button names, empty states, and the success state should match the product the customer will see.
One correction. When a label or callout is wrong and the spoken steps are right, use frame editing to change that visual. Frame editing does not change narration or audio. When the spoken step is wrong, revise the script and render again.
One reuse. Keep the Custom Style and the voice. Render a troubleshooting variant from the error-state article, with scene boundaries for the failed state and the recovery. An admin variant and an end-user variant share that identity and use different script objectives. A language version is a separate reviewed render.

Controls that make the explanation usable

Customers stall when the concept and the interface live in different places. These controls close that gap.

Draft, then lock the critical lines. Prompt Mode writes the first narration from the help article. Script Mode is for the steps a customer must hear exactly: a permission name, a warning, a required field. Both are professional paths. Serious teams do not have to hand-write every line before Golpo starts.
Real interface inside the explainer. Own Media (Business and higher, and Pay As You Go) inserts your images and video. Use the actual settings screen, the real empty state, or a short capture of the click path. If the raw recording should be the spoken track, use Own Narration (Business and higher, and Pay As You Go). The recording sets the duration and the spoken language. A language setting does not translate that audio. Audio-only upload does not create a face. Picture-in-Picture keeps a recorded speaker visible when you want the person in frame. See the picture-in-picture guide.
State transitions as scenes. Custom Scenes (Growth and higher, and Pay As You Go) let you split or combine scenes within the engine limit before generation. Give “request submitted” and “request approved” separate scenes so the customer can see the handoff. The saved map can be inspected later. It does not establish that the UI is current.
Labels from the script. On-screen text from script only (Canvas and Sketch) restricts generated labels to the script source. Golpo may show a subset of those words. In the API, set onscreen_text_from_script_only. Captions, when you need them, are a separate track you add in your player. Still read every label against the product.
One brand and one voice, two audiences. Custom Style is saved in My Styles and reused in Canvas or Sketch (Business and higher; API use also needs API access). It guides the look. It is not pixel-exact typography. Voice Instructions (Creator and higher, and Pay As You Go) set tone, pace, and pronunciation for generated narration. They do not clone a person. An authorized Voice Clone (Business and higher, and Pay As You Go) speaks new scripts in a saved voice. Use the same style and voice for the admin video and the end-user video, and change the script objective and the scene map.

A hypothetical permissions workflow

Picture a hypothetical project tool. New workspace administrators invite users and never create an approval workflow. Product analytics shows the drop-off after the invite. Interviews point to uncertainty about who can approve. Education has one approved permissions article and a raw recording of an admin creating the workflow.

Prompt Mode drafts a 2-minute onboarding narration from that article: what an approval workflow is, and why the invite alone does not route work. Script Mode carries the exact permission names. Own Media places the real permission screen and the success state into the explainer. Custom Scenes separate invite sent, permission granted, and workflow published. The team reviews the script, renders, and frame-edits any label that drifted from the screenshot.

The reuse is a troubleshooting variant for “the approver never sees the request,” plus an end-user variant that explains how to submit. Both use the saved Custom Style and voice. The admin cut keeps the permission wording. The end-user cut keeps the submit wording. Placement sits after the first invite, in the product surface the team already controls, with a link to the deeper article.

Measure workflow creation and permission-related tickets for people who saw the video and for a comparable group, in the analytics you already have. Expand placement when the behavior moves and errors do not rise. Treat that comparison as a test you run, and record the result in your own systems.

Plan, duration, and credits

A standard video uses 1 credit per selected minute. A 2-minute onboarding selection is 2 credits. The troubleshooting variant is another 2 credits at the same rate. Each reviewed language variant is its own render. On Pay As You Go, Edit script before creating video charges 10% after the script and 90% after the video. Frame editing charges the selected duration again for that version.

The combined path on this page — Custom Style, Own Media, and Own Narration or Voice Clone — is on Business and higher, and on Pay As You Go. Custom Scenes are on Growth and higher, and on Pay As You Go. Voice Instructions are on Creator and higher, and on Pay As You Go. Prompt Mode and script review are available across plans; length and controls vary. Confirm allowances on the pricing page. The Free plan is not a downloadable publishing workflow for customer education.

Review checklist

The script matches the current documentation page, and task-critical steps used Script Mode.
Screenshots and recordings are authorized and show the UI customers have now. Generated interfaces are illustrations.
On-screen labels were checked against the script and the product. Captions, if required, are a separate track.
Each state transition has the scene you intended. The scene map did not change the spoken steps.
Admin and end-user variants share the saved style and voice and teach different jobs.
The asset record names source version, audience, owner, placement, duration, and review date.
Hosting, in-product placement, analytics, and watching the source for changes happen in your application and your workflow. Golpo returns the video.

Frequently asked questions

What is SaaS customer education?

A governed program that helps a defined user perform the next valuable product behavior across onboarding, activation, support, adoption, and expansion.

Who owns customer education?

Ownership is cross-functional, and one accountable program owner governs priorities, assets, measurement, and maintenance. Product owns product truth; support owns recurring friction; customer success owns account context.

How is customer education measured?

Measure task success, activation, or customer-success reuse in the product analytics and support tools you already run. Connect exposure to the target behavior. A finished video does not establish the cause of a metric change.

Where should videos appear?

At the moment of need: inside onboarding, contextual help, support replies, the help center, a success program, or release communication. Hosting, in-product placement, analytics, and source-change monitoring stay in your application and workflow.

How does Golpo combine a product screenshot with the explanation?

Prompt Mode drafts narration from the approved help article. Own Media inserts the real screenshot or a short UI recording into the explainer. Script Mode keeps task-critical steps in your exact words. Custom Scenes give each state transition its own scene. A saved Custom Style and voice carry across the admin and end-user variants.

How many credits does a customer-education video use?

A standard video uses 1 credit per selected minute. A two-minute onboarding selection is 2 credits, and a two-minute troubleshooting variant is 2 more. On Pay As You Go, Edit script before creating video charges 10 percent after the script and 90 percent after the video. A frame edit is charged again on the selected duration of that version. Prices are on the Golpo pricing page.

Publish one explanation before the next cohort

Choose the behavior the next onboarding cohort still misses. Bring the documentation page and a recording or screenshot of that flow, review the script, and publish one contextual explanation where that moment already happens. Then measure task success, activation, or whether customer success reuses the video, in the systems you already have.

Create the onboarding explainer in Golpo · Compare plans and credits