Mailbind for agencies

What an agency actually needs from an inbox

Mailbind’s Team plan is built around those six. Every query is scoped to the workspace and checked against the membership of the account asking, per resource rather than per page — and each resource has a cross-workspace access test in the suite, so the scoping is verified rather than assumed.

• A mailbox per client, connected once, with the credentials never visible again.
• Access by person: the people on an account see that account’s mailboxes and no others.
• Replies from the client’s own address, through the client’s own server.
• Handover that survives holidays and turnover: assignment, internal notes, summaries.
• Removal in one action when someone leaves, with no password to rotate.
• A record of who did what, for the week a client asks.

Who sees which mailbox

Mailboxes are shared with named members. An account manager added to three clients sees three mailboxes; a new designer sees none until someone gives them one. Owners and administrators connect and remove mailboxes, invite people and manage billing; members read and answer.

That makes onboarding and offboarding administrative rather than technical. Nobody edits a shared document of passwords, and nobody has to remember which four mailboxes a departing colleague could reach.

Why the sender rule is the feature agencies notice

Answering a client’s customer from the agency address is the mistake that costs money. The customer replies to the agency, the thread leaves the client’s mailbox, and months later the client cannot find the correspondence in their own archive — and they are right to mind.

In Mailbind a reply leaves from the mailbox that received the message, through that mailbox’s own SMTP server at the client’s provider. The message is indistinguishable from one the client sent: same domain, same SPF and DKIM alignment, same archive. Where several addresses land in one client mailbox, each can be added and verified so it answers as itself.

Billing, and what it costs for a studio of five

Team is €14 a month per member, or €140 a year per member, on one invoice for the workspace with no VAT added. Five people is €70 a month regardless of how many client mailboxes you hold — which is the opposite shape from the per-user support platforms, where the mailbox count is free and the people are the bill.

Adding a member mid-month adjusts the next invoice for the days used; removing one frees the seat at the end of the period. Invoices are downloadable from Settings per workspace.

If you want one workspace per client rather than one workspace with many mailboxes, that works too — but members are counted per workspace, so the usual arrangement is one workspace for the agency.

Privacy, and what to tell a client

Mailbind encrypts mailbox credentials with AES-256-GCM, hosts in the European Union, keeps a workspace audit log for three months and publishes a data processing agreement under GDPR article 28. What it cannot do is tell you whether that satisfies your own professional obligations — read the DPA and the privacy policy, and ask whoever advises you.

In practice the sentence a client wants is this: their mail stays at their provider, Mailbind holds a synchronised copy on EU servers to make search and sharing work, credentials are encrypted and unreadable, and disconnecting the mailbox deletes the copy within thirty days.

Common questions

Keep reading

• Who it is for
• For freelancers
• Keep client inboxes apart
• Shared inbox for teams
• Security at Mailbind
• Mailbind vs Missive