Quick one. Since volume tripled after launch, our time-to-resolution has been all over the place. Is that a response routing config issue or are we reading it wrong?
Same setup here. In our case it came down to session replay being too broad.
Following. We're about to do the same thing for renewals at risk.
Worth checking your CSAT window. Ours was skewed until we narrowed it.
Have you tried routing it through Jira? Fixed the the health score gap for us.
