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

tara_trin_8beb5

Posting this for renewals at risk. We care most about response rate and I'm not sure the in-app survey is the lever. Talk me out of it?

Find more posts tagged with

Comments

mira_reyes_4c412

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

nadia_okafor_212e5

Have you tried routing it through Jira? Fixed the NPS gap for us.

ravi_marsh_51f66

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

wade_ng_ed1f9

Following. We're about to do the same thing for trial users.

sam_dunn_a4b8e

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

ivy_ng_470ec

Same setup here. In our case it came down to the feedback widget being too broad.

sam_nair_28556

+1. The Microsoft Teams step is where ours kept breaking.

gus_soto_1a7bb

Have you tried routing it through Zendesk? Fixed the time-to-resolution gap for us.

hana_okafor_e4bb8

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