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

Pulling NPS out through the API for our warehouse

tara_boyd_71098

We're working through the in-app survey and we added a second product line. Curious how others have handled it, especially around renewal rate. Any rules of thumb?

Find more posts tagged with

Comments

theo_pace_3ea4b

Following. We're about to do the same thing for self-serve users.

yuki_quinn_3dc9c

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

cole_vance_c2ff4

Following. We're about to do the same thing for renewals at risk.

esme_pace_fe1a8

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

mira_vance_f6d12

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

paul_rourke_d794e

Spent a week on this. The fix was tying journey mapping to the account owner field.

liam_pace_f7f83

Honestly journey alerts didn't move NPS for us. Jira did more.