NPS Comment Analysis Template (free)

[NPS open-ended follow-up comments collected from promoters, passives, and detractors in usercall.co surveys]

[Example: Jan 1, 2026 – Mar 31, 2026]

[Example: Priya Shah, UX Research]

[Example: What are the main drivers of promoter enthusiasm, passive hesitation, and detractor dissatisfaction in recent NPS feedback?]

"Once we got everything connected, the team started using it daily and it's honestly saved our CS leads a ton of time. The only rough part was setup — figuring out the first workflow took longer than it should have."

"I like the product, but we still can't do role-based routing the way we need to. That's kind of a blocker for rolling it out to the full support org."

"Support was actually great. We hit a weird issue with imports and someone got back to us in like 20 minutes with a workaround and then followed up the next day."

"The UI is clean and most of the team picked it up without training, which is rare for us. I just keep getting pushback from finance that the per-seat pricing feels steep for occasional users."

"We're not churning yet, but we're comparing you pretty closely to a competitor that has deeper Salesforce integration out of the box. Right now it feels like we'd have to patch too much ourselves."

"The product does what we need and I can point to faster response times since we rolled it out, so that's a win. But onboarding was messy — too many steps, too many settings, not enough guidance."

"Honestly the biggest issue is I can't justify the price yet. For a smaller team like ours, the value might be there later, but right now it feels ahead of what we're ready to spend."

"I recommend it because it's easy to use and way less clunky than the tool we replaced. That said, if support had been slower during the first month, we probably would've had a very different experience."

Comments in this theme describe the experience of getting started, configuring workflows, and reaching first value.

This theme captures unmet product needs, missing functionality, and comparison points where alternatives appear stronger.

These comments point to whether customers can see measurable impact and whether that impact feels meaningful enough to justify continued use.

This theme covers reactions to price, seat model concerns, and whether cost feels aligned with current customer needs.

Feedback in this cluster reflects how much responsive, effective support shapes customer confidence and retention.

Key insight: Customers often see value after adoption, but early setup friction can slow activation and dampen first impressions.

Representative quote: "Once we got everything connected, the team started using it daily and it's honestly saved our CS leads a ton of time. The only rough part was setup — figuring out the first workflow took longer than it should have."

Recommended action: Simplify initial configuration with guided setup, best-practice defaults, and clearer onboarding checklists.

Key insight: Missing workflow and integration capabilities are limiting expansion and making competitor alternatives more attractive.

Representative quote: "We're not churning yet, but we're comparing you pretty closely to a competitor that has deeper Salesforce integration out of the box. Right now it feels like we'd have to patch too much ourselves."

Recommended action: Prioritize the highest-frequency missing capabilities and create a clear roadmap message for at-risk accounts.

Key insight: Positive NPS sentiment is often tied to visible operational gains, but customers need help connecting product usage to measurable outcomes.

Representative quote: "The product does what we need and I can point to faster response times since we rolled it out, so that's a win. But onboarding was messy — too many steps, too many settings, not enough guidance."

Recommended action: Arm CS and marketing with ROI proof points, benchmarks, and customer-facing value reviews.

Key insight: Price concerns are less about absolute cost alone and more about whether packaging matches team size, usage frequency, and current maturity.

Representative quote: "Honestly the biggest issue is I can't justify the price yet. For a smaller team like ours, the value might be there later, but right now it feels ahead of what we're ready to spend."

Recommended action: Review packaging and pricing for lighter-use teams, and test clearer messaging on who the current plans are best for.

Key insight: Fast, human, high-quality support strengthens promoter sentiment and can offset friction during the first month of use.

Representative quote: "Support was actually great. We hit a weird issue with imports and someone got back to us in like 20 minutes with a workaround and then followed up the next day."

Recommended action: Preserve response-time strengths, document high-impact support moments, and feed recurring support issues back into onboarding and product improvements.

[Example: Customers clearly value usercall.co once live, but setup friction and missing advanced capabilities are shaping passive and detractor feedback.]

[Example: Onboarding & Setup]

[Example: Review all onboarding-friction excerpts with Product and Customer Success, then prioritize 2–3 setup improvements for the next release.]

[Example: Head of Product, Customer Success Lead, Support Manager]

[Example: Apr 8, 2026]