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

Is there a way to break out CES by renewals at risk?

diego_webb_ecf17

Half our team lives in Snowflake, so getting journey mapping data in there matters. How clean has that been for you?

Find more posts tagged with

Comments

aisha_akoto_7c7ec

Same setup here. In our case it came down to journey alerts being too broad.

nina_trin_286a9

We hit this too. Scoping session replay to self-serve users first made it manageable.

nadia_mehta_b8ff5

Spent a week on this. The fix was tying response routing to the account owner field.

ned_dunn_d9425

Same setup here. In our case it came down to journey alerts being too broad.

nina_pace_77fd6

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

hana_hale_21582

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

ivy_soto_31f7c

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