This maps onto the DiSC Call Flow Tool. Its 23 steps, 13 internet and 10 video, move through the same seven stages below, and its misread-recovery banners use the exact language quoted in the Misread Recovery section. If you're running the tool live, this page is the "why" behind what it's prompting you to say.
STAGE 1
Open & Greeting
The first ten seconds set the pace for the whole call, and customers don't announce their style. This stage is about reading tone and pace from how they answer your first question, not locking in a label. In the tool, this lines up with the "Reading the Room" step before Step 1.
"Let's get this sorted — can I get your name and the address on the account?"
Watch for: short answers, no small talk, may interrupt your greeting script entirely.
"Thanks for calling in — I'll get you sorted. First, who do I have the pleasure of helping today?"
Watch for: chatty, friendly, may answer the wrong question while telling a story.
"Hi, thanks for your patience — I'm here to help. Can you start with your name and address?"
Watch for: softer, slower delivery, may apologize for calling or hesitate before answering.
"Good afternoon. To pull up the right account, I'll need your name and service address."
Watch for: precise, may volunteer account numbers or specifics unprompted.
A customer answers your greeting with "Yeah, hi, look, my internet's been down for an hour" before you finish your line. That clipped, get-to-it tone is a D signal. Drop the rest of the scripted greeting and go straight to gathering details.
STAGE 2
Discovery
This is where the customer describes the problem in their own words, Step i-2 / v-1 in the tool ("Gather Issue Details"). The skill isn't talking. It's listening differently by style. Some customers need to be drawn out. Others need to be reined in.
"Got it. Full outage, slow, or just one device?"
Watch for: getting talked over if you ask open-ended questions — narrow to multiple choice.
"Oh no, that's frustrating! Tell me what's going on — when did you first notice it?"
Watch for: tangents — gently redirect with warmth, not a cutoff.
"No rush at all — just walk me through what's been happening."
Watch for: minimizing their own problem ("it's probably nothing") — take it seriously anyway.
"Can you give me specifics — error codes, light patterns, exact timing?"
Watch for: they may already have done their own diagnosis — ask what they've already tried.
A customer says "I don't really know computers but the little light on the box thing is doing something weird, I think it's blinking?" That hedging, apologetic tone reads S. Slow down, make it normal not to know the terms, and describe what to look for instead of asking them to diagnose it.
STAGE 3
Diagnosis
Steps i-3 through i-6 / v-2 through v-7 in the tool, checking for area outages, identifying equipment, reading lights and displays. This stage has the most back-and-forth, and the most chances for a customer to feel rushed or talked down to.
"Checking now for an outage in your area — give me five seconds."
Watch for: impatience with silence — narrate briefly rather than going quiet.
"Let's play detective for a second — I'm checking if this is a bigger thing on our end."
Watch for: keep energy up during dead air, or they may disengage.
"I'm checking a couple things on my end — you haven't done anything wrong, this is just normal troubleshooting."
Watch for: they may apologize during dead air — reassure, don't just fill silence.
"I'm cross-referencing your modem's signal levels against our outage map now."
Watch for: they may ask why a step matters — have the actual reason ready, not just "standard procedure."
A customer asks "Why do you need to know what kind of modem I have? Can't you just see that?" That's not hostility. For a C, it's a request for the logic. Explain that the equipment type changes which lights and steps apply, instead of just repeating the question, and it usually resolves on the spot.
STAGE 4
Resolution
The reboot, the refresh signal, the test, steps i-7 through i-9 / v-5 through v-9. Customers usually have to wait here, since the 60-second power-cycle window is non-negotiable, and how you frame that wait matters as much as the fix.
"60 seconds, starting now. Don't plug it back in early — it won't fully reset if you do."
Watch for: the urge to rush the wait themselves — be direct about why the timing matters.
"Alright, unplugged! While we wait the minute, how's your day going otherwise?"
Watch for: use the wait time for rapport, not silence — it keeps them engaged instead of restless.
"Take your time unplugging it — I'll stay on the line the whole 60 seconds with you."
Watch for: don't disappear during the wait — staying present matters more than the content of what's said.
"The full 60 seconds lets onboard memory fully discharge — a shorter wait won't reliably reset it."
Watch for: giving a vague "just trust me" — they'll comply faster once they know the mechanism.
A customer says "I'll just unplug it for 10 seconds, that's basically the same thing, right?" Instead of repeating the instruction, explain briefly why it isn't the same. For most styles, the reason ("the modem needs the full minute to clear") gets more cooperation than restating the rule.
STAGE 5
Misread Recovery
Sometimes the read was wrong. What looked like D was a stressed S, or a quiet C turns out to be an i who hadn't warmed up yet. The call-flow tool has a recovery banner for exactly this moment, triggered the instant you reclassify mid-call. The lines below are the tool's actual recovery language. Use them verbatim or as a model.
"Got it — switching gears. I'll keep this quick and skip ahead to what matters."
Watch for: don't over-explain the switch — a D wants the new approach, not an apology for the old one.
"Ah, gotcha — let's recalibrate. I'll walk through this with you a little differently."
Watch for: keep it light — treat the correction as normal conversation, not a stumble.
"No problem at all — let's slow down and take this at whatever pace works for you."
Watch for: reassure explicitly that the misread isn't their fault or an inconvenience.
"Understood — adjusting my approach. I'll be more precise about the next few steps."
Watch for: don't just apologize — naming the specific adjustment rebuilds credibility faster.
You opened brisk and direct, assuming D, but three exchanges in the customer keeps asking "wait, can you back up, why does that happen?" That's a C signal you missed. Reclassify out loud with the C recovery line above, then start giving the mechanism behind each step, not just the instruction.
STAGE 6
Escalation
The tool's final step in each path is titled "Resolution or Escalation," the moment you tell a customer the issue needs a technician, a different team, or more time than this call allows. This is the highest-stakes point on the call. Handled well, escalation builds trust. Handled poorly, it reads as a brush-off no matter the style.
"This needs a technician on-site. I can get you booked for [day] — want the soonest slot?"
Watch for: don't hedge or apologize excessively — lead with the next concrete action.
"I really wish I could fix this one over the phone, but I'm going to get our tech team out to take great care of you."
Watch for: don't let the warmth replace clarity on what happens next and when.
"This is going to need a technician, but you've done everything right — let's get you scheduled."
Watch for: explicitly remove blame — S customers often worry escalation means they did something wrong.
"Based on the signal levels we found, this requires a line technician — here's exactly what they'll check on-site."
Watch for: give the actual diagnostic reasoning for the escalation, not just the decision.
Every troubleshooting step is exhausted and the issue still isn't fixed. A D customer who's been clipped and efficient the whole call doesn't want sympathy now. They want the next available appointment slot, stated plainly. Comfort instead of a date reads as stalling.
STAGE 7
Close
The wrap-up: confirming the outcome, logging it, ending the call. In the tool, this is where the call-outcome log (Resolved or Escalated, plus an optional note) appears. The close is also where a rushed ending can undo good work, or a slow one can finally lose a D customer's patience.
"You're all set — fixed and confirmed. Anything else before I let you go?"
Watch for: a long wrap-up script will undo the efficiency they valued the whole call.
"Glad we got that sorted! It was great chatting with you — call back anytime if anything comes up."
Watch for: end warmly, not abruptly — a flat close can feel like a cold shoulder.
"That should do it — and if anything comes back, you can call again and we'll pick right back up."
Watch for: confirm explicitly that calling back isn't a burden — reassurance matters even at the end.
"To summarize: we identified [cause], resolved it via [fix], and confirmed signal levels are back to normal."
Watch for: skipping the summary will leave them feeling the call ended without real confirmation.
The fix worked, but the customer goes quiet at the close instead of confirming. For an S, silence at the end usually means lingering uncertainty, not satisfaction. A direct check-in ("just to confirm, is everything working on your end now?") gets a real answer instead of an assumed one.
The style doesn't change what's true about the problem. It changes whether the customer feels like the call was about them, or about the script.
See it built into a live tool
The DiSC Call Flow Tool walks through all 23 steps of an internet or video call with pre-written language for every style, plus the misread-recovery banner referenced above.
Open the Call Flow Tool Book a free intro call