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 response rate from sliding after we rolled it out to the support team?

nadia_vance_ff0e0

Posting this for self-serve users. We care most about CSAT and I'm not sure session replay is the lever. Talk me out of it?

Find more posts tagged with

Response Rate

Comments

nina_pace_ae287

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

maya_carr_75cb2

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

ruth_pratt_6209d

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

liam_boyd_a7a80

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

sam_webb_65ba1

Curious what cadence you landed on. We over-asked and the health score tanked.

yuki_vance_26b7f

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

felix_frei_eda17

We hit this too. Scoping journey mapping to self-serve users first made it manageable.

carl_voss_ec99f

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

nadia_mehta_ebf9f

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