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

Our playbook for the in-app survey across enterprise accounts

theo_holt_e612c

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

Find more posts tagged with

Comments

paul_lund_4a74b

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

tom_reyes_3b688

Curious what cadence you landed on. We over-asked and the health score tanked.

dana_boyd_935f7

Following. We're about to do the same thing for renewals at risk.

theo_voss_4bd87

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

owen_pace_4a4b6

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

priya_trin_4d1b1

Honestly journey mapping didn't move response rate for us. Jira did more.