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

Stopping CSAT from sliding after we switched CRMs last month?

maya_sato_8f073

Quick one. Since we added a second product line, our time-to-resolution has been all over the place. Is that a the in-app survey config issue or are we reading it wrong?

Find more posts tagged with

CSAT

CRM Migration

Comments

paul_quinn_e7e68

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

aisha_holt_de6fd

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

liam_voss_14a4f

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

sam_calvi_c3acc

Have you tried routing it through Microsoft Teams? Fixed the renewal rate gap for us.

cole_boyd_8e533

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

ravi_holt_29128

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

kiran_carr_9dec5

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