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

Small win: response routing caught a churn risk early

felix_carr_207e4

We measured time-to-resolution before and after turning on segments. The result surprised us. Anyone seen the same?

Find more posts tagged with

Comments

tara_voss_61f01

Honestly CES tracking didn't move NPS for us. Snowflake did more.

marcus_holt_b9f0e

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

carl_quinn_1419c

We hit this too. Scoping auto-theming to our SMB tier first made it manageable.

cole_nair_6793c

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

ivy_ng_88840

We hit this too. Scoping journey mapping to self-serve users first made it manageable.

gus_nair_fda86

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

diego_lund_13588

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

sofia_marsh_a7635

Same setup here. In our case it came down to CES tracking being too broad.