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

Segment sync dropping CSAT — anyone seen this?

priya_frei_a0fe0

Posting this for our SMB tier. We care most about the health score and I'm not sure auto-theming is the lever. Talk me out of it?

Find more posts tagged with

Comments

tom_ng_43b50

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

sofia_nair_570a6

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

tom_sato_a5553

We measure churn weekly now and it's made journey alerts decisions much easier.

tom_frei_97dfe

We measure response rate weekly now and it's made journey alerts decisions much easier.

liam_soto_f5521

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

maya_lund_6e644

We hit this too. Scoping CSAT surveys to trial users first made it manageable.

paul_nair_0afaf

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

ivy_okafor_65d33

Curious what cadence you landed on. We over-asked and time-to-resolution tanked.