Should CSRs and sales reps be scored on the same rubric?
No. A CSR converts an inbound call into a booked appointment in a few minutes. A sales rep diagnoses, presents options and asks for a decision, usually in person and over a much longer conversation. A few core items overlap — identification, listening, a clear next step — but the outcome each role controls is different, so the weighted items have to be different.
Score people on what they can actually control
The CSR does not control whether the job sells. She controls whether a qualified caller ends the call with an appointment on the calendar and accurate information attached to it. Scoring her on average ticket punishes her for a technician's conversation she was not part of.
The sales rep does not control lead quality or the promise the CSR made on the phone. He controls the walkthrough, the diagnosis, the options presented and whether a decision was requested. Scoring him on call volume is the same category error in the other direction.
The general rule is simple to state and easy to violate: score people on the part of the outcome they can influence, and report the rest as context. Context still matters, it just does not belong in someone's performance number.
The overlap is smaller than it looks
Three or four items belong on both rubrics: identifying yourself and the company, letting the customer describe the problem before proposing anything, confirming what you heard, and ending with a specific next step and a time.
Almost everything else diverges. Callback number capture is critical for the CSR and irrelevant once a rep is standing in the kitchen. Presenting more than one option is central to the sales visit and usually wrong on a two-minute intake call.
The third role people forget
Dispatch and scheduling is its own standard. That role handles reschedules, arrival windows, angry callers whose technician is late, and confirmation calls — none of which have a booking outcome to score against. Judge it on accuracy, promise-keeping and de-escalation instead.
Shops that run one rubric across all three roles end up with a scorecard that is unfair to two of them. Separate standards are cheap to maintain when the rubric layer is configurable per role.
Dispatchers also absorb the consequences of everyone else's mistakes, which makes their scores noisy if you are not careful. A confirmation call that goes badly because the technician is three hours late is not a dispatcher failure, and the rubric has to be able to tell the difference.
Where the two rubrics should talk to each other
The most useful cross-role report is not a score at all. It is the comparison between what the CSR told the customer would happen and what the technician found when he arrived. Repeated mismatches there cause cancellations, discounts and bad reviews, and neither rubric catches them alone.
Joining call data to job outcomes is what makes that visible — the same plumbing behind revenue intelligence reporting.
Topics: role standards · CSR · sales · rubric design
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.