Team Access pricing

Team Access: people bought once, for the account.

Team Access gives a colleague, an assistant or a contractor their own connection to a mailbox you own, with a permission level and a daily cap you set, and their own line in the activity record. It is bought once, for the account, as a tier of 3, 5 or 10 named people, on top of Pro on the mailboxes themselves.

  • Tiers 3, 5 or 10 people
  • From £119.99 + VAT a year
  • Mailboxes Pro, per mailbox, £34.99 + VAT

The tiers

The 3 Team Access tiers

A tier is a number of named people. Each may be given their own connection to any Pro mailbox on your account, and one person on several mailboxes is still one person.

Team 3

£10.00 a month Per account, paid annually at £119.99 + VAT

  • 3 named people, across every mailbox on the account
  • Own connector URL and permission level per person
  • Own daily cap per person, set by you
  • Remove a person in one action
Buy Team 3

Team 5

£16.67 a month Per account, paid annually at £199.99 + VAT

  • 5 named people, across every mailbox on the account
  • Own connector URL and permission level per person
  • Own daily cap per person, set by you
  • Remove a person in one action
Buy Team 5

Team 10

£33.34 a month Per account, paid annually at £399.99 + VAT

  • 10 named people, across every mailbox on the account
  • Own connector URL and permission level per person
  • Own daily cap per person, set by you
  • Remove a person in one action
Buy Team 10

Mailboxes are bought per mailbox. People are bought once, for the account. A tier includes no mailbox: every mailbox you share stays on whatever plan it has, Pro at £34.99 + VAT a year or free, and the tier sits on top. There is no per-head discount and no "whole team included" figure, because the 3 prices above are the whole price list. Paid by card through Stripe as one annual payment, net of VAT, renewing annually until you stop it.

Per person

What each person gets

You invite a person by email address, choose which of your mailboxes they may reach, and set 3 things for them: a permission level, whether the calendar is included, and a daily cap. Each person then gets their own connector URL, one per mailbox they are on, which they paste into their own AI client. Nothing of yours is shared with them: not your password, not your token, not your connection.

The level is the same 3-step ladder every connection on this site carries: Read only, Draft and file, or Send and delete, with the calendar on or off beside it. Level, calendar, cap and display name are changed from the People tab and land on every mailbox the person is on at once, on their next call, without anybody reconnecting. The tool reference lists every tool under the level that reaches it.

An invitation is bound to the address it was sent to. It is accepted only by an account whose verified email address is the invited one; a forwarded link does not work for anybody else, and the refusal names the account that is signed in and shows the invited address in masked form. Once accepted, every call the person makes carries their name in the activity record, so the log on a shared mailbox says who did what rather than only what was done.

Removing a person is one action. Every share they held and every connection they made end together, each connection on its next call, and they are emailed to say so. Pausing a person is the same control without the email, and resuming them takes one seat check. A person who is not entitled, because the tier lapsed, you downgraded, or you paused them, is refused with a plain sentence in the control panel and an opaque refusal in their AI client; nothing of theirs is deleted, and a tier that covers them again seats them without re-inviting.

The People tab of the Mailbox MCP control panel on a Team 5 account: a seat line reading 2 of 5 seats used, 2 waiting, then a row for Alice Okafor, active, Draft and file, with the calendar, on 2 mailboxes, with a daily cap of her own, and a row for ben.carter@acme.example, active, Send and delete, on one mailbox, with no cap of his own.
The People tab: one row per person, with their level, cap and mailboxes, and the seats in force on the account.

Metering

How a shared mailbox's daily allowance grows

A Pro mailbox has up to 1,000 MCP calls a day, counted over a rolling 24 hours. Sharing it does not divide that between people: it grows by 1,000 for each person entitled on the mailbox. The allowance is 1,000 multiplied by 1 plus the number of people active on it, so a Pro mailbox shared with 2 people has 3,000 calls a day between the 3 of you. A parked or paused person does not count. Sharing is on top of Pro: a mailbox that is not on Pro cannot be shared, and the panel says so if you try. If Pro lapses on a mailbox that is shared, the people stay attached and the mailbox drops to 5 calls a day between everybody on it until Pro is bought again.

