Prism

Customer Education & Enablement

Prism Customer Success Handbook — Section 2.9

Why this matters more here than at most companies

SMB accounts have no standing cadence call (2.2 Meeting Standards & Working Norms). There is no monthly conversation where a stuck implementer mentions they can't figure out how to publish a dashboard. They just stall — quietly, without complaining, and the account looks unremarkable until it doesn't renew.

For most of the book, education is the coverage. That makes content a health intervention rather than a support nicety, and it changes how the CSM should value the time spent building it: content is the only thing that scales in a solo-CSM model. A template that serves the whole SMB book is worth more than the same hours spent on any single account.

What exists

Each piece below maps to a specific friction point from 1.5 Customer Journey Map. Content that doesn't map to a known stall is content nobody needed.

Automated onboarding sequence

Milestone-triggered emails walking the implementer through Connected → Built → Live → Recurring.

  • Fires on milestone completion — what to do next, now that you've done this
  • Fires on milestone non-completion — a nudge when a milestone is still open past its target (e.g. day 10 with milestone 1 unmet)

The non-completion trigger is the more valuable of the two. It's the only mechanism that reaches into a silently stalling SMB account before the health model has enough history to flag it.

Template library

Pre-built dashboard and report templates, organized by industry.

Directly attacks two stage-2 frictions: the build effort on milestone 2, and the data-hygiene burden — a template that expects certain fields tells the customer what to clean up, rather than leaving them to discover it.

"What to say to your client" script

Change-management guidance for introducing the Portal to an end client.

This is the highest-value piece of content on the list, because it addresses the exposure moment (1.5 Customer Journey Map, stage 3) — the stall that ordinary product documentation cannot touch. The account isn't confused about how the Portal works; they're uneasy about what their client will say. A script the AM can adapt removes the need to improvise a client conversation, which is the actual blocker.

Knowledge base

How-to documentation covering Connect setup by source type, Studio, Portal, and Scheduler. The baseline reference layer — necessary, not differentiating.

Live enablement (Mid-Market and Enterprise)

  • Training sessions for new AM cohorts
  • Refreshers after turnover — which doubles as Champion Departure mitigation (1.5 Customer Journey Map, stage 5): the operational knowledge problem is solved by making sure more than one person knows how things are wired

When education is the right intervention — and when it isn't

The classic tech-touch failure is sending documentation at a structural problem.

Stall Right intervention
Doesn't know how to do the next step Education. Docs, template, tutorial.
Waiting on credentials from someone outside the project Not education. An org-chart conversation, escalated to the practice lead.
Nervous about showing a client Not education, but content helps. The script plus a pilot-client recommendation. Reassurance and a decision made easier, not instruction.
Doesn't have time Not education. Sequencing conversation with the practice lead about realistic scope.
Data isn't client-ready Both. Template guidance plus an honest conversation about cleanup effort.

Diagnose before sending. A stalled account that receives a tutorial for a problem it doesn't have learns that Prism isn't paying attention.

Ownership

There is no education function at this company size.

  • CS owns the content — what exists, whether it's current, whether it maps to real stalls
  • Product and Marketing help produce it — screenshots, polish, distribution
  • The CSM writes the substance, because they're the only one who knows where accounts actually get stuck

This is explicitly part of the CSM's job, not an extracurricular. Time allocated to content is coverage-model work.

Maintenance

Content decays as the product changes. Two rules:

  1. Product change notice (2.5 Cross-Functional Interfaces) triggers a content review. If Product ships a UI change or deprecation, the relevant docs and templates are checked — a knowledge base showing last year's interface is worse than none, because it teaches customers not to trust it.
  2. Quarterly review of what's actually used. Which templates get adopted, which sequence emails get opened, which docs get traffic. Content nobody uses either solves a problem nobody has or isn't findable — both worth knowing.

Findings feed the quarterly system review (2.3 Operating Rhythm).