Recruitment operations
Recruitment Slack and Email: How to Run Both Without Losing CVs
By Andre · · 14 min read
Recruitment Slack and Email: How to Run Both Without Losing CVs

Use Slack for conversation and decisions about a hire, and keep every CV in one searchable candidate database fed from your hiring inbox. Slack is where your team talks about a candidate. Email is where the candidate’s CV actually arrives. Problems start when a CV lives only in a forwarded message or a chat thread that nobody can find three weeks later. Below you will find how to set up Slack channels for hiring, how to move email into Slack, what to keep out of chat, and how to give each tool one clear job.
TL;DR
- Create one private Slack channel per open role and, at interview stage, one per candidate. Pin the job listing and the deadlines.
- Forward or route email into Slack for discussion only. The CV itself should sit in a single searchable record, not in a chat thread.
- Never paste candidate details into general channels. Post a link to the record and keep the conversation around it.
- Give each tool one job: the inbox receives, the candidate database stores and searches, Slack discusses and decides.
- If CVs come in through a shared mailbox, we built RecrutFlo to read the attachments and build the profiles for you, so Slack stays light.
Table of Contents
- What Slack does well in hiring, and what it does not hold
- Set up Slack channels for each role
- Getting email into Slack
- Where the CVs should live
- A working routine, step by step
- Keep candidate data safe in chat
- Who owns what: Slack, email or a database
- What to automate first
- Start with the inbox, then the channel
- Our perspective
- FAQ
- Sources
What Slack does well in hiring, and what it does not hold
Slack’s own hiring guidance treats the channel as the basic unit of collaboration. A single point of collaboration for each role means faster decisions and quicker answers to candidates, and the searchable history of the channel doubles as a record of how the hire was made.
The practical gain over email threads is easy to see in a story Slack tells about Shopify. When an interviewer dropped out at the last minute, the replacement was invited into the channel and found the candidate information and interview questions already there. In email you would forward a chain of messages and hope nothing was missed.
What Slack does not do is receive applications. Candidates apply by email, so the first thing that happens to a CV is that it lands in a shared inbox: a PDF or Word attachment on a message with a subject line like “Application for sales role”. Slack never sees it unless someone forwards it. That gap is where small teams lose track of people.
Set up Slack channels for each role
A simple structure keeps hiring talk findable. Slack recommends a private channel for each position, with the job listing pinned and the lead recruiter and deadlines in the channel purpose. Here is how to apply that on a small team.
- Name the channel by role. Use something like #hiring-sales-manager. A consistent pattern lets anyone find it with search.
- Create it before the job is posted. Slack’s HR handbook suggests opening the channel early so hiring managers, department leads and recruiters can agree on scope, salary band and title and finalize the job description together.
- Pin the job description and write the purpose line. Name the lead recruiter and the dates for the first shortlist and for offers.
- Add a second channel for interviewers. Slack’s guide advises a separate channel where interviewers coordinate logistics and topics to avoid duplicate questions and gather feedback.
- Use a candidate channel at interview stage. Slack suggests naming it interview-[candidate name] and pinning the résumé at the top, which works for scheduling and debriefs.
- Archive when the role is filled. The same guide recommends archiving related channels so the workspace stays tidy.
For offers, Slack’s HR resource proposes private channels for compensation discussions per person, such as #offer-name, plus an #hr-team channel for strategy and compliance, all described in Slack for HR, Recruiting, and DEI. Keep pay talk out of any channel where people not involved in the hire could read it.
Threads help too. The same resource describes using threads for an organized, searchable discussion around each shortlisted candidate, and reactions to pick interview slots. One thread per candidate in the role channel means feedback stays attached to the right person.
Getting email into Slack
Teams ask this most often: how do I get the email into Slack? There are three common ways, and each suits a different amount of volume.
Forward single emails
Slack introduced Outlook and Gmail add-ins that let you forward important emails, along with attachments, straight into Slack. For Gmail, HubSpot’s walkthrough describes installing the Slack add-on, opening the email, clicking the Slack icon, choosing the person or channel and adding a note. It takes seconds and suits the odd email, such as a hiring manager’s reply or a referral.
Subscribe a channel to notifications
If your applicant tools send email notifications, many can push them to a channel instead. Slack’s recruiting blog notes that one applicant tracking system’s Slack integration can send new candidate, referral and scorecard-due alerts to users or a channel, cutting inbox clutter. The principle applies to any tool: let a system alert the channel, and keep the record in the system.
Automate routing by rule
Automation services can watch a mailbox, filter by sender, subject or attachment and post a message into a channel. That suits alerts such as “new application received”. It is a poor place to store CVs, because each message is just text in a stream.
A caution that applies to all three: forwarding is manual, and manual steps get skipped on busy days. If your volume is more than a few applications per role, you want the inbox itself to do the sorting.
Where the CVs should live
Chat is built for conversation, which scrolls away. A CV is a document you need to find again by skills, location, language or role, sometimes months later for a different vacancy. Slack’s search will find a file name if someone remembers it. It will not tell you who in the pile speaks German, has five years of warehouse experience and is available in January.
That is the job of a candidate database. We built RecrutFlo for teams whose applications arrive in a shared mailbox. It connects to Microsoft 365, Outlook and IMAP mailboxes, finds the CV attachments in incoming email, reads PDF, DOC and DOCX files, and pulls out contact details, experience, skills, languages, location, role context, salary expectations and availability. Each candidate becomes a searchable profile, and duplicates are flagged, so the same person applying to three roles does not appear as three strangers.
The result for your Slack workflow is simple. When the hiring manager asks “who else did we see for this kind of role?”, you search the database instead of scrolling a channel or digging through forwarded messages. If you want to see how this fits a small team’s mailbox, our guide to setting up a hiring inbox walks through it, and the article on automating candidate intake covers the intake step in detail.

