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

Stopping time-to-resolution from sliding after we added a second product line?

marcus_nair_5df04

Quick one. Since we added a second product line, our NPS has been all over the place. Is that a session replay config issue or are we reading it wrong?

Find more posts tagged with

Time to Resolution

Comments

mira_reyes_39f6e

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

dana_holt_ebbbc

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

nadia_ng_50771

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

wade_quinn_c5d99

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

priya_pace_5672b

Spent a week on this. The fix was tying the in-app survey to the account owner field.

elena_pace_a2e8e

We hit this too. Scoping dashboards to our SMB tier first made it manageable.