Email collaboration is a whole team answering one address together, with everyone able to see what has arrived, who has it, what has already been said, and which conversations are still open. That is the whole of it. Assignment, internal notes, status filters and customer history all exist to make those four things visible without anyone having to ask a colleague.
We make Vidual Inbox, so we have a stake in this. But the definition holds whichever tool you land on, and the precision is worth having, because most small teams sit somewhere in between: everyone gets the messages, but nobody can see who’s handling what.
Passing an email on isn’t sharing the work
Forwarding and CC hand someone a copy. From the moment that copy lands, it and the original start drifting apart. Your colleague replies from her own address, so the customer now holds two threads with two people at the same business. Nothing anywhere records that she took it. If she is away next week, the only way to find out whether the customer ever got an answer is to go digging through a sent folder — and only if the reply went out from the shared account at all, which it did not.
A shared login is a step up and still not collaboration, because everyone is signed in as the same person. Nobody can claim a conversation as theirs, so ownership is remembered rather than recorded, and follow-ups sit unanswered because they were nobody’s job in particular. If you are weighing up Gmail’s own options at this point, we have written about delegation and Google Groups in detail, including where each one gives up.
The difference is that nothing gets copied. The conversation stays where it is, and what the team knows about it — who picked it up, whether it still needs answering — is attached to it rather than held in someone’s memory.
The four failures it exists to fix
The same handful of problems come up in every small team we talk to.
- Two people answer the same message. Both saw it, neither knew the other was already typing, and the customer gets two replies that don’t quite agree.
- Nobody answers it. Everyone assumed someone else had it. This is the expensive one, because nothing visibly breaks — the customer simply goes elsewhere and you never learn why.
- History doesn’t follow the person. A repeat customer’s email and their Instagram DM arrive as unrelated threads from unrelated strangers, so whoever picks one up starts from zero with someone who has bought from you three times.
- Context lives in one head. The apprentice can answer the question. Only the founder knows what was promised last time.
We have written separately about what breaks when a small team shares an address and the software built around it. This piece is about the practice rather than the software.
The features that do the real work
Marketing pages list dozens. Only a handful do anything collaborative, and you can judge any tool on whether it has them.
| What it does | Why it matters | In Vidual Inbox |
|---|---|---|
| Assignment | Turns “someone should reply” into “Sam is replying” | Reply and it’s yours; reassign with a tap |
| Filterable status | Shows what’s outstanding in one glance | Mine, unassigned, waiting, closed |
| Internal notes | Lets the team discuss a customer without the customer seeing | Notes inside the thread, with @mentions that notify |
| Customer context | Whoever picks it up picks up the relationship | A sheet of notes, tags, history and files that persists |
| One record per person | Same human, email and DM, one history | Merge profiles so history follows the person, not the channel |
| Replies from your address | Keeps the machinery invisible to the customer | Your brand address, each person’s own signature |
| Every channel, one stream | Because customers don’t only email | Email, Instagram DMs, WhatsApp, Telegram, live chat |
Two things get sold as collaboration and aren’t: ticket numbers and automation rules. Both are volume-management machinery. At five people the problem isn’t routing throughput, it’s visibility — so we ship without tickets, SLA timers or rule engines on purpose. If you do need them, Freshdesk or Zendesk are the better buy and we’ll say so. There’s a decision tree if you’re on the line.
Ten questions for your own inbox
Answer these about the setup you have today, not the one you mean to build. It takes about a minute and the result is only as useful as your honesty about the fourth one.
- Can you tell, without asking anyone, who is handling each open conversation right now?
- Can you see every message waiting on a reply from your team, in one list?
- When a colleague replies, does it go out from your brand address rather than theirs?
- If someone left today, would you keep their conversation history and their notes?
- Can you discuss a customer’s order with a teammate inside the thread, where the next person will find it?
- When a repeat customer writes in, do you see their past conversations before you reply?
- If they emailed once and DM’d another time, are those the same record?
- Do Instagram DMs, WhatsApp messages and website chats reach the same place as email?
- Can you triage all of it from a phone, properly?
- Does adding an eleventh person leave your bill unchanged?
Answer all ten to see where you land.
Where Vidual Inbox sits
We are the small-team end of it. One place where everyone sees every conversation, whether it arrived by email, Instagram DM, WhatsApp, Telegram or the chat box on your site, with assignment, internal notes, status filters, tags and a customer sheet that follows the human rather than the channel. Up Ahead surfaces replies still waiting and dates customers mentioned in passing. Catch Up summarises long threads. Otto drafts and suggests, always with your sign-off, and never sends on your behalf.
It is £24.99 a month flat plus VAT with as many team members as you like — the same bill at nine people as at two, which matters here more than it looks. Per-seat pricing discourages the exact thing collaboration depends on, which is everyone being in the room. Setup takes under an hour, and Gmail users authorise in a single popup with no DNS to wrangle. The full list is on the pricing section.
Common questions
What is email collaboration?
A whole team answering one address together, with everyone able to see what has arrived, who is handling it, what has already been said, and which conversations are still open. Everything else exists to make those four things visible without anyone having to ask.
How is email collaboration different from forwarding or CC’ing people?
Forwarding creates a copy, and a copy carries no ownership, no status and no record. Your colleague replies from her own address, the customer ends up with two threads, and there is nothing to check but a sent folder. Collaboration keeps one conversation, with who has it and what state it’s in attached to the conversation itself, so the next person to open it knows everything without asking.
Isn’t a shared login the same thing?
No, because everyone is signed in as the same person. Nobody can claim a conversation as theirs, so ownership is remembered rather than recorded, and follow-ups sit unanswered because they were nobody’s job in particular.
What features actually enable email collaboration?
Four do most of the work: assignment, a status you can filter, internal notes with mentions, and customer context that persists. After those, one record per person across channels, and replies from your brand’s own address. Anything built for triaging volume is solving a different problem.
How does Vidual Inbox fit the category?
It is a shared inbox for teams of one to ten who have outgrown a shared Gmail login but would never adopt an enterprise help desk. Every channel in one stream, with assignment, notes, tags, status filters and a persistent customer sheet, at £24.99 a month flat however many people you add. It deliberately isn’t a ticketing system, a CRM, or an AI auto-replier.
Run the ten questions on the inbox you have now. If the gaps look familiar, Vidual Inbox is free for 14 days with no card — £24.99/month after that, every feature, every team member, no per-seat surcharge.