SDR Mock Cold Call Interview: A Script You Can Adapt
An SDR mock cold call interview is a role-play where you contact someone who was not expecting your call. The interviewer plays the prospect. Your task is to introduce yourself, give a relevant reason for calling, listen to the reply, and decide whether a follow-up would be useful.
This worked example gives you a short script to practice, plus different responses for a busy prospect, an existing provider, and a clear refusal. Learn the purpose of each part so you can change your words when the conversation changes.
Check the brief before choosing your script
Ask what you are selling, who you are calling, how long you have, and what the exercise should accomplish. Confirm whether notes are allowed. Use the employer’s instructions if they differ from the example here.
For the wider interview, use our SDR interview question guide. This exercise focuses on the first conversation with a prospect.
A mock cold call example you can practice
Imagine you sell HarborDesk, a fictional tool that puts customer inquiries in a shared inbox and lets a team assign each inquiry to a person. The practice brief says Jordan manages customer support at a company that is hiring more support staff.
You have not spoken with Jordan before. The hiring is a reason to ask about the team’s process, not proof that anything is wrong. All names, product details, and buyer answers below are invented for practice.
1. Introduce yourself and explain the interruption
You: “Hi Jordan, this is Sam from HarborDesk. This is a cold call. Could I take 30 seconds to explain why I reached out, then you can tell me whether it is relevant?”
Jordan: “Okay, briefly.”
Pause for the answer. If Jordan agrees to a short explanation, keep that promise.
2. Give a reason and ask one question
You: “I saw you are hiring more support staff. HarborDesk gives teams a shared inbox where each inquiry has an owner. How are you keeping track of who handles each customer inquiry today?”
Jordan: “We use a shared email account. Sometimes two people reply to the same customer.”
You connected a checked fact to a question. You did not claim that hiring automatically creates a problem.
3. Follow the answer before asking for a meeting
You: “When two people reply, what does that create for the team?”
Jordan: “Mostly confusion. We have to check who is handling it.”
You: “Is that something you want to improve as the team grows?”
Jordan: “Yes, we have been discussing it.”
The prospect has now described a problem and an interest in improving it. That supports a next-step suggestion. It does not establish a budget, buying authority, or a qualified opportunity.
4. Suggest a follow-up with a clear purpose
You: “Would a 15-minute conversation be useful to look at how assigning an owner could fit your team’s process?”
Jordan: “Possibly. I would want our support lead there.”
You: “That makes sense. What time would work for both of you?”
The meeting has a purpose based on Jordan’s answer. Confirm the agreed details before finishing. The 15-minute suggestion is part of this example, not a requirement for every interview.
Keep brief notes afterward: Jordan reported duplicate replies, wants to review the process, and would involve the support lead. Budget and purchase timing remain unknown. Do not turn an agreed conversation into a claim that you have won a customer.
Change your response when the prospect changes theirs
Use these as alternative practice rounds. You do not need to deliver every response in one call.
“I’m busy.”
You: “Understood. Would another time suit you, or should I leave it here?”
Jordan: “Try Thursday afternoon.”
You: “Would 2 p.m. work for a brief call?”
Confirm a time only if Jordan welcomes the callback. If they want to end the call, finish politely.
“We already have a provider.”
You: “Understood. How is the current setup working for your team?”
Jordan: “It is working well, and we are not considering a change.”
You: “Thanks for letting me know. I will leave it there.”
You gave the prospect room to explain. You did not criticize a competitor or invent a reason they should switch.
“Just send me some information.”
You: “Happy to. Would a short overview of assigning inquiries be useful, or is there something else you want to see?”
Jordan: “The assignment part would help. I am not ready to book anything.”
You: “Understood. I will send that overview.”
Send the relevant approved material through the agreed channel. A request for information is not an agreement to a meeting or repeated follow-ups.
“I’m not interested. Please don’t call again.”
You: “Understood. I will note that you do not want further calls. Thanks for your time.”
Stop the pitch. Respecting a clear refusal is part of the exercise, even when it means you do not book a meeting.
Practice once, get feedback, then try again
Ask a friend to play Jordan and choose one response without telling you which. Use the employer’s time limit if you know it. Otherwise, a short practice round is enough to rehearse the opening and one branch.
Review these five questions:
Did I explain who I was and why I called?
Did I use information from the brief without inventing product claims?
Did my next question follow the prospect’s answer?
Did I suggest a next step that fit what I heard?
Did I respect the prospect’s time and any clear refusal?
Choose one change for the next attempt. If your partner says you asked too many questions at once, redo that moment with a single question: “How do you assign inquiries today?” Then pause. The improvement should be something your partner can hear.
If you record a practice round, get your partner’s permission. You can also use Salesforce’s cold-call practice guidance for ideas on varying the prospect’s level of interest.
If your interviewer asks for a longer needs discussion, move to our mock discovery call example. For other assessment formats, see sales interview assessments.
Ready to walk into your next interview with confidence?
The Confident Interview Method gives you a focused, one-hour way to choose stronger examples, answer difficult questions, and speak clearly without memorizing a script. Start here if you want a complete preparation process you can reuse before future interviews.
The Confident Interview Method
$29
One focused hour with 10 practical lessons you can use in your very next interview.
“After spending hours reading blogs and articles, I am so glad that I bought this. It covered what I think are the most important parts of interviewing. Thanks for making this so concise.” - Drew Whitehead
Prefer a faster, lower-cost option?
The Interview Playbook eBook gives you practical strategies for preparation, communication, body language, and interview practice that you can start using right away.
Frequently asked questions
Should I memorize a script for an SDR mock cold call?
Know your opening and the purpose of your questions. Practice with different replies so you can listen and adapt. A word-for-word script is difficult to use when the prospect interrupts or gives an unexpected answer.
Do I have to book a meeting to pass?
There is no universal pass rule. Ask about the employer’s expectations. A meeting can be an appropriate goal, but do not force one when the prospect has no relevant need or clearly wants to end the call.
What if I do not know the answer to a product question?
Say you would need to check before confirming it. For example: “I would want to verify that integration before promising it. Which system would it need to work with?” Keep the unknown visible in your notes.
Is a mock cold call different from a discovery call?
A cold-call exercise starts with an unexpected contact and tests whether you can earn a relevant conversation. Discovery usually explores the needs of someone who has agreed to speak. Employers may combine the two, so follow the actual brief.
Comments