The CSR Who Will Not Challenge a Prospect After 6 Years: A DISC Case Study
By Craig Pretzinger and Jason Feltman
After six years, she still will not introduce a product the client did not ask about. Most owners assume it is a motivation problem. DISC data says it is almost always something different.

Six Years and She Still Won't Ask the Question
Six years in. Knows every renewal date on every account she touches. Handles carrier disputes without escalating. Clients ask for her by name.
And she will not, under any circumstances, say: "I noticed you carry auto with us but not home. Can we look at that?"
You've had this conversation three times. She nods. Agrees it matters. Two weeks later, nothing's different.
Before you have that fourth conversation, consider what the Insurance Dudes' DISC research says directly: "DISC describes behavior, not performance." The reason she's not initiating cross-sell conversations is almost certainly not that she lacks courage or doesn't care about the agency. The behavior you're asking for runs directly against how she's wired.
What a High-S Actually Experiences
The DISC framework describes high-S profiles as patient, service-oriented, consistent, and deeply resistant to conflict. Not big dramatic conflict. Conflict in the sense of introducing any information that might change how the client experiences the call.
For your high-S CSR, a cross-sell conversation feels like introducing friction into a relationship she spent years making smooth. Even when the client would benefit. Even when the product is genuinely relevant. Her brain is saying: "I don't want to risk this relationship by saying something they didn't come here to hear."
That's not a character flaw. That's a behavioral profile doing exactly what it was built to do. High-S instinct is to stabilize, not push. Asking her to push without addressing the underlying pattern is asking her to fight her own wiring on every single call.
Sales Strength Is a Separate Variable
The Insurance Dudes' analysis makes a point most agency owners miss: sales strength is separate from personality profile. A high-S can absolutely sell. The path just looks different than it does for a high-D or high-I.
A high-D says "I need to make sure you have everything covered. Do you have home with us?" and the directness feels natural coming out of their mouth. For a high-S, that same directness feels abrasive when they try to deliver it.
The phrasing that works for her connects the proactive conversation to service rather than selling: "One thing I always check when I have a client with auto is whether there's a gap on the home side. Can I get you a quick comparison?"
Same goal. Different frame. The service language matches her communication style.
The reason most cross-sell training fails for high-S team members is that it hands them scripts written by high-D trainers. Those scripts feel fake when she delivers them. The behavior doesn't change because the tool doesn't fit the hand.
What Account Rounding Actually Means for Retention
Kelly Donahue's agency systems work puts a concrete number on this: agencies hitting 80 percent or more of clients carrying multiple policies show measurably better retention. The client with three policies doesn't leave for a 10 percent discount. The client with one policy might.
Your CSR handling every renewal on a single-policy client and never introducing a second product is, without meaning to, creating retention risk. She's working with tools that don't match the job she's being asked to do.
Agency Performance Partners' benchmarks put the standard for a CSR in a hybrid service/rounding role at about 50 account rounding conversations per month. Most agencies measuring this find they're way below it, and the gap isn't from CSRs refusing the goal. It's from CSRs who don't have a communication structure that makes the goal accessible.
The Tracking Piece Most Owners Skip
Seth Preus's accountability work shows that weekly tracking enables course correction at the speed decisions actually happen. Monthly rounding reviews tell you whether last month was good or bad. Weekly check-ins on conversations initiated tell you whether this week is on track.
For a high-S team member, weekly tracking isn't threatening when you frame it right. The framing that works: "I want to know how many conversations you had, not what the outcome was." Counting conversations is a process metric. It's not a judgment on whether she closed anything. It gives her a number she can hit through consistent behavior, which is exactly how she's wired.
The accountability structure that fails for high-S: "You need to be doing more account rounding." Too vague, no weekly feedback, no way to know if the behavior is changing. The one that works: "Let's track rounding conversations each week and see what the number is." Now there's a process to follow. That's high-S native territory.
The Four-Step Fix
Step 1: Run the DISC assessment. Before the next cross-sell conversation, run the profile. Look at S and D scores specifically. If S is dominant and D is low, you're dealing with a communication style problem, not a motivation problem. That changes your entire approach.
Step 2: Build service-framed scripts together. Work with her to write two or three phrases that introduce a rounding conversation in service language. Let her write them. A high-S who owns the script will use it. One that was handed to her feels like a costume.
Step 3: Set a weekly conversation count, not a close rate. Start at 10 rounding conversations per week. Not closes. Conversations. The close rate follows once the behavior is in place. Preus's tracking data consistently shows this sequence.
Step 4: Give feedback on the language, not the outcome. When she reports back, ask "how did the conversation go?" not "did they buy?" For a high-S, the quality of the relationship during the call is what she's evaluating. Work inside that frame.
That fourth conversation about cross-selling doesn't have to go the same way the first three did. When you change the structure to match the behavioral profile, the behavior follows. When you keep running the same play and expecting a different result, you're carrying a problem that has a straightforward fix.