Shared inbox for teams

How a shared mailbox works in Mailbind

A mailbox is connected once, by one person, and then shared with the workspace. The credentials are encrypted and never shown again — not to the person who entered them, and not to the colleagues who now read the mailbox. Nobody has to be told the password of support@ in order to answer it.

Everyone who can see the mailbox sees the same list, the same threads and the same state. When a colleague opens a conversation and starts replying, that is visible: the point of a shared inbox is that two people never answer the same customer twice.

• Assign a conversation to a member, or pick it up yourself.
• Tabs for what is assigned to you, what is unassigned and what the team has in hand.
• Internal notes on a thread, which the customer never receives.
• Replies go out from the shared address, signed by the team rather than by whoever happened to be at the keyboard.

Roles, so access matches responsibility

A workspace has owners, administrators and members. Connecting or removing a mailbox, inviting people and changing billing belong to the owner and the administrators; reading and answering belong to everybody who has been given the mailbox. A new member sees the shared mailboxes they were added to and nothing else.

Every mailbox stays scoped to the workspace that connected it. A query for a message, an attachment or a draft is always checked against the membership of the asking account, which is tested on every resource rather than trusted from the URL.

Shared inboxes are part of the Team plan. Free and Pro are single-member plans; the mailboxes you connect there are yours alone.

What a support team gets out of it

• One queue instead of a forwarding chain, so nothing lands in a personal inbox and stays there.
• A record of who answered what: the workspace audit log keeps three months of actions.
• Needs-reply triage over the shared queue, so the messages still waiting on a human are the ones at the top.
• AI summaries on long threads, which is what makes a handover between two people cheap.
• Snooze and rules, so a thread that is waiting on a customer leaves the queue until the day it matters.

Moving an existing support address in

1. 1Create the workspace and invite the people who will answer.
2. 2Connect support@ once: pick the provider, enter the mailbox password or app password, and let Mailbind fill in the IMAP and SMTP servers.
3. 3Share the mailbox with the members who need it, and give the administrators who manage mailboxes their role.
4. 4Set the signature for the shared address, so every reply reads as the team.
5. 5Add rules if the queue needs sorting on arrival, and turn on Needs-reply triage.

Common questions

Keep reading

• All features
• AI email assistant
• Send from the right address
• Arabic and RTL email client
• Security
• Help: roles and permissions