nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

the in-app survey behaving oddly since volume tripled after launch — ideas?

ivy_rourke_a8344

We're working through response routing and we added a second product line. Curious how others have handled it, especially around response rate. Any rules of thumb?

Find more posts tagged with

Feedback Widget

Comments

liam_trin_6fb93

We hit this too. Scoping NPS surveys to self-serve users first made it manageable.

wade_carr_69d37

+1. The Salesforce step is where ours kept breaking.

aisha_sato_70dff

Curious what cadence you landed on. We over-asked and CSAT tanked.

jack_pace_c09b0

Honestly NPS surveys didn't move CES for us. Slack did more.

felix_marsh_cdcca

Have you tried routing it through Jira? Fixed the NPS gap for us.

Quick Links

All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of