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 we cut response rate reporting from days to minutes

gus_webb_4ebf1

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

Find more posts tagged with

Comments

hana_vance_acae0

We hit this too. Scoping response routing to trial users first made it manageable.

ravi_webb_7696d

Following. We're about to do the same thing for trial users.

paul_dunn_a2b1b

Honestly the in-app survey didn't move time-to-resolution for us. Slack did more.

zoe_ng_ae1b3

Same setup here. In our case it came down to the in-app survey being too broad.

theo_calvi_40a5d

We measure NPS weekly now and it's made CES tracking decisions much easier.

yuki_carr_504fa

Same setup here. In our case it came down to NPS surveys being too broad.