Here is a scene that plays out in recruiting teams every week. A candidate texts back at 4:45pm on a Friday. The recruiter who has been talking to her is out until Tuesday. The candidate takes another offer on Monday. Nobody else on the team knew the conversation existed because it lived on one person's phone. A shared inbox is the plain fix for this, and once teams try it, very few go back.
The problem with private threads
When candidate conversations happen from personal phones or individual email accounts, three things go wrong at once:
- Coverage. Replies arrive when the original recruiter is off, in an interview, or has left the company. The candidate waits, and waiting candidates leave.
- Context. A colleague picking up the thread has no idea what was promised, what was asked, or what the candidate already said. So they ask again, and the candidate feels like a number.
- Record. If the conversation is not on the applicant record, it does not exist for compliance, for handoff to the hiring manager, or for figuring out why a candidate dropped out.
Illustrative example: a staffing branch with five recruiters found that about one in six inbound replies arrived while the assigned recruiter was unavailable for more than four hours. That is not an edge case. That is Friday afternoon.
What changes when everyone sees everything
A shared inbox puts every SMS and email conversation with every applicant in one place, visible to the whole team, attached to the applicant record. In Apex ATS the thread reads like a chat, newest message at the bottom, with the resume, stage and notes one click away. A few things follow from that:
- Anyone can answer. Whoever is online picks up the reply. The candidate gets a response in minutes instead of days.
- Nobody needs a briefing. The full history is right there. "I see Priya mentioned you can start on the 3rd, does that still work?" is a much better opening than "Can you remind me where we left off?"
- Managers can coach. Seeing how conversations actually go is the fastest way to help a new recruiter get better, and to spot templates that need rewriting.
- Handoffs stop being a project. When someone goes on leave or leaves for good, their candidates do not go with them.
The objections, and honest answers
"My candidates are my relationships." They are, and the relationship is stronger when the candidate never gets left hanging. A candidate does not experience the difference between you and your teammate as a betrayal. They experience a fast answer.
"People will step on each other." This happens in the first week and then stops. The thread shows who replied last, and a two-line team norm ("if the owner is online, leave it; if not, reply and tag them") handles it.
"It feels like surveillance." It can, if it is introduced as monitoring. Introduce it as coverage instead, because that is what it is. Nobody objects to a colleague answering their phone when they are out sick.
Setting it up without drama
- 01Move all candidate messaging into the ATS. No more texting from personal numbers, even for the "quick ones." The quick ones are exactly the ones that get lost.
- 02Give the team one shared sending number, plus individual signatures inside the message so candidates know who they are talking to.
- 03Agree on a response-time target for inbound replies during business hours. One hour is realistic for most teams.
- 04Write down the two-line coverage norm and pin it somewhere.
- 05Review the inbox together once a week for the first month. Look for stuck threads and templates that get edited every time they are used.
A shared inbox is not a big cultural shift. It is a small operational one with an outsized effect on how fast candidates hear back and how much your team knows about its own pipeline. Set it up, run it for a month, and count how many Friday-afternoon replies get answered before Tuesday. That number is the whole argument.