Your recruiter phone screen script, rewritten

On 1 October 2026 we corrected our own blog. Some older posts had described our pilot’s 89 percent saving as being against manual phone screens. It was not. The 89 percent was real, but it compared against about 18 hours of reading profiles for a 3,000-applicant drive. Phone-screening those same 3,000 people at 10-15 minutes a call would take 500-750 hours. The phone screen was never a baseline anyone at that volume could actually run. It was the step they skipped.

That arithmetic is why so many teams are moving the first round from a recruiter’s phone to a structured voice interview. The work that moves with it is the script: the list of recruiter phone screen questions that lived in a document, or in one senior recruiter’s head. This post sorts a typical script into what to keep, what to cut and what to rewrite, then gives a template you can copy. It opens a series on how one voice interview replaces the recruiter phone screen. The other four posts cover how to assess communication skills without a phone call, structured vs unstructured interviews, how many candidates to shortlist and what an AI interview agent does.

What questions should a recruiter phone screen include?

A recruiter phone screen should include two or three knockout questions with yes or no answers (location, shift, notice period), three or four job questions scored on a written scale, one or two checks of resume claims, and time for the candidate’s questions. Cut anything that only builds rapport or that the law says not to ask.

Most scripts mix these four kinds of question together. Sorting them is the whole job, because each kind is asked, answered and scored differently.

Sort every question into one of five buckets

Take your current script and put every question into one bucket:

1. Knockouts. Facts that end the process if the answer is wrong: can work the night shift, can join within 30 days, is willing to work from the Pune office. Answer format is yes or no, or a number.
2. Scored job questions. Questions that show whether the person can do the work: “Tell me about a time a customer was angry with you. What did you do?” These get a rating scale.
3. Resume checks. Confirming what the resume says. SHRM’s guide to effective phone screens suggests confirming employment dates and asking about specific, quantifiable claims like “supervised eight staff members.”
4. The candidate’s questions. What the job pays, how many rounds, whether freshers are hired. Not scored, but skipping them loses good candidates.
5. Cut. Small talk, “where do you see yourself in five years,” and anything illegal or irrelevant.

A typical script, sorted

Here is a common 12-question recruiter script for a customer support role, with what happens to each question:

That leaves two or three knockouts, four scored questions, one resume check and the candidate’s question time. About 10-15 minutes, every time.

Rules for rewriting each question

One question, one purpose. “Tell me about your experience and why you want this job” is two questions with two scores. Split it.

Ask for an example, not an opinion. “How do you handle pressure?” gets an opinion. “Tell me about the busiest day you had last month” gets a story you can score.

Write knockouts as a plain sentence with the condition. “Must be able to join within 30 days.” If you cannot write the condition down, it is not a knockout; it is a preference.

Never knock out on a vague answer. “Maybe, depends on the offer” to a relocation question is not a no. It goes to a person.

Keep the law in the room. The EEOC’s guidance on pre-employment inquiries says questions should be limited to what is essential for determining whether a person is qualified, and bars pre-offer questions about disability. A script written down in advance is easier to check than a recruiter improvising on call 40 of the day.

The template: copy and adapt

ROLE: Customer support associate, Pune office, rotational shifts

KNOCKOUTS (yes or no; a vague answer goes to review, never auto-reject)
K1. This role works rotational shifts, including nights. Can you work those shifts?
K2. Can you join within 30 days of an offer?
K3. The role is based in our Pune office, five days a week. Does that work for you?

SCORED QUESTIONS (0-10 each, anchors written below)
Q1. Walk me through your last role. What did a normal day involve?
Q2. Tell me about a time a customer was angry with you. What happened, and what did you do?
    Anchors: 2 = blames the customer or no example; 5 = a real example, a sensible fix;
             8 = a real example, a fix, and what they changed afterwards
Q3. Tell me about the busiest day you had in the last month. How did you decide what to do first?
Q4. Why this role, and why now?

RESUME CHECK
R1. Your resume says you handled about 60 tickets a day at your last job. What kind of tickets?

CANDIDATE QUESTIONS (prepared answers)
Rounds: two after this one. Freshers: yes, for this role. Shift allowance: yes.

What the phone call did that a voice interview does not

Be honest about the trade. A recruiter on the phone can sell the role to a strong candidate who is wavering, hear that someone is in a noisy bus and offer to call back, and pick up a thread nobody planned for. A structured voice interview does none of that by design. It asks the same questions of everyone, which is the point, and it means the persuading and the unplanned conversation move to the next round. Keep a human call for the shortlist, where those things matter most. We cover where that conversation goes in how to shortlist candidates when nobody phones them first.

Running the script as a voice interview in HireQwik

In HireQwik, the script above becomes a job’s screening setup. HireQwik drafts the setup from the job description and HR reviews it: knockouts become deal-breaker questions written as plain sentences (“must be able to join within 30 days”). Scored questions come from the job and the candidate’s resume, and a conversational mode asks up to 12 questions naturally, following up when an answer is vague. The candidate takes it as a 10-20 minute voice interview in their browser, at a time they book.

When a knockout rejects someone, the reason quotes the candidate’s own words. If that quote cannot be found in the full transcript, the candidate goes to On Hold for a person to check, never straight to rejection. At the end, candidates can ask about the company, and the answers come from the company information you add, so “how many rounds?” is answered from the same source every time. Every interview keeps its recording and transcript, and HR makes the decision. Take the live AI interview to hear a script like this one run, or compare it with our phone screen interview guide if you are still running the calls yourself.