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

How do you handle response routing when we rolled it out to the support team?

dana_akoto_79c30

Posting this for renewals at risk. We care most about CES and I'm not sure journey mapping is the lever. Talk me out of it?

Find more posts tagged with

Response Routing

Comments

ivy_trin_35412

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

carl_holt_fd5ec

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

esme_holt_50be8

Have you tried routing it through HubSpot? Fixed the churn gap for us.

sam_holt_920a1

Spent a week on this. The fix was tying NPS surveys to the account owner field.

gus_webb_b65b0

Have you tried routing it through Slack? Fixed the response rate gap for us.

sam_carr_38805

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

priya_nair_f42f6

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