TesseraData warehouse620 employeesNorth America, EMEA

Tessera cut onboarding tickets in half by publishing docs and video together

Tessera's customer education team could record six lessons a month against a product that changed twelve things a month. Generating video and documentation from one capture closed the gap — and halved onboarding ticket volume in two quarters.

Customer educationHelp centerLocalizationAnalytics
−51%
Onboarding support ticketsTwo quarters after the academy relaunch
4×
Lessons published per quarterSame two-person education team
+29%
Course completion rateAfter restructuring based on retention data
6
Languages by defaultPreviously English only

“The written guides are the sleeper feature. Every video we publish also becomes a help article, in six languages, with screenshots that are always current. Support ticket volume on onboarding fell by half.”

MLMika LindqvistHead of Customer Education, Tessera

The academy was quietly becoming wrong

Tessera had a well-regarded customer academy: forty-one lessons covering everything from first connection to advanced modelling. It had been built over eighteen months by a two-person team, and by the time the last lesson was published the first eleven were describing an interface that no longer existed.

“Content decay is the whole problem in customer education and nobody talks about it,” says Mika Lindqvist. “Everyone benchmarks how many lessons you have. Nobody benchmarks how many of them are still true.”

The written documentation was maintained separately, by a different team, which meant the video and the article would periodically contradict each other — the fastest way to lose a customer's trust in both.

One capture, both formats, permanently in sync

Tessera rebuilt the academy so that every lesson is a single recording producing both a video and a written article. Because they are derived from the same source, they cannot disagree.

When the product changes, the team re-records only the affected step. The video, the article, the animated GIFs and all six language versions rebuild around it. A UI refresh that would previously have been triaged into next quarter is now an afternoon.

The team also discovered a use they had not anticipated: retention data across the course turned out to be a product signal. A lesson that everyone abandons at the same step is usually pointing at a genuinely confusing part of the product.

Support saw it first

The ticket impact was not gradual. Within six weeks of publishing the rebuilt onboarding track, tickets tagged as onboarding questions fell by roughly a third; by the end of the second quarter they were down 51%.

Lindqvist attributes most of it to two things: the guides being genuinely current, and the same content existing in both formats. “Half our customers were never going to watch a video. We had been serving them a transcript and calling it documentation.”