Recruitment operations
How to Manage Resumes in a Shared Inbox Without Losing Any
By Andre · · Updated · 14 min read
How to Manage Resumes in a Shared Inbox Without Losing Any

A shared inbox keeps resumes manageable when you do four things: give each person individual access, sort every application on arrival, store each candidate once, and set a deletion date. Past a few dozen applications a week, folders and flags stop scaling. At that point you need something that reads the attachments for you.
This guide covers the setup, the daily routine, the failure points, and the point where a mailbox should hand off to a searchable database.
TL;DR
- Use a real shared mailbox with individual, revocable access. Never share one password.
- Triage every application the same way: acknowledge, label, assign. Keep offers, rejections and salary talks human.
- The inbox is a transport layer, not a database. Duplicates, overwritten files and unsearchable PDFs are what break it first.
- Set a retention rule before you need it. US federal rules can require keeping applications for at least one year.
- When searching by skill, language or location matters, add parsing instead of more folders.
Table of Contents
- Why resumes pile up in shared inboxes
- Set up the mailbox properly first
- Build a triage routine the whole team follows
- Naming, versions and duplicates
- Where the inbox method breaks down
- From inbox to searchable candidate database
- Retention: decide the deletion date now
- What we think: the inbox should stay, the data entry should go
- Where RecrutFlo fits
- A one-week plan to get your shared inbox under control
- FAQ
- Sources
Why resumes pile up in shared inboxes
Most small teams start the same way. A careers address such as jobs@ or recruiting@ goes on the job ad, and applications land there. Two or three people watch it. Nobody owns it fully.
The problems show up in a predictable order:
- Two people reply to the same candidate, or nobody does because each assumes the other has.
- The same person applies for three roles and ends up as three separate emails.
- Someone asks, “Do we have anyone who speaks German and has warehouse experience?” The answer is a long afternoon of opening attachments.
- A recruiter leaves, and their saved copies of resumes leave with them.
None of this is a discipline problem. Email was built to deliver messages, not to hold structured records of people. The fix is to set the inbox up properly, add a routine, and know when it has reached its limit.
Set up the mailbox properly first
Use a shared mailbox, not a shared login
The most common shortcut is one set of credentials passed around the team. It works until someone leaves. Recruitment inbox specialists point out that this makes revoking access impossible without resetting the password for everyone, and that delegated, individual-level access is the standard even for small teams. It also destroys your audit trail, since you can no longer tell who read, moved or deleted a message.
If you use Microsoft 365, a shared mailbox in Exchange Online lets a group monitor and send from one common address. Each person signs in with their own account. A few details matter for recruiting:
- Full Access lets someone read and manage the folders. Send As lets them reply so the message appears to come from the shared address, which is usually what you want on candidate emails. Send on Behalf shows the individual’s name alongside it.
- Permission changes can take up to 60 minutes to show up, per Microsoft’s documentation. Grant access before a new hire’s first day, not during it.
- According to Microsoft’s admin guidance, a shared mailbox without a license is limited to 50 GB. Resumes with attachments add up faster than most teams expect, so check the size now and then.
Google Workspace users have a similar choice between delegation and a collaborative inbox through Groups. The collaborative inbox adds conversation assignment and status tracking, which helps accountability. Delegation is simpler but offers no ownership of individual threads.
We go deeper on what to check in four shared inbox permissions recruiters should verify, from resumes to connected apps.
Decide who can see what
A recruiting mailbox holds personal data: contact details, work history, sometimes photos, birth dates or health information volunteered in a cover letter. Give full access only to the people who actually screen. A hiring manager who needs to see three finalists does not need the whole mailbox.
If you connect any software to the mailbox, apply the same test. Ask what it can read, whether it can send, and who on your side can disconnect it.
Build a triage routine the whole team follows
A shared inbox without rules means every person invents their own system. Agree on one, write it on a single page, and keep it short.
Three states, not twelve
A workable minimum is: new, in review, done. Everything in the inbox is one of those. “Done” means the candidate has been replied to and either moved to a record or archived.
One published label taxonomy for recruiter inboxes separates candidates into groups such as qualified top prospects who need priority responses, and others. You do not need that many tiers. What matters is that a label tells the next person what to do, not just what the email is.
Assign on arrival
The fastest way to lose a candidate is the “someone will get it” email. Pick one of two models:
- Rotation: each person owns the inbox for a day or a week.
- By role: each open role has one owner who handles everything for it.
Rotation suits agencies with many small mandates. Role ownership suits an in-house team with a few openings.
Automate the routine, keep the human parts human
Acknowledgments are safe to automate. One recruiting-inbox guide draws the line this way: routine acknowledgments, nudges on stalled threads and interview scheduling can be automated, while offers, rejections, salary negotiations and conflict resolution should stay with a person. It also warns that robotic generic templates can damage your employer brand.
Starting templates for each stage are in our recruitment email templates. Edit them so they sound like your company.
Capture resumes with rules, up to a point
If you use Outlook, three simple rules go a long way: route messages with resume-like subjects to a folder, flag messages with attachments, and categorize by sender. We lay these out in 3 Outlook rules to capture resumes, including the point where rules stop being enough.
Rules can only see subject lines, senders and whether an attachment exists. They cannot read the resume. That is the ceiling.

