WhatsApp ATS integration

A WhatsApp ATS integration is a native connection between an applicant tracking system and WhatsApp. It lets recruiters send and receive WhatsApp messages directly from each candidate profile inside the ATS, instead of switching to their phone or a separate browser. Every message, attachment and voice note is logged on the right candidate, tagged to the right project, and visible to the team. With Jarvi, the integration uses your existing WhatsApp number through the WhatsApp Web protocol, with no Cloud API, no Meta Business verification and no per-message fees.

With Jarvi, integrating WhatsApp with your ATS takes under two minutes and three steps. Open Settings, then Emails, calendars and phones. Click Connect an account and pick WhatsApp. Scan the QR code from your phone, the same way you would for WhatsApp Web. Your existing conversations sync automatically and attach to the right candidates when a phone number matches. From there, every recruiter on the team can link their own WhatsApp number and start messaging from any candidate profile.

Recruiters integrate WhatsApp with their ATS to talk to candidates where they actually reply, while keeping the conversation logged inside the recruitment pipeline. WhatsApp gets opened in minutes and replied to in hours, where email and LinkedIn typically take days. Bringing it inside the ATS solves the side effects: no more conversations stuck on a personal phone, no more lost context on team handover, no more compliance gap on candidate data. Reply rates go up, time-to-hire goes down, and the audit trail stays clean.

Native WhatsApp integration is still rare among ATS vendors. Most ATS platforms either offer no WhatsApp support, or rely on paid add-ons through the WhatsApp Cloud API, which means a new number, Meta verification, per-message fees and a 24-hour reply window. Jarvi is one of the few ATS to ship native WhatsApp out of the box, with your existing number, on every paid plan, with no Cloud API setup.

Yes, with Jarvi WhatsApp can be a step in any automated sequence: first contact, follow-up, interview reminder, post-interview check-in, rejection, post-placement check-in. Sequences auto-stop the moment a candidate replies, so the conversation switches back to the recruiter without any spam risk. Variables like first name, role, client and interview slot are substituted at send time.

Yes. Jarvi hosts data in the EU on SOC 2 Type 2 certified infrastructure, encrypts messages in transit and at rest, and keeps a full audit trail of every WhatsApp action. Each candidate file can be erased in one click, including the full WhatsApp history, and retention is configurable per project. Recruiters keep per-account access control so WhatsApp conversations stay scoped to the right project owners.

Neither. Jarvi connects to your existing WhatsApp account via the same QR code flow as WhatsApp Web. You keep your number and your contacts. No Business API setup and no per-message Meta fees. Works with both standard WhatsApp and WhatsApp Business.

No. WhatsApp messaging is included on every paid Jarvi plan. No per-message Meta billing and no template approval to go through.

Yes. Every recruiter on the team links their own number via their own QR code. Conversations stay tied to the recruiter who owns the candidate relationship, even on shared projects.

WhatsApp's terms allow regular use of the Web protocol, which is what Jarvi uses. Risk goes up the moment you send mass cold blasts to lists of unknown numbers, which is where accounts get flagged. Jarvi enforces human-paced sending and respects WhatsApp's rate limits by default. In normal recruitment usage, ban reports are extremely rare and typically tied to mass cold outreach, which Jarvi prevents by design.

In most EU markets, yes. You need a legal basis: consent, legitimate interest with a clear opt-out, or a pre-existing relationship. Jarvi keeps the trail traceable, with project tagging and one-click erasure. We recommend stating who you are and where you got the candidate's number in your first message.

Yes. Every message, attachment and voice note is archived on the candidate profile and tagged to the right project. The audit trail logs each action with its channel, timestamp and user. Retention follows your GDPR settings.

Yes. WhatsApp can be a step in any Jarvi sequence: first contact, interview reminders, post-interview follow-ups, rejections, post-placement check-ins. Sequences auto-stop the moment a candidate replies. A recruiter can take over the conversation manually at any point.

Yes. Resumes, job descriptions, salary grids, images, voice notes. Everything supported by WhatsApp is supported by Jarvi.

Replies surface in your Jarvi inbox and through push notifications. Nothing is lost, and nothing has to be re-typed from your phone.

Yes. Jarvi has a single plan and WhatsApp is included, with no add-on or extra fee.

Jarvi follows WhatsApp's own pacing limits, which are built for human use, not bulk marketing. In practice, an active recruiter sending personalised messages will not hit a ceiling. If you are moving toward bulk send territory, our team will help you set up the right configuration before you scale.

Yes. Each candidate profile can be exported, and admins can extract full conversation logs at any time for audits, compliance reviews or candidate-erasure requests.