Keka HR + AI Phone Interviews — Filling the Screening Gap
Keka is one of the most widely used HR platforms among Indian SMBs and mid-market companies, built around payroll, performance, and attendance, with Keka Hire as its recruitment and ATS layer. It's popular for good reason — clean UI, solid reporting, customizable hiring workflows, and it plugs straight into the rest of the Keka suite so a new hire moves from "offer accepted" to "on payroll" without a data handoff.
What Keka Hire doesn't do is talk to candidates. It tracks them, schedules them, and manages the pipeline around them — but the actual phone screen still has to be a person dialing a number.
That's fine at low volume. It becomes the bottleneck the moment you're hiring at scale — for BPO seats, field sales, delivery, or support roles where you're sourcing hundreds of applicants for a few dozen openings. This post looks at where Keka Hire's job ends and where AI phone screening picks up.
What Keka Hire does well
Keka Hire is a full applicant tracking system built into Keka's broader HRMS. It handles job requisitions, careers page postings, LinkedIn integration, candidate pipelines, interview scheduling, offer generation, and — because it's part of the same suite as Keka's payroll and onboarding modules — a clean handoff once someone's hired. Recruiters can build custom, stage-by-stage hiring workflows per role type, and reporting on pipeline health is a genuine strength: recruiters consistently point to Keka's tracking and analytics as one of the platform's best features.
Pricing is transparent relative to enterprise HRMS norms — Keka Hire runs on a per-recruiter-seat model, roughly ₹1,500-2,500/month/recruiter depending on plan tier, plus GST and a one-time setup fee. That's accessible for a growing Indian company, and if you're already running Keka for payroll or performance, adding the recruitment module keeps everything under one login.
For structuring a hiring pipeline, keeping candidate records organized, and reporting on funnel health, Keka Hire does exactly what it's built to do.
Where the gap shows up
The gap is the phone call — specifically, the first-round screen. Keka Hire can schedule an interview slot, send reminders, and log outcomes. It cannot dial a candidate, ask a structured set of screening questions, listen to the answers, and produce a score a recruiter can act on. That entire step sits on a human.
For senior or low-volume hiring — say, under 10 open roles a month — that's not a real problem. A recruiter making a handful of calls a week has time to do it properly. The math breaks down at volume. If you're running 300 applicants through the funnel for 20 BPO or sales roles, someone has to either call all 300 or guess which resumes are worth a call — and either choice costs you either recruiter hours or good candidates.
The quieter cost is missed calls. Indian candidates for hourly and entry-level roles frequently don't pick up unknown numbers, or are only reachable at specific hours. Without a systematic retry process, a missed call is usually just a lost candidate. Nobody tracks the leak because there's no visibility into how many qualified people simply never got called back.
Side-by-side comparison
| Feature | Keka Hire | Fawin | |---|---|---| | Core function | ATS + broader HRMS (payroll, performance, attendance) | AI screening — resume scoring + phone interviews | | Resume parsing | ✅ Structured parsing within ATS | ✅ AI resume screening with 0–100 ATS score | | JD parsing | Manual entry per requisition | ✅ Automated JD parsing to define scoring criteria | | Phone screening | ❌ Scheduling only, no call automation | ✅ AI voice agent conducts the interview | | Languages | Not applicable | English, Hindi, Hinglish | | Missed-call handling | ❌ None built in | ✅ 2 auto-retries, 24h apart, auto-refund if uncontactable | | Pricing model | Per-recruiter-seat, ~₹1,500-2,500/month + setup fee + GST | Credit-based, pay per screening use | | Payroll/onboarding tie-in | ✅ Native, part of Keka suite | Not applicable — screening layer only | | Integration model | Native within Keka, some third-party via API | Webhook-based, plugs into any ATS including Keka | | Best fit | Managing hiring pipeline through to payroll, one system | Screening high-volume applicants before recruiters get involved |
The two aren't competing — they're sequential
Teams sometimes treat "should we switch off Keka" as the question. It's usually the wrong question. Keka Hire and an AI screening layer sit at different points in the funnel, and stacking them works better than replacing either.
A practical flow: candidates apply through Keka's careers page and land in the pipeline as usual. Before a recruiter opens a resume, it runs through AI screening for an ATS score against the JD. Candidates who clear the threshold get an automated phone interview — in the language they're comfortable with — instead of sitting in a queue waiting for a recruiter to find a callback window. The transcript, score, and recommendation feed back into Keka Hire via webhook, so the pipeline stays the single system of record for status, history, and eventual handoff to payroll.
Recruiters keep ownership of the pipeline, the shortlist interviews, and every final call. What changes is that they're reviewing candidates who already cleared a resume score and a structured phone screen, instead of manually triaging a raw applicant list one resume at a time.
What this actually saves
For a team hiring 20-30 people a month in high-volume roles, the practical impact is a few hundred recruiter-hours a month that stop going into cold-calling and start going into offer negotiations, hiring manager alignment, and final-round interviews. It also plugs the missed-call leak — candidates who don't answer the first attempt get called again automatically, on a fixed schedule, instead of quietly disappearing from the funnel.
None of this requires ripping out Keka. It requires putting a screening layer in front of it that does the two things Keka Hire wasn't built to do: score resumes against a JD automatically, and run the phone screen without a recruiter dialing the number.
That's the specific gap Fawin fills. It plugs into an existing Keka Hire setup over webhooks — no migration, no disrupting a payroll and HR system your team already relies on. Resumes get an AI-generated ATS score, and shortlisted candidates get an AI phone interview in English, Hindi, or Hinglish, with automatic retries for missed calls and a refund if a candidate is never reached. Keka stays exactly where it is as the system of record; it just stops being the place where screening work quietly piles up.