Pro mailbox shared with People, counting you Calls a day
Nobody 1 Up to 1,000
1 person 2 Up to 2,000
2 people 3 Up to 3,000
4 people 5 Up to 5,000

You can cap any one person lower than that. A cap is a figure you set per person from the People tab; it applies on each mailbox they are on, and it is a second count inside the same check the mailbox's own limit uses. A person who reaches theirs is told so in a sentence their assistant can relay: that the mailbox itself still has capacity, and that the owner can raise their ceiling from the People tab. It is a limit that was reached, not a fault, and the sentence says that too.

A shared mailbox with a tray for each person on it: the robot at one mailbox sorting letters into 4 trays.
One mailbox, and the allowance grows with each person on it

On every mailbox of a Team account

The 6 claim and approval tools

Every mailbox on a Team account registers 6 tools that a mailbox on an account without a tier never sees. They exist so that 2 colleagues, each with their own assistant, do not both answer the same message, and so that a person who may not send from the mailbox can still get a reply out through you.

Claims: who is dealing with which message

Claim a message, or a set of them, so colleagues sharing the mailbox know somebody is dealing with it and nobody answers it twice. Hand a message to a named colleague. Release a claim when it is done. Every listing on a Team mailbox says who holds each message, and a reply, forward or draft reply to a message somebody else holds opens with one sentence naming them and still does the work: it is information, not a refusal. The claim is a keyword on the message in the mailbox itself, set by the mail server, so it survives the assistant, the session and the connection and vanishes with the message if the message is deleted; who holds it is a record of ours naming the mailbox, the folder, the message and the person, never a subject, an address or a line of the message.

  • claim_email
  • release_email
  • assign_email

Approvals: a draft waits for the owner to send it

A person whose connection may draft but not send writes the reply as a real draft in Drafts and marks it as waiting for the owner. The owner's assistant lists every draft waiting, newest first, with who asked, when, the recipients, the subject and a preview, and sends the one the owner approves through the ordinary send path: one Sent copy, the draft's own attachments and threading, and the draft removed from Drafts the way a mail client removes one it has sent. A draft nobody asked about is refused. Sending a draft back for changes is an ordinary email from the owner to the person; there is no tool for it.

  • request_approval
  • list_pending_approvals
  • approve_and_send

The fact behind both is a keyword on the message in your own mailbox, so it survives the assistant and the session and vanishes with the message if the message is deleted; who holds it is a record of ours that names the mailbox, the folder, the message and the person, and never a subject, an address or a line of the message. Nothing here moves a message or marks it read. A mail server that does not accept custom keywords is told so by the tools rather than pretended at, and Outlook may not show a keyword it did not set. Each tool, with what it does and where it refuses, is on the tool reference, and the Team Access guide walks through a claim and an approval end to end.

What you are told

The 2 owner alerts

Both are emails, both are on unless you turn them off under what we email you about, and neither holds anything back: they are information an owner cannot get by reading their own mailbox, because the sends were made by somebody else and the Sent folder does not say who.

  • The Monday digest. Every Monday at 08:00 London time, an owner with somebody active on a mailbox gets one email: per person, the sends, filings and reads over the last 7 days, and the drafts waiting for approval across the shared mailboxes.
  • The first-time-domain alert. The first time a shared person sends to a domain the account has not written to since Team Access began, through any mailbox, you are emailed once: who, which mailbox, the domain and the subject. Your own sends never alert; they only teach the account which domains it knows.

Out-of-hours alerts and behavioural alerts are deliberately not built.

A shared person sending to a domain the account has not written to before: the robot lifting a letter out of a mailbox and holding it up.
The first letter to a new domain is the one you hear about

