KoltrixHow to find anything in a shared mailbox: search techniques
Worked examples of finding old threads in a shared mailbox: search by sender domain, exact phrase, date range, attachment and label, and combine filters well.
On this page(12 sections)
- The general approach
- Task 1: Everything from one customer company
- Task 2: A specific phrase from an old email
- Task 3: Something from a known time period
- Task 4: An email with an attachment
- Task 5: Everything with a particular label
- Task 6: Combining filters for a precise answer
- Quick reference
- Saving common searches
- Name things so they can be found later
- When search fails
- Bottom line
A shared mailbox is a team's memory, but only if you can find things in it. "Didn't someone from that company ask about this last spring?" should take thirty seconds to answer, not twenty minutes of scrolling.
Search syntax differs between email tools, but the techniques are the same everywhere. This guide works through realistic search tasks in a shared support mailbox, shows the approach for each, and ends with habits that make future searches easier.
The general approach
Good searches narrow from what you know for sure to what you're less sure of:
- Start with the most certain fact: usually who sent it or roughly when.
- Add one filter at a time and see how the results change.
- Use exact phrases only for words you're confident appeared verbatim.
- Open the newest matching thread first; it often references the older ones.
The examples below use generic, commonly supported operators such as from:, after: and quoted phrases. Check your tool's help page for the exact syntax it supports.
Task 1: Everything from one customer company
"Pull up all our conversations with Northwind."
People at one company use different addresses, but they usually share a domain. Search by domain rather than by person:
from:northwind.example
To include conversations where Northwind was in To or Cc (for example, threads you started), many tools support searching any address field, or you can run a second search with to:northwind.example.
Watch out for: customers writing from personal webmail addresses. If you know the person's name, add a search by name as a second pass.
Task 2: A specific phrase from an old email
"A customer once reported 'sync stopped after the update.' What did we tell them?"
Use an exact phrase in quotes:
"sync stopped"
Pick a short, distinctive fragment rather than a whole sentence. Customers rarely use exactly the wording you remember, so "sync stopped" is more likely to match than "sync stopped working after the latest update."
If the exact phrase finds nothing, drop the quotes to match the words anywhere in the message, then narrow with a date range.
Task 3: Something from a known time period
"We had a wave of billing questions around the price change in March."
Combine a topic word with a date range:
billing after:2026-03-01 before:2026-04-01
Date filters are one of the fastest ways to cut a large result set. Even an approximate range ("sometime in spring") removes most of the noise.
Task 4: An email with an attachment
"Someone sent us a signed contract as a PDF. Where is it?"
Filter for messages with attachments, and if your tool supports it, by file name or type:
has:attachment contract
filename:pdf from:northwind.example
If the attachment name isn't searchable in your tool, search for words likely to appear in the message body alongside it: "attached," "signed," "please find."
Task 5: Everything with a particular label
"Show me all threads we labeled as feature requests about exports."
Labels make search much more powerful, because they add information that isn't in the text:
label:feature-request export
This works only if labels were applied consistently, which is one of the best arguments for a small, agreed label set.
Task 6: Combining filters for a precise answer
"Did anyone from Bluebird report the CSV export bug before the fix in August?"
Stack what you know:
from:bluebird.example CSV before:2026-08-15
If that returns nothing, relax one filter at a time:
- Drop the date (maybe they reported it later).
- Replace
CSVwithexport(maybe they described it differently). - Search the domain with
to:(maybe someone on your team emailed them first).
Relaxing one filter at a time tells you which assumption was wrong.
Quick reference
| You know... | Search by | Example |
|---|---|---|
| The company | Sender domain | from:northwind.example |
| A memorable phrase | Exact phrase | "sync stopped" |
| Roughly when | Date range | after:2026-03-01 before:2026-04-01 |
| There was a file | Attachment filter | has:attachment invoice |
| How it was categorized | Label | label:billing refund |
| Several of the above | Combine | from:acme.example label:billing after:2026-01-01 |
Saving common searches
Some searches come up every week: open billing questions, threads from your largest customers, bug reports from the last seven days. If your tool supports saved searches or filtered views, save them. If not, keep a short note of the search strings in your team playbook so everyone can copy them.
Useful saved searches for a support mailbox:
- Threads from your top accounts' domains
- Unanswered threads older than a day
- Everything labeled
bugin the last two weeks - Messages mentioning "cancel" or "refund" in the last month
Name things so they can be found later
Search is only as good as what's in the mailbox. A few habits make future searches easier:
- Write descriptive subjects when you start a thread: "Northwind: SSO setup questions," not "Quick question."
- Rename vague subjects when you reply to an important thread, if your team agrees it's acceptable: add a short prefix like "[Bug: CSV export]."
- Use labels consistently with an agreed, short list.
- Mention key terms in your replies. If a customer described a bug vaguely, your reply can name it precisely ("the CSV export timeout"), which makes the thread findable by that term later.
- Don't split one topic across many threads when you can keep it in one.
When search fails
If nothing turns up:
- Check whether the conversation happened in a personal inbox rather than the shared one. This is common in teams that used to forward mail.
- Ask the team in chat; someone may remember the customer or the time frame.
- Search sent mail as well as received mail.
- Consider whether it was a phone call or chat, not email at all.
Bottom line
Start from what you know for certain, usually the sender's domain or a time period, and add filters one at a time. Use exact phrases sparingly, lean on labels when they're consistent, save the searches you run every week, and write subjects and replies that your future self can find.
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.
