Plan requirement
| Subscription | Any plan |
| Also required | Quality Assurance or Workforce Engagement Management |
| Access | Agent |
The comment is the review that matters. Everything else on the screen is bookkeeping around it.
Writing feedback
- Quote the specific part of the conversation.
- Say what the effect was.
- Say what would have worked better.
- Note one thing that went well.
Be specific or say nothing
"The second reply gave the return address but not the deadline, so the customer wrote back to ask" is actionable. "Could be more complete" is not, and it reads as criticism without content.
Say what to do instead
Feedback that names a problem without a better alternative leaves the agent knowing they were wrong and not what right looks like. That is demoralising and useless in equal measure.
Include what went well
Not as padding. Agents repeat what they know worked, and a review that only lists faults teaches nothing about what to keep doing.
Write to the person
Somebody will read this about their own work. Passive constructions and clinical phrasing make ordinary feedback feel like a formal finding.
Receiving it
Read it when you have a few minutes, not between two tickets. First reactions to feedback are defensive by design, and the second reading is the useful one.
If you disagree, dispute it. That is what the mechanism is for, and a reviewer being corrected is a normal outcome rather than a confrontation.
Talk about the patterns
One review is one exchange. A conversation about three months of reviews is where anything actually changes.
Comments
0 comments
Article is closed for comments.