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

What worked for us setting up response routing

theo_webb_f9703

Posting this for self-serve users. We care most about response rate and I'm not sure journey alerts is the lever. Talk me out of it?

Find more posts tagged with

Comments

yuki_trin_ffcd0

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

lena_pace_ebb64

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

dana_quinn_cb951

We hit this too. Scoping session replay to renewals at risk first made it manageable.

wade_nair_647a2

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

maya_ng_63f0e

Worth checking your renewal rate window. Ours was skewed until we narrowed it.

esme_rourke_780c9

Same setup here. In our case it came down to auto-theming being too broad.

lena_holt_f50b6

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

omar_ng_05462

Following. We're about to do the same thing for self-serve users.