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 response routing across self-serve users

marcus_mehta_8d608

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

Find more posts tagged with

Comments

ravi_sato_a167a

We hit this too. Scoping journey mapping to trial users first made it manageable.

ivy_mehta_840df

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

kiran_calvi_a59f3

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

elena_calvi_f3e69

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

esme_reyes_83462

We measure NPS weekly now and it's made dashboards decisions much easier.

liam_dunn_831f1

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