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

Small win: auto-theming caught a churn risk early

theo_ng_ab916

Half our team lives in Salesforce, so getting the feedback widget data in there matters. How clean has that been for you?

Find more posts tagged with

Comments

ned_nair_5e8e4

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

owen_quinn_d03aa

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

bea_boyd_e4317

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

hana_boyd_9b60a

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

hana_soto_f83a6

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

owen_holt_32c7a

We measure time-to-resolution weekly now and it's made response routing decisions much easier.