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

journey mapping behaving oddly since we switched CRMs last month — ideas?

omar_rourke_c88ad

Half our team lives in Microsoft Teams, so getting auto-theming data in there matters. How clean has that been for you?

Find more posts tagged with

Comments

zoe_ng_51265

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

tom_soto_389f5

We hit this too. Scoping response routing to renewals at risk first made it manageable.

diego_carr_43e18

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

sam_rourke_831d7

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

tom_ng_62013

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

Quick Links

All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of