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

Getting response routing into Jira cleanly

ruth_quinn_e1648

Posting this for enterprise accounts. We care most about churn and I'm not sure the in-app survey is the lever. Talk me out of it?

Find more posts tagged with

Comments

owen_calvi_1ce7d

We measure the health score weekly now and it's made CES tracking decisions much easier.

esme_rourke_ec05b

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

maya_soto_9e27b

Same setup here. In our case it came down to response routing being too broad.

omar_voss_8626e

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

priya_soto_50001

We measure CES weekly now and it's made segments decisions much easier.

esme_carr_8b591

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