Naming, versions and duplicates
Once resumes leave the inbox and get saved to a shared drive, three problems appear.
Inconsistent filenames. “CV final.pdf” and “Resume (2).docx” tell you nothing. Pick one pattern such as Lastname_Firstname_Role_YYYY-MM.pdf and use it for every file.
Overwrites. A candidate sends an updated resume. Someone saves it over the old one, and now you cannot see what changed or when. Keep both, dated. Our guide to resume version control covers how to stop overwrites in a day.
Duplicates. The same person applies through the website, emails a recruiter directly and gets referred by a colleague. Without a unique identifier, you have three records. Email address is the usual key, but candidates change addresses and use different ones for different employers. A good duplicate check also compares names and phone numbers.
The practical rule: one candidate, one record, many documents. Whatever you use, spreadsheet or software, hold to it.
Where the inbox method breaks down
Be honest with yourself about the volume. Here is a rough guide based on what we see in how teams work, not a measured benchmark:
| Weekly applications | What usually works | What starts to hurt |
|---|---|---|
| Under 20 | Shared mailbox, three states, a tracking sheet | Little |
| 20 to 100 | Mailbox plus rules plus a disciplined spreadsheet | Retyping data, duplicates, slow searches |
| 100 and more | A tool that reads resumes and builds profiles | Everything manual |
The signal to move on is not volume alone. It is when someone asks a question the inbox cannot answer. “Who applied for this in the last two years?” “Who is available next month?” “Who speaks Spanish and lives within an hour of Dallas?” Those questions need structured data, and the data is currently locked inside PDF attachments.
Research from an email-sorting vendor suggests that manual inbox handling costs recruiters hours copying data between systems, which fits what small teams tell us. Treat the exact hours as an estimate that varies by team.
From inbox to searchable candidate database
The step after a well-run shared inbox is not a full applicant tracking system for most small teams. It is a layer that reads what arrives and turns it into profiles.
In practice that means four things:
- Detecting resume attachments among invoices, signatures and logos.
- Extracting fields: contact details, experience, skills, languages, location, role, and where available salary expectations and availability.
- Flagging duplicates so one person has one profile.
- Making it searchable by those fields instead of by filename.
We wrote a step-by-step on turning inbox resumes into a candidate database. If you are weighing this against a full ATS, our comparison of a recruitment inbox and a traditional ATS lays out the trade-offs.
Retention: decide the deletion date now
A mailbox that never gets cleaned is a liability. Old resumes sit in an inbox that many people can open, with no record of why you still hold them.
In the US, the federal rule at 29 CFR 1602.14 requires employers covered by it to preserve hiring records, which include applications and resumes, for one year from the date the record was made or the hiring action was taken, whichever is later. Coverage depends on employer size and other factors, and state or local rules, or federal contractor rules, may require more. Ask your employment counsel or HR advisor which rules apply to you before you set a deletion date.
If you recruit candidates in the UK or EU, different rules apply. The UK data protection regulator publishes guidance on recruitment and selection, and the French regulator has a recruitment data protection guide in French. Those regimes lean toward keeping personal data no longer than needed, so check them if candidates there apply to you.
Whatever period you choose, write it down, tell candidates in your privacy notice, and make deletion automatic or calendar-driven. A manual cleanup that nobody owns will not happen.

