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

Moved renewal rate with journey alerts — here's our setup

nina_okafor_c6ecf

Trying to get response routing right for self-serve users. The defaults don't quite fit. What did you change?

Find more posts tagged with

Comments

omar_marsh_35103

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

ned_nair_94153

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

sofia_calvi_068e8

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

ned_boyd_b8cef

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

mira_webb_fbffb

Worth checking your time-to-resolution window. Ours was skewed until we narrowed it.

paul_dunn_4bde1

Honestly response routing didn't move response rate for us. Microsoft Teams did more.

priya_carr_35449

We hit this too. Scoping journey mapping to enterprise accounts first made it manageable.

sofia_webb_37d00

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