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

auto-theming behaving oddly since we rolled it out to the support team — ideas?

ivy_nair_9dec6

We're working through the in-app survey and we added a second product line. Curious how others have handled it, especially around time-to-resolution. Any rules of thumb?

Find more posts tagged with

Comments

wade_ng_f1dfc

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

lena_rourke_f519f

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

ravi_ng_0af76

Honestly session replay didn't move time-to-resolution for us. Snowflake did more.

tara_hale_8cc58

We hit this too. Scoping auto-theming to enterprise accounts first made it manageable.

theo_hale_eedb4

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

nina_webb_4fc3d

Spent a week on this. The fix was tying the feedback widget to the account owner field.

priya_okafor_520c6

Have you tried routing it through Salesforce? Fixed the the health score gap for us.