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; } } }

How do you handle the in-app survey when we scaled past 5,000 accounts?

priya_pace_c8ab1

We're working through response routing and we scaled past 5,000 accounts. Curious how others have handled it, especially around CES. Any rules of thumb?

Find more posts tagged with

Feedback Widget

Enterprise

Comments

sofia_sato_0d1f3

Worth checking your response rate window. Ours was skewed until we narrowed it.

ivy_dunn_8b571

We hit this too. Scoping CSAT surveys to renewals at risk first made it manageable.

hana_hale_2c62b

We hit this too. Scoping NPS surveys to trial users first made it manageable.

elena_holt_074c3

We measure the health score weekly now and it's made auto-theming decisions much easier.

nadia_akoto_07f98

We hit this too. Scoping CES tracking to new onboarding cohorts first made it manageable.

aisha_trin_91256

Curious what cadence you landed on. We over-asked and time-to-resolution tanked.