A working routine, step by step
Here is a routine a five-person team can run without extra software beyond the inbox, the candidate database and Slack.
- Publish the role and open the channel. Post the job, pin it in #hiring-[role], and name the lead recruiter.
- Let applications land in the shared inbox. Use one dedicated address for the role or the team, not personal inboxes. Our piece on shared inbox permissions lists what to check about who can see what.
- Turn email into records. RecrutFlo reads the attachments in that mailbox and builds the profiles, so nobody retypes names and phone numbers. This is the step where manual data entry disappears, and the step that is easiest to get wrong in a forwarding-only setup, because a CV that nobody forwarded is a CV nobody considered.
- Search, then shortlist. Filter by skills, experience, languages, location and role. Our candidate search best practices shows how to phrase searches for small pools.
- Discuss in Slack. Post the shortlist in the role channel, one thread per candidate, each with a short summary and a reference to the record. Decisions and feedback go in the thread.
- Schedule. One public example is Sourcegraph’s recruiting handbook, where the team requests availability by email or through its applicant system, then submits a scheduling request form in a Slack channel and tracks coordinator updates with emoji. The idea carries over: email reaches the candidate, Slack coordinates the team.
- Close and archive. Archive the Slack channels, and make sure the outcome is noted on the candidate’s record, not only in chat.
For agencies, the same flow applies with client channels in place of internal ones. Our staffing agency email workflow shows how an inbox becomes a database for recruiters who place people across many roles.
Sourcing outside your inbox works with the same discipline. If you also approach people who never applied, reaching passive candidates creates new CVs and new conversations. Both need a place to land beyond a chat thread.
Keep candidate data safe in chat
A channel feels private, but chat history behaves differently from a records system. HireGen Academy’s lesson on connecting applicant systems, email and Slack puts the rule plainly: do not paste candidate details into general channels, and have approval messages link to the record rather than repeat it. Its reasoning is that chat history is searchable by people who should not see it and usually sits outside your deletion rules.
Turn that into habits:
- Post a name and role, plus a link or reference. Leave out phone numbers, addresses, salary history and personal details.
- Use private channels only for sensitive stages. Offers and pay belong in a channel with a short member list.
- Limit guests. Slack’s guide mentions inviting external recruiters with restricted guest access. Check what a guest can see before adding one.
- Decide how long chat is kept. Set it to match how long you keep candidate records.
- Mind the rules where your candidates live. If you hire in the EU, the GDPR sets requirements for handling applicant data. Our GDPR recruitment compliance guide covers the basics for small teams. For specific legal questions, speak to a qualified employment lawyer or your data protection officer.
RecrutFlo is built with workspace isolation, team access control and an audit trail, and with EU data protection principles in mind. That gives you a controlled place for personal data, so chat only needs to carry references.
Who owns what: Slack, email or a database
The cleanest setups give each tool a single job. If two tools both seem to hold the “real” status of a candidate, people stop trusting either.
| Task | Best home | Why |
|---|---|---|
| Receiving applications | Shared hiring inbox | Candidates already apply by email |
| Turning CVs into records | Candidate database (RecrutFlo) | Extracts details, flags duplicates, keeps files together |
| Searching past candidates | Candidate database | Filter by skills, language, location, role |
| Team discussion and feedback | Slack role channel and threads | Fast, visible to the whole panel |
| Interview reminders | Slack reminders and calendar | Slack’s resource suggests reminders a day or 30 minutes before |
| Offers and pay | Private Slack channel, link to the record | Small audience, no personal data pasted |
| Exporting for a client or manager | CSV export from the database | One clean file instead of screenshots |
The tidy division means a new team member can answer three questions fast: where did this person apply, where is their CV, and what did we decide. Our comparison of a recruitment inbox versus a traditional ATS explains why a small team may not need a full applicant tracking system to get this structure.
What to automate first
If you only automate one thing, make it the move from email to record, since every later step depends on it. Reminders and channel alerts come second. Slack’s resources show how /remind and Slackbot reminders can nudge interviewers before an interview and ask for a quick score and written feedback afterward. These are easy wins because they are small and rule-based.
Keep a human on judgment calls. Automation should read, sort and remind. Your recruiters should still decide who moves on. We designed RecrutFlo with that split in mind: it handles repetitive work while recruiters stay in control. For more on sequencing, see what small businesses should automate first.
Start with the inbox, then the channel
RecrutFlo has a Free plan, so you can test the workflow on your own hiring mailbox before paying. Paid plans on our pricing page are Starter at 19 € per month, Professional at 49 € per month and Business at 149 € per month. If you need more capacity, extra processing runs are a one-off purchase: 100 runs for 9 €, 500 for 29 € or 1,000 for 49 €. There is no sales call or onboarding project to set it up.

