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

Webhook for segments firing twice — dedupe advice?

diego_webb_d3301

We measured time-to-resolution before and after turning on auto-theming. The result surprised us. Anyone seen the same?

Find more posts tagged with

Comments

elena_frei_56b34

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

jack_pace_3b43e

Curious what cadence you landed on. We over-asked and response rate tanked.

kiran_akoto_f9009

Following. We're about to do the same thing for new onboarding cohorts.

zoe_ng_ae1b3

Worth checking your the health score window. Ours was skewed until we narrowed it.

maya_okafor_66230

Have you tried routing it through Snowflake? Fixed the NPS gap for us.

omar_reyes_69c07

Honestly segments didn't move time-to-resolution for us. Marketo did more.

priya_dunn_f2b72

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