SDR: Manager AI

When a prospect asks whether AI will replace managers, treat the question as an opening into a real coaching workflow. A broad answer about technology leaves an SDR with no reason for a second conversation. A useful answer finds one review task, the judgment attached to the task, and the person responsible for policy. The goal is not an argument about replacement. The goal is a meeting where people examine work already slipping through the gap.

Start with a recent moment rather than a future prediction. Ask when a manager last listened to a call before a coaching meeting. Ask what happened after a rep missed a key question or lost control of a conversation. Ask who decides whether feedback from a recorded call fits internal rules. Each answer moves away from an abstract concern and toward a process somebody owns.

In a fictional practice call, Leah speaks with Samira, a regional vice president. Samira says, “My managers fear AI will remove their role or add another screen to watch.” Leah replies, “Which part of call review has become hardest to keep up?” Samira says managers used to hear two calls before each one to one coaching session. Busy weeks now push those reviews aside. Leah asks, “When a manager does hear a call, what judgment do you expect?” Samira says each manager should choose one behavior, explain why the moment mattered, and agree on a practice step with the rep.

Leah has learned something useful without making a product claim. The missed task is call review before coaching. The manager judgment is selecting one behavior from a full conversation. The next question is governance. Leah asks, “Who has a view on recorded calls and generated feedback?” Samira names enablement, human resources, and information security. Leah then proposes a working session with those people and one frontline manager. Her request has a purpose: map the current review path and decide whether a focused practice session deserves further work.

Notice what Leah leaves out. She does not promise fewer manager hours. She does not say software will score every call correctly. She does not claim a rep will improve after receiving feedback. Those outcomes depend on local routines, source quality, manager skill, approval rules, and many details outside an early sales conversation. A precise question builds more trust than a long answer built from assumptions.

Preparation matters before a first call. Read the account notes for hints about manager span, call review habits, onboarding pressure, or a recent change in sales leadership. Write two open questions and one meeting request. Keep each question short enough for a prospect to answer without translating jargon. For example, “Where does coaching preparation break down now?” asks for a real scene. “What does your call coaching strategy look like?” invites a vague response and makes follow up harder.

An SDR also needs a way to separate an opinion from a buying signal. “AI is everywhere” is an opinion. “Our managers stopped reviewing calls before coaching meetings” points to a workflow. “I do not know who approves call recordings” points to a decision path. Write each response in the call note using the prospect’s own terms. Do not label a concern as urgent unless the prospect describes urgency. During a later meeting, those exact notes help the group agree on what deserves attention.

Some prospects ask the replacement question as a test. They want to learn whether an SDR will overstate a tool or respect manager work. A calm response keeps the focus practical. Try, “I would start with the coaching work managers perform today. Which part requires their judgment, and which review step gets skipped when time is tight?” This response neither dismisses concern nor turns the call into a debate about a future no one has defined.

Another prospect might say, “Our managers already have a dashboard.” Do not assume a dashboard solves the review burden. Ask, “How does a manager turn a dashboard signal into a coaching conversation?” The answer sometimes reveals a gap between seeing a number and choosing an action. A manager might see a low discovery score, yet lack a shared way to listen for the question a rep missed. A meeting with enablement gives people room to inspect this handoff without treating a score as a verdict.

The meeting invitation should make attendance feel deliberate. Avoid asking for “the right people” or “anyone involved with AI.” Name the roles connected to the decision. A short note might say, “You described managers skipping call review before coaching sessions. Would a twenty minute discussion with enablement, a frontline manager, and your recording policy owner help map the current review step and decide who should assess a focused practice?” Samira knows why each person belongs and what decision waits for them.

Set a modest agenda. First, ask a manager to describe one recent coaching meeting from preparation through follow up. Next, ask enablement where guidance exists for selecting a behavior to coach. Then ask the policy owner what questions need review before recorded calls or generated feedback enter a practice. No one needs to settle a large technology decision during this session. The group needs a shared picture of the work and a clear owner for the next decision.

During roleplay, have a colleague interrupt with a hard question. The colleague says, “Will this replace my managers?” Answer in one sentence, then return to a specific process. “Managers still make coaching judgments, so I would first learn where their review routine fails.” The colleague then says, “We need proof before we involve security.” Reply, “Who normally decides when security joins a conversation about recorded calls?” Your job is to earn a useful next step, not to win every objection.

Review the practice recording with a simple check. Count how often you asked a question before describing a capability. Listen for a claim about time, performance, or approval you did not receive from the prospect. Mark any moment where you changed the subject before learning who owns the workflow. Then rewrite one question in everyday language. This work helps an SDR sound prepared without relying on stock phrases.

In a fictional follow up, Leah sends Samira a note before noon on Tuesday. She writes, “You described managers missing call review before their coaching meetings, even though they still need to choose one behavior for each rep. I suggest a twenty minute working session with your enablement lead, one frontline manager, and the person who guides recording policy. We will map the review step and name the owner for any next assessment.” Leah opens her calendar, offers two specific times, and waits for Samira’s choice.