Connect your Microsoft 365, Outlook or IMAP mailbox on recrutflo.com, let it read the next batch of applications, and keep Slack for what it does best: talking about the people you are considering.
Our perspective
Most small teams we talk about do not have a Slack problem. They have a CV problem that shows up in Slack. Someone forwards an attachment, three people reply, and a week later nobody can say where the original file went.
Our view is that the inbox should do the boring work. Applications arrive by email, so that is where capture should happen: read the attachment, extract the details, flag the duplicate, and file a searchable profile. Then Slack can be what it is good at, a place for a short conversation that points at a record.
We also think you should not have to adopt a heavy platform to get there. RecrutFlo works with the mailbox you already use, keeps plan limits and prices public, and leaves the hiring decision with your recruiters.
Marco
FAQ
How do I send email to Slack for recruiting?
The fastest way is the Slack add-in for Gmail or Outlook, which forwards an open email and its attachments to a person or channel. For regular alerts, route notifications from your applicant tools into a channel. Use forwarding for discussion, and keep the CV itself in your candidate database.
Should candidate CVs be posted in Slack channels?
Avoid it for anything beyond a small private channel. Chat history is searchable by many people and often outside your retention rules. Post the candidate’s name, the role and a link or reference to the record, and keep personal details in the system built to hold them.
Do I need an ATS if I already use Slack and email?
You need somewhere that stores and searches candidate records. That can be a lighter tool than a full ATS. A database fed from your hiring inbox gives a small team searchable profiles and duplicate detection without a long setup.
How should I name recruiting channels in Slack?
Use a predictable pattern. Slack suggests #hiring-[job title] for each position and interview-[candidate name] for candidates at the interview stage. Add the lead recruiter and deadlines to the channel purpose, and archive the channel when the role is filled.
Sources
- Slack: How Slack helps you recruit smarter
- Slack: The Slack handbook for HR teams
- Slack: Hiring and recruiting, the Slack way
- Slack: Slack for HR, Recruiting, and DEI
- Slack: How Slack and Shopify approach employee engagement
- Slack: New tools to streamline work and boost alignment
- HubSpot: 7 Slack Tips and Tricks
- HireGen Academy: Connecting ATS, calendar, email and Slack
- Sourcegraph handbook: Resources for recruiting operations