What we think: the inbox should stay, the data entry should go
We built RecrutFlo around a belief that many recruitment tools get backwards. Teams do not need to abandon the inbox. The inbox is where applications already arrive, where candidates already write, and where the team already works. Forcing everyone onto a new platform adds a migration, training and a new place for things to get lost.
What teams do need is to stop retyping. Every resume read by a person and copied into a spreadsheet is time spent on work a machine does acceptably. So we connect to the mailbox you already have, find the resume attachments, extract the details into a profile, and flag duplicates. Recruiters stay in control of what happens next. We automate the repetitive part and leave candidate decisions with people.
We also think small teams are badly served by software that demands a sales call, an implementation project and a long contract before you can see whether it works. That is why we publish plan limits and prices, and offer a free plan to test the workflow on your own mailbox.
And we take privacy seriously because resumes are personal data. Workspaces are isolated, access is controlled by team role, there is an audit trail, and our approach follows EU data protection principles. Whatever tool you pick, ask any vendor those same questions.
— Marco
Where RecrutFlo fits
If your team receives resumes by email and spends real time reading, retyping and searching them, RecrutFlo is built for that exact workflow. It connects to Microsoft 365, Outlook and IMAP mailboxes (Gmail is coming soon), detects PDF, DOC and DOCX resumes, builds searchable profiles, flags duplicates, and supports CSV export.
Plans on the pricing page run from a Free plan to Starter at 19 € per month, Professional at 49 € per month and Business at 149 € per month. If you need more capacity in a month, you can add 100 processing runs for 9 €, 500 for 29 € or 1,000 for 49 €, each a one-off purchase. See how it works before you connect anything. If your mailbox is IMAP-based, this setup guide covers connecting it safely.
A one-week plan to get your shared inbox under control
You do not need a project. Here is a sequence a small team can finish in five working days.
- Day 1: Fix access. List who has access to the recruiting mailbox. Remove shared passwords. Switch to individual permissions, and allow up to an hour for changes to take effect.
- Day 2: Agree the states and owners. Write down new, in review and done. Decide rotation or role ownership.
- Day 3: Set up rules and templates. Add the folder rules, an acknowledgment template and a standard rejection template.
- Day 4: Clean up what exists. Merge duplicates, rename files to your pattern and archive anything past your retention date.
- Day 5: Test the limit. Ask five realistic search questions of your current setup. If you cannot answer them in a few minutes each, you have your answer on whether to add parsing.
Repeat the Day 5 test every quarter. The honest answer will change as volume grows.
FAQ
Is a shared mailbox the same as a shared inbox?
Not quite. “Shared mailbox” is the Microsoft 365 term for a mailbox several people open with their own accounts. “Shared inbox” is the general idea, and it also covers collaborative inboxes in Google Workspace or dedicated shared inbox tools. For resumes, what matters is individual access, a clear owner for each message and an audit trail.
Can I use rules alone to organize resumes?
Rules can sort by subject, sender and attachment, which is enough for a low volume. They cannot read the content of a resume, so they cannot tell you a candidate’s skills, location or languages. When you need to search by those details, you need parsing or manual data entry.
How long should I keep resumes from unsuccessful candidates?
In the US, federal rules under 29 CFR 1602.14 set a one-year minimum for covered employers, and some states or contracts require longer. Beyond that, keep them only as long as you have a documented reason, and tell candidates. Check with employment counsel for your situation, and see different rules if you recruit in the UK or EU.
Do I have to leave my email provider to use a resume database?
No. Our approach is to connect to the mailbox you already use rather than replace it. You keep your existing email and your team keeps working in it.
Sources
- Shared mailboxes in Exchange Online, Microsoft Learn
- About shared mailboxes, Microsoft 365 admin
- Shared Mailbox im Recruiting, emailmanager.ai
- Recruiter Inbox Management, Email Ferret
- Recruiting Inbox Automation, aiemaily.com
- Best Email Sorters For HR & Recruiters
- 29 CFR 1602.14, Cornell Legal Information Institute
- Recruitment and selection, ICO
- Guide recrutement, CNIL