Leaders at a utility want one number for the outage agent, which tells a customer the current status of that customer's outage. Which metric should the architect report?
Select an answer to reveal the explanation.
Short Explanation
Counting people who walked into the lobby does not tell you who left with the right outage status. You report how often the agent finishes with the correct status for that customer. A raw session count stays high even when the status is wrong.
Full Explanation
The number leadership asked for has to measure the job the agent was given, which is stating the correct outage status for that customer. Completion of the correct status does that in one figure. A count of sessions opened stays high when people ask and the agent says nothing useful, so it is a volume figure rather than a result. Average word count can reward a long wrong status the same way it rewards a short right one, because length does not compare the reply to the outage record. License counts describe what the team is allowed to buy, not whether yesterday's outage replies were right. The status metric still needs a definition of correct, taken from the outage record for that customer, or the number becomes another vanity figure with a better name. Exam caveat: one executive number is fine when it is task completion. It is not fine when it is traffic. Operational check: score a sample of replies against the outage record, mark a reply wrong when the status does not match that customer's outage, and keep the session count off the quality line.