1. Confirm role interest
Which role are you applying for?
Workflow Template
Candidate screening call app template
Screens applicants by phone for availability, experience, eligibility, salary range, and fit before recruiter review.
Best fit
- Recruiters
- Hiring managers
- High-volume roles
Do not use it for
- Discriminatory screening
- Final hiring decisions
Call flow
2. Ask availability
When could you start?
3. Screen requirements
What relevant experience should the recruiter know about?
4. Capture salary range
Which role are you applying for?
5. Save recruiter summary
When could you start?
Prompt template
Screen job candidates by phone. Ask role interest, availability, relevant experience, basic eligibility, salary range, and questions for recruiter. Avoid discriminatory questions. Save a screening record.Questions asked
- Which role are you applying for?
- When could you start?
- What relevant experience should the recruiter know about?
Human handoff
- Accommodation request
- Sensitive legal eligibility question
- Candidate asks for recruiter
Structured output schema
{
"outcome": "Candidate screening outcome",
"fields": [
{
"description": "candidate name captured during the call.",
"name": "candidate_name",
"required": true,
"type": "date"
},
{
"description": "phone number from caller id captured during the call.",
"name": "phone_number_from_caller_id",
"required": true,
"type": "text"
},
{
"description": "role captured during the call.",
"name": "role",
"required": true,
"type": "text"
},
{
"description": "availability captured during the call.",
"name": "availability",
"required": true,
"type": "text"
},
{
"description": "experience summary captured during the call.",
"name": "experience_summary",
"required": true,
"type": "text"
},
{
"description": "work authorization captured during the call.",
"name": "work_authorization",
"required": false,
"type": "text"
},
{
"description": "salary range captured during the call.",
"name": "salary_range",
"required": false,
"type": "text"
},
{
"description": "fit notes captured during the call.",
"name": "fit_notes",
"required": false,
"type": "text"
}
]
}Transcript example
AI: Hi, I am an AI call workflow for Candidate screening. Which role are you applying for?
Caller: I am applying for the customer support role.
AI: When could you start?
Caller: I can start in three weeks and have two years of support experience.
Recommended integrations
AirtableNotionSlack
Launch review
Caller promise
Make the first screen and opening line match what the caller will actually get. For Candidate screening, the promise should be narrow enough that a caller understands the purpose before sharing details or scanning a QR code. Avoid broad claims like "we can help with anything"; a specific promise produces cleaner calls and clearer follow-up.
Required outcome
Decide which fields are required before the call can be considered complete. A practical first version should capture candidate name, phone number from caller id, role, then send a summary that the workflow owner can act on without replaying the call. If a field is not used for routing, qualification, scheduling, or review, remove it from the first launch.
Human review
Write down the cases that should not be automated. Use human review for accommodation request, sensitive legal eligibility question, candidate asks for recruiter so the workflow stays useful without pretending to handle every edge case. Review the first real calls before connecting higher-risk actions or expanding the workflow.
FAQ
When should I use a candidate screening Call App?
Use it when the call is repeatable, the team already knows the information they need, and the caller benefits from speaking instead of filling out a form. It works best for recruiters, hiring managers, high-volume roles.
What should the AI ask first?
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "Which role are you applying for?". Keep follow-ups short so the caller does not feel like they are reading a form over the phone.
What output fields should be saved?
Save a structured result with candidate name, phone number from caller id, role, plus a summary, completion status, and handoff reason when needed. The owner should be able to act on the result without interpreting raw transcript text.
What should trigger human handoff?
Human handoff should trigger when the caller needs judgment, asks for a person, gives conflicting answers, or matches one of the workflow-specific rules: accommodation request, sensitive legal eligibility question, candidate asks for recruiter.
Clone this template
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.