A dialer built into your ATS, not bolted onto it

Calls happen outside the ATS, so the ATS is always out of date

A recruiter dials a candidate from their mobile or a separate softphone. The call happens, but the ATS never hears about it — no duration, no outcome, no note — unless the recruiter stops to type it up afterward, which is the first thing that slips on a busy desk. Managers end up reporting on activity nobody logged, and a promised callback lives in someone's memory instead of a dated follow-up.

Every candidate call starts and ends inside the ATS

Your ATS syncs a thin candidate list to WebCallHub — id, name, phone, job, owning recruiter, no résumés or notes — and a Call button appears next to each one. The call itself, and its outcome, write straight back.

One click, company number shown

The recruiter's browser or desk phone rings first, then the candidate — showing a company number, never the recruiter's personal mobile. A dialer covers numbers not yet in the system.

Candidates reach their own recruiter

A candidate calling back the company number is identified by their phone number and routed to the recruiter who owns them, ahead of the general desk.

Every call becomes a record

Direction, length and status are logged automatically — including calls nobody answers — plus an outcome the recruiter picks from a fixed list (interested, not interested, callback, interview scheduled, no answer, wrong number, left voicemail, not reachable) with free-text notes.

A callback is a date, not a memory

Picking "callback" creates a dated follow-up instead of a note nobody counts. Recruiters see today's calls, connect rate and talk time; managers see the whole desk by recruiter and by outcome.

What a calling desk actually needs

• A recruitment or staffing desk that dials candidates from its own ATS all day, not occasionally
• A manager who wants call volume and outcomes reported per recruiter, not reconstructed from memory
• A desk that wants candidates routed to the recruiter who owns them, not a shared queue
• Recordings that need to live in the customer's own S3 with server-side encryption and a retention rule
• A team migrating off a separate power-dialer tool that never wrote back to the ATS at all

Frequently asked questions

What is a recruiter dialer with ATS integration?

A recruiter dialer is click-to-call built into the applicant-tracking system recruiters already work in, rather than a separate phone app: a Call button next to each candidate rings the recruiter first, then the candidate, and writes the call's outcome back to that candidate's record automatically. WebCallHub's version is the Calling Desk plan (formerly called Recruiter Desk — same plan, same prices; per seat from $39/seat/month, 500 PSTN minutes per seat pooled) — the same plan sold to auto sales, insurance and property desks, built specifically for recruitment and staffing desks here; Business ($79/month) and Enterprise also support outbound calling and the same webhook for smaller teams.

Which ATS does this connect to?

There is no prebuilt, named connector for Bullhorn, Greenhouse, Workday or any other ATS — the integration is WebCallHub's API plus a webhook (or a poll, for an ATS behind a firewall) that the ATS's own developer wires up, typically an afternoon's work, not a project. A runnable demo of the flow — sign up, buy a number, mint an API key, sync candidates, add the Call button, connect the webhook — is at webcallhub.com/demos/ats-navetech.html.

What gets written back to the candidate record?

Every call, including ones nobody answers: direction, duration, status, the outcome the recruiter picked from a fixed list (interested, not interested, callback, interview scheduled, no answer, wrong number, left voicemail, not reachable), and free-text notes. A callback outcome creates a dated follow-up. As a separate event — because it happens after the call ends — the outcome and any follow-up date post back too. Optionally a call.started event can pop the candidate in the ATS the moment the phone starts ringing.

Is this the same as WebCallHub's AI receptionist for recruitment agencies?

No — they solve opposite directions of the same problem. The AI receptionist (webcallhub.com/recruitment-agencies) answers INBOUND calls when your desk is empty, evenings and weekends. This is the recruiter's own OUTBOUND dialer for candidates they are calling. A desk can run both.

What does it cost?

The Calling Desk plan (formerly Recruiter Desk) is sold per seat from $39/seat/month ($34 from 5 seats, $29 from 10, $25 from 25, $21 from 50), with 500 PSTN minutes per seat pooled across the desk and $0.04/minute beyond that. It is self-serve up to 200 seats; larger desks are quoted. Outbound calling and the ATS webhook are also included on Business ($79/month) and Enterprise. Free, Starter and Growth cover inbound website calls only.

What can't it do?

Being honest about the limits: there is no power or predictive dialer, no local-presence number pool, no call whisper, barge or coaching, and nothing pushes to the ATS in real time — the ATS polls WebCallHub's API for new call records (or receives a webhook). Outbound calls are recorded only when the workspace sets recording to always-on, since there is no widget for a candidate to consent through on an outbound call.

Put a Call button next to every candidate

See the flow end to end at the ATS demo, then talk to sales about the Calling Desk plan for your desk.