KoltrixArchive or delete? Retention habits for team mailboxes
Why archiving customer mail usually beats deleting it, what is safe to delete, how to handle attachments and storage, and how to write a retention policy.
On this page(8 sections)
Every team mailbox eventually faces the same question: once a thread is done, does it get archived or deleted? Many teams never decide, so each person does whatever feels right, and a year later half the history is gone and the other half is a junk drawer.
A few clear habits, written down, fix this. This post gives you a decision table for the common cases, explains why archiving is the right default for anything involving customers, and outlines a simple retention policy you can adapt.
A note before we start: this is operational guidance, not legal advice. Depending on your industry and where you operate, you may have legal obligations to keep certain records for a minimum time, or to delete personal data after a certain point. Check those obligations with someone qualified and let them override anything here.
Why archiving is the right default for customer mail
Archiving removes a thread from the working view while keeping it searchable. Deleting removes it (usually after a short trash period) for good. For customer conversations, archiving wins for practical reasons:
- Context for the next conversation. When a customer writes again in six months, the previous thread tells you what they tried, what you promised and how they felt.
- Answering "what did we tell them?" Disputes about refunds, commitments or support quality are settled by the actual emails.
- Learning from history. Recurring questions, common bugs and good replies are all in old threads. Deleted threads can't feed your docs or train new teammates.
- Search is cheap; regret is expensive. Archived mail costs a little storage. A deleted thread you suddenly need costs far more.
The goal of inbox cleanliness is a clear working view, and archiving achieves that just as well as deleting does.
The decision table
| Type of email | Default action | Notes |
|---|---|---|
| Customer support conversations | Archive | Keep the full thread, including attachments |
| Sales and partnership conversations | Archive | Useful for renewals and relationship history |
| Billing, invoices, receipts | Archive | Often subject to record-keeping rules; check yours |
| Security reports and account-access requests | Archive | You may need to show what was requested and how you verified it |
| Internal discussion about a customer | Archive | Keep it with or linked to the customer thread |
| Newsletters and marketing you subscribed to | Delete or let them expire | Unsubscribe if nobody reads them |
| Tool notifications (CI, monitoring, social) | Delete after they've served their purpose | Often duplicated in the tool itself |
| Cold pitches with no reply | Delete or archive in bulk | Low value either way; pick one and be consistent |
| Obvious spam and phishing | Delete (report if your tool allows) | No reason to keep |
| Messages containing secrets (passwords, keys) | Rotate the secret, then delete | Don't leave credentials searchable |
| Personal data requested for deletion | Follow your deletion process | See your obligations and privacy policy |
What's reasonable to delete
Deleting isn't bad; deleting the wrong things is. Good candidates:
- Duplicates. Notification emails that mirror information kept in another system.
- Pure noise. Spam, phishing, marketing you never read.
- Sensitive content that shouldn't persist. A customer who emails you a password or API key should be told to rotate it, and the email should go.
- Data you've been asked to delete, handled through whatever process your privacy commitments require, including any copies in other systems.
When in doubt, ask: "Could anyone on the team plausibly need this in a year?" If yes, archive.
Attachments and storage
Attachments are where mailboxes get heavy. A few habits keep storage sane without losing history:
- Don't strip attachments from customer threads. Screenshots, logs and invoices are part of the record.
- Move large internal files out of email. Design files, exports and recordings shared internally belong in file storage, with a link in the email.
- Search for the biggest offenders occasionally. Most email tools let you search or sort by size. A handful of huge messages usually account for a lot of the space.
- Watch for duplicate attachments from people re-sending the same file in every reply.
If your plan has a storage limit, know roughly where you stand before you hit it, not after.
Writing a simple retention policy
A retention policy can be half a page. It should answer:
Team mailbox retention policy (draft)
1. Default: archive, don't delete, any thread with a customer,
prospect, partner or vendor.
2. Delete: spam, phishing, unread marketing, notifications
duplicated in other tools.
3. Secrets: if an email contains a password, key or token, ask the
sender to rotate it, then delete the message.
4. Deletion requests: follow [process link]; covers email and any
copies in other systems.
5. Minimums and maximums: [list any legal retention periods that
apply to us, as confirmed by (name/role)].
6. Owner: [name] reviews this policy every [six/twelve] months.
Item five is the one to get professional input on. Everything else is team habit.
What about departing teammates' mail?
Retention questions get sharper when someone leaves. Their personal mailbox may hold customer conversations that never touched the shared inbox: a renewal negotiated directly, a bug report sent to them by name, a vendor contract discussed over several months.
Before closing a departing teammate's account, decide what happens to that history:
- Customer and vendor threads should move somewhere the team can reach, such as the relevant shared mailbox or an archive the right people can search.
- Their address can often stay alive as an alias pointing to a shared mailbox for a while, so customers who write to them still reach someone.
- Purely personal mail (benefits, payroll, personal notes) should be handled respectfully and in line with your employment policies, not dumped into a shared folder.
This is one more reason to keep customer conversations in shared mailboxes in the first place. History that lives in a shared mailbox doesn't need rescuing when someone moves on.
Making the habit stick
- Agree on "done" means archive. When someone finishes a thread, the action is archive, every time.
- Teach it in onboarding. New teammates copy whatever they see; show them the policy on day one.
- Make bulk cleanup boring. A monthly ten-minute pass deleting noise is better than a heroic cleanup once a year.
- Don't punish full archives. Search exists. Nobody should feel they need to prune customer history to keep things "tidy."
Bottom line
For team mailboxes, archive is the default and delete is the exception. Keep everything involving customers, money and security; delete noise, duplicates and anything containing secrets. Write the rules down on half a page, get qualified input on any legal retention requirements, and make "done means archive" a team habit.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
