The ATS Has the Record. But Does It Have the Conversation?
By Brett Dyess
I’ve used Google Voice for recruiting calls and texts for about fifteen years.
Not because I was trying to become an omnichannel recruiting visionary. I wanted to work from a normal-sized monitor, with a keyboard and mouse, instead of squinting at a stupid phone I can barely see.
I can have the résumé open. Check the calendar. Type like an actual human. And answer “Does Thursday at 2 work?” without picking up the most distracting device ever invented.
Desktop when I’m working. Phone when I’m moving.
Apparently, I’ve been passionate about omnichannel recruiting for years. I just didn’t know it had a name.
The interesting part is where the conversation lives
Google Voice made it easier for me to communicate from the computer where I was already doing the work. But convenience is only part of the story.
Recruit CRM’s SMS capabilities through Twilio, its WhatsApp integration, and Workable’s new native WhatsApp integration raise a bigger question:
Does the conversation live with the candidate—or somewhere the recruiter has to remember to look?
Recruit CRM documents SMS powered by Twilio and a native WhatsApp integration currently in beta rollout. Its WhatsApp messaging connects to candidate and contact profiles, with visibility controlled by message privacy settings.
Workable’s October 2 announcement describes sending and receiving WhatsApp messages inside the candidate record, with conversations saved alongside emails, notes, and evaluations. It is offered as a paid add-on.
Those are useful product developments. What interests me is the direction they point toward.
“Contacted” doesn’t tell me what happened
An ATS can show a perfectly respectable sequence:
Applied → Contacted → Screened → Interviewed → Offered → Hired.
That tells us where someone is in the process. It doesn’t necessarily tell us where we stand with the person.
Imagine a candidate texts: “Interested, but I can’t relocate until January.”
The ATS says: “Contacted.”
Both statements can be accurate. Only one helps me decide whether this particular opportunity makes sense right now.
The same problem shows up with compensation expectations, another offer, an unanswered question about travel, or a hiring manager’s promise to clarify the scope of the role.
If that context is scattered across texts, emails, calls, WhatsApp, social messages, and somebody’s notes, the record may be complete enough for reporting while the next conversation starts almost from scratch.
And when another recruiter takes over, “It’s in my phone somewhere” is not much of a knowledge-transfer strategy.
From record to engagement to intelligence
I see three useful layers:
System of Record: Who is this person, what role are we discussing, and where are they in the process?
System of Engagement: What have we said to each other, through which channels, and what needs a response?
System of Intelligence: Given that history, what should we understand—and what should we do next?
Each layer depends on the ones before it. A conversation still needs a reliable candidate record. Intelligence still needs accurate context.
Connecting the channels is a start. Preserving the meaning of the conversation is the more valuable step.
The January relocation example should help an advisor distinguish “not interested” from “interested at a different time.” A compensation discussion should make the next conversation more informed. A competing offer may change the timing of a hiring-manager decision.
These are examples of how I think the information could support better work. They are not claims that the integrations announced today automatically perform all of that analysis.
This is Talent Advisor 2.0 material
A Talent Advisor does more than move names between stages. The work includes understanding what the business needs, what the candidate wants, where those interests align, and what is getting in the way.
Conversation context is part of the evidence.
Used well, it could also become institutional intelligence. Repeated compensation concerns might suggest a role needs recalibration. Relocation conversations might expose a constraint in the hiring plan. Questions that keep coming up might tell us the job description is leaving something important unexplained.
That requires judgment. Three conversations are not a market study. An old preference is not necessarily a current one. A candidate’s words should remain distinguishable from a recruiter’s interpretation or an AI-generated summary.
The useful system would help the advisor see the source, check the context, ask a better question, and make a better decision. It would also respect who is allowed to see the conversation.
The human still owns the relationship—and the judgment about what the information means.
The next step is candidate context
Google Voice brought my recruiting communications onto my computer. The next step is bringing the relevant candidate context into the work itself.
I want less time reconstructing what happened and more time having a useful conversation about what happens next.
Your ATS may know who the candidate is. But does it know the conversation?
Google Voice, Recruit CRM, Workable — apparently I’ve been giving all three of you free publicity.
My PayPal information is available upon request. 😂