Every ATS advertises an integration count. The number is close to meaningless, because integrations differ enormously in depth and the count treats a full two-way calendar sync and a webhook that posts a notification as equivalent.
Four integrations carry most of the practical value. Everything else is optimisation.
1. Calendar
The highest-value connection by a wide margin, because scheduling is where elapsed time actually accumulates. In most funnels the gap between deciding to interview and the interview happening is larger than every other delay combined.
What good looks like: real-time availability for every interviewer, invitations created with the candidate and the interviewer both on them, rescheduling that updates both sides, and self-scheduling links so the candidate books directly into open slots.
What shallow looks like: a calendar file attached to an email. That is a notification, not an integration — it does not know who is free.
The test question: can a candidate book their own interview into a genuinely free slot without a coordinator touching it? If not, scheduling is still manual.
2. Team chat
Hiring decisions stall waiting for people who do not open the ATS. Chat integration moves the request to where those people already are.
What good looks like: notifications when a candidate needs a decision, scorecard reminders before a debrief, and the ability to act — approve, comment, advance — without leaving the conversation.
What shallow looks like: a channel filling with every stage change. Notification volume that nobody reads is worse than no integration, because it trains people to ignore the channel.
3. Video interviewing
What good looks like: a meeting link generated automatically when the interview is scheduled, present on both the candidate and interviewer invitations, and the recording — where used — attached to the candidate record with the same retention rules as everything else.
That last point is the one that gets missed. Recordings held in a separate video platform sit outside your retention policy and outside your deletion process. If a recording survives the deletion of the application it belongs to, your retention policy is not being applied.
4. Job distribution
What good looks like: one posting action that publishes to your careers page, the boards you use, and the structured feed that makes the role eligible for Google for Jobs — with the source recorded on every application that comes back.
Source attribution is the part that matters and the part most often missing. Without it, channel analysis is impossible, and channel budget is allocated on impression.
The ones worth less than they appear
- HRIS sync. Genuinely useful, but it fires once per hire. Valuable at scale; irrelevant to the daily workflow.
- Background check providers. Useful where checks are routine, otherwise a link is enough.
- Assessment platforms. Worth it only if results return to the candidate record automatically. Otherwise it is a bookmark.
- Long integration directories. A hundred shallow connections and four deep ones is a worse product than four deep ones alone.
Three questions to ask about any integration
- Which direction does the data flow? One-way is a notification. Two-way is an integration.
- What happens when it fails? Silent failures are the worst case — a scheduling integration that drops an invitation without telling anyone costs you a candidate and nobody finds out for a week.
- Does candidate data leave the system? Every integration that receives candidate data is a processor to list in your privacy notice, and possibly a cross-border transfer to account for: data residency.
That third question is why an integration count is a poor buying signal. Each connection is a data-sharing relationship, and more of them is not automatically better.
For what Hireall connects to and how deeply, see integrations.