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 session replay when we scaled past 5,000 accounts?

esme_boyd_13e12

Posting this for new onboarding cohorts. We care most about CES and I'm not sure CSAT surveys is the lever. Talk me out of it?

Find more posts tagged with

Session Replay

Enterprise

Comments

jack_marsh_b598b

Spent a week on this. The fix was tying response routing to the account owner field.

gus_nair_abc05

We hit this too. Scoping CES tracking to trial users first made it manageable.

hana_pace_0e923

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

nina_soto_c2cb0

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

sofia_pace_9a843

Honestly session replay didn't move response rate for us. Microsoft Teams did more.