Finding Onboarding Friction Across Customer Conversations

Finding Onboarding Friction Across Customer Conversations

The Challenge

Onboarding is where Oura either earns a customer’s confidence or loses it. New users arrive with expectations shaped by the sales process, and the first few interactions with the product set the tone for everything that follows. Oura’s customer-facing teams understood this and invested heavily in onboarding support.

The challenge was visibility. Onboarding feedback arrived from every direction.

Feedback sources:

• Live chat

• Implementation calls

• Support tickets

• Customer success notes

Each source captured a piece of the new-customer experience. Live chat exposed in-the-moment confusion. Implementation calls surfaced setup friction that customers would never bother to log. Support tickets recorded repeatable technical issues. Customer success notes carried the qualitative texture of how onboarding actually felt for a new account.

But no single team owned all of those sources, and no one had a complete view of where new customers were actually getting stuck. A CSM running an implementation call might notice a setup problem that never appeared in support data. A live chat rep might handle the same confusion ten times in a week without that pattern reaching the product team responsible for fixing it.

Worse, it was hard to separate isolated complaints from repeated problems. A single frustrated ticket could look urgent in isolation but represent a one-off edge case. Meanwhile, a quieter pattern, the same small confusion mentioned across different channels by different customers, could be the real onboarding gap and go unnoticed because no individual signal looked significant. Without a way to assemble those conversations together, Oura could not confidently tell which friction was structural and which was incidental.

How Oura Used Fawna

Oura brought their onboarding conversations into Fawna and grouped them by the dimensions that mattered most for finding friction.

Grouping dimensions:

• Product area

• Segment

• Urgency

• Source

With conversations organized this way, the team could move beyond individual anecdotes and look at patterns. They focused on three questions that helped them prioritize the right work:

• Which problems appear across multiple channels and therefore represent real friction?

• Where do customers need guidance versus where does the product itself need to change?

• Which issues create the most work for onboarding teams and customers alike?

Asking those questions inside Fawna let Oura see onboarding friction the way it actually existed: distributed across sources, repeated across customers, and concentrated in specific product areas and segments. A theme that showed up in live chat, implementation calls, and CS notes was clearly structural. A theme that appeared only in tickets from one segment pointed to a more targeted fix. Urgency helped the team sequence what to address first, while source context helped them understand the nature of each problem.

What Changed

Product and customer success began reviewing the same evidence before retrospectives and planning cycles. Previously, each team arrived with its own list of issues, gathered from different sources and weighted by different instincts. Now they opened Fawna together and walked through the same themed conversations. That shared starting point removed the alignment tax that had slowed every prior onboarding discussion.

Every theme was connected to its original conversation. When the team identified a friction point, they could immediately read the actual words customers used, see which channels it came from, and understand which segments were affected. Decisions were no longer based on summarized abstractions stripped of context. They were grounded in the real evidence of what customers experienced.

That clarity let Oura prioritize with confidence. The team focused on the improvements that would most reduce friction across the largest number of new customers.

Priority improvements:

• Setup flow simplification

• Permissions clarity

• Workflow visibility for new users

Each of those priorities was traceable back to a body of conversation evidence, which made it easier to justify, sequence, and measure.

What Oura Achieved

• Onboarding friction visible across all channels in one place, not siloed by team

• Product and customer success teams aligned on shared evidence before planning

• Improvements prioritized with confidence because every theme connected to real conversations

• Less manual compiling of feedback across sources before each review

• A clearer distinction between genuine product gaps and education gaps

“Fawna finally gave us a complete picture of where new customers get stuck. We can tell the difference between a one-off complaint and a real pattern, and every onboarding decision we make now traces back to actual conversations. Our product and CS teams are working from the same evidence for the first time.”