WhatsApp integration for Atlas
WhatsApp conversations connect to Atlas. Messages a consultant sends from their phone land against the candidate record, rather than in personal chat history. The thread sits with the calls and emails on that candidate, and it feeds Atlas Memory. Consultants message candidates on the channel they actually answer, and the agency keeps the record. If the consultant leaves, the conversation stays with the agency.
Live · Reviewed September 2026
What WhatsApp does
WhatsApp is a free private messaging and calling app, used on phones worldwide. Personal messages and calls carry end to end encryption, so only the people in the conversation can read them. It handles one to one threads, group chats, voice notes, and voice or video calls from the same place. Meta also runs WhatsApp Business, which companies use to reach customers at scale. For recruiters, the relevant part is reach. Candidates already have it open. It sits with the other phone and message connections on the Atlas integrations list.
What changes in your day
A candidate ignores two calls and an email, then replies to a WhatsApp message that afternoon. Most desks worked around that for years by moving the real conversation onto a personal phone. The thread now logs against the candidate record in Atlas instead. Salary expectations, notice period, the counter-offer they mentioned, the reason they went cold: all of it sits on the record. The next person to touch that candidate finds it.
Consultants leave. That is the part of the model nobody designs for, and it is usually the week the gaps show up. When the conversation history sat in one person's WhatsApp, the agency lost it with the laptop and the phone. Anything captured against the record stays where it was: the desk that inherits the candidates inherits the context too. Handover becomes a matter of reading, not asking around.
Nine months pass and the same candidate becomes relevant again. What was said on the call is there. What was typed into WhatsApp is there too, feeding Atlas Memory alongside the calls and the emails. The view of that candidate stops depending on which channel they happened to prefer. Nobody has to remember which thread the good detail was in. That is the difference between a warm approach and starting again.
Four candidates are through to second stage and all four want to know where they stand. The update goes out from Atlas, on the channel each of them reads. No separate app, no switching to a personal phone. The message is logged as it sends, so the record shows who was told what and when. Candidate control is mostly cadence, and cadence is easier to hold when messaging lives where the pipeline does.
The note nobody writes is the one after a WhatsApp exchange. It gets summarized into the record on Monday, or it does not. The version that survives is whatever the consultant remembered. That step is gone. No screenshot to paste, no summary to write up. The conversation was in the database when it happened.
How to turn it on
On your side you need a WhatsApp account for the consultants who will use it. Admin rights in Atlas cover the rest. From there, the team at Atlas customer support will switch it on for your account. The question worth settling first is a policy one. Which desks message candidates on WhatsApp today, and where the agency expects those conversations to be stored. Agree that before the first consultant starts messaging. Nothing needs to change about how consultants message. The point of the connection is that the record fills itself while they do it.
If you are working out the rest of the stack, the same write-up exists for Aircall and Devyce.
WhatsApp FAQ
Where do WhatsApp messages show up in Atlas?
Against the candidate record. The thread sits with that candidate's calls and emails. Anyone working the record sees the messaging history in the same place as the rest of the activity. Nothing has to be copied across by hand.
Can consultants carry on messaging candidates from their own phones?
Yes. Messages sent from a consultant's phone are captured against the candidate record in Atlas. The conversation becomes part of the agency's database rather than personal chat history. The device it was typed on stops mattering. Consultants do not change how they work.
What happens to the messaging history when a consultant leaves?
It stays with the agency. The thread was captured against the candidate record, not held on a personal phone. The desk that inherits those candidates inherits the conversation history too. Handover stops depending on what one person remembers to hand over.
Does WhatsApp content feed Atlas Memory?
Yes. Messaging captured through the integration feeds Atlas Memory alongside calls and emails. The picture Atlas holds of a candidate includes what was said in chat. Channel no longer decides whether a detail is remembered. The thread counts as part of that candidate's history.
Can we update candidates without leaving Atlas?
Yes. Candidates can be kept updated from inside the platform, on the channel they respond to. There is no switching between the CRM and a phone. Each message is logged against the record as it sends. Interview confirmations and offer updates land the same way.
Is WhatsApp secure enough for candidate conversations?
WhatsApp applies end to end encryption to personal messages and calls. Only the people in the conversation can read them. What the integration adds is a record. The exchange also exists inside the agency's database, and not only on a consultant's handset.