Changing your mind

Upgrading, downgrading, cancelling and refunds

Up and down are immediate, and neither moves the date your year ends. Moving up invoices the difference for the rest of the year now, prorated by Stripe. Moving down credits the difference to your next invoice. The confirmation screen shows the direction and, on a downgrade, names the people beyond the new allowance, newest first, before anything changes; those people are parked, not deleted, and a bigger tier later seats them again, oldest first, without anybody being re-invited.

Cancelling is cancel-renewal. The seats run to the end of the paid year and the tier ends on that day, when everybody on it is parked: every call of theirs is refused until a tier is bought again, while their levels, caps and connector URLs are kept, so buying one again restores them without re-inviting. Nothing is deleted.

A full refund of the year's Team payment ends the tier the same day, cancels the subscription, parks everyone, and emails you naming them. A refund of only the prorated invoice for an upgrade changes nothing on its own. The refunds and cancellation policy carries the 14-day right for UK consumers and the cases we refund outside it, for a Team tier as for a Pro mailbox.

The Team Access card on the Billing screen of the Mailbox MCP control panel: 4 tiles reading Team 5, your tier for the whole account; 2 of 5 seats used, under People; the monthly figure, paid annually with VAT noted, for the account; and the renewal date. Below them a Change tier control, a Stop it renewing button with the sentence that stopping keeps every seat until the renewal date, and a note on how Team Access is charged.
The Team Access card on the Billing screen: the tier, the seats, the charge and the renewal as 4 tiles, and the controls to change or stop it.

Questions

Questions about Team Access

What does a Team tier include, and what does it not include?

A tier is a number of named people, 3, 5 or 10, who may be given their own connection to any Pro mailbox on your account, each with their own connector URL, their own permission level, their own daily cap and their own line in the activity record, plus the claim and approval tools on every mailbox you share. It does not include any mailbox: mailboxes stay Pro per mailbox at £34.99 + VAT a year, and only a mailbox on Pro can be shared. People are bought once, for the account; one person on 3 of your mailboxes is one seat.

Do I still need Pro on each mailbox I share?

Yes. Team Access works on a mailbox on Pro, and the control panel refuses an invitation naming one that is not, with a sentence that names the mailbox and asks you to move it to Pro first, then invite. A Pro mailbox's allowance grows with the people entitled on it: 1,000 calls a day for the owner plus 1,000 for each person, so a Pro mailbox shared with 2 people has 3,000 a day, and the owner can cap any one person lower than that. If Pro lapses on a shared mailbox, the people stay attached and the mailbox drops to 5 calls a day between everybody on it until Pro is bought again.

What happens if I downgrade with more people than the smaller tier allows?

The people beyond the new allowance are parked, newest first, and the confirmation screen names them before anything changes. A parked person is refused with a plain sentence in the control panel and an opaque refusal in their AI client; nothing of theirs is deleted, and moving to a bigger tier again seats them, oldest first, without anybody being re-invited. A downgrade credits the difference to your next invoice; an upgrade invoices the difference now; both take effect immediately and neither moves the date your year ends.

What happens when I remove somebody?

Every share they held and every connection they made end in one action, and every connection ends on its next call: there is no session to wait out and nothing for them to sign out of. They are emailed to say so. An invitation that was never accepted is withdrawn without an email. Their lines in the activity record stay, so you can still see what was done and by whom.

What happens if I cancel a Team tier, or get it refunded?

Cancelling stops the renewal: the seats run to the end of the paid year and the tier ends on that day, when everybody is parked and kept rather than deleted. A full refund of the year's Team payment ends the tier the same day and parks everyone, and you are emailed naming them. Re-subscribing seats them again without re-inviting. The refunds page carries the 14-day right and the exceptions in full.

Invite the first person from the People tab.

Connect a mailbox, buy a tier on the Billing screen, and the invitation takes an address, a level and a cap. Nothing of yours is handed over.