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

Stopping time-to-resolution from sliding after we rolled it out to the support team?

maya_marsh_f90e0

We measured CSAT before and after turning on dashboards. The result surprised us. Anyone seen the same?

Find more posts tagged with

Time to Resolution

Comments

maya_webb_90055

We hit this too. Scoping journey mapping to self-serve users first made it manageable.

cole_voss_62453

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

omar_mehta_bc16a

Worth checking your time-to-resolution window. Ours was skewed until we narrowed it.

tara_boyd_9fd6e

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

diego_calvi_539f6

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

Quick Links

All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of