Team inbox software sells two arrangements under one name, and the two work in completely different ways. One is a shared address. A queue at info@ or billing@ that several people work through together, where the software’s job is to stop two people answering the same message and to see that every message gets an answer. The other is a second person inside a named mailbox, working your mail, at your address, with your clients. Most small firms search for the first and need the second. The seat is the more expensive of the two in every way except the invoice.
The chapter before this one ends by turning the coverage question around. It asks who is in the inbox for the rest of the year, rather than who watches it for three days. Then how much of your working life they can read once they’re in. Then what the arrangement costs to keep. Three separate questions, asked in that order, and answered here in the same one.
The queue and the seat
Start by naming the two things. Almost every disappointing purchase in this category is a firm buying one and needing the other.
A queue is an address that belongs to a function rather than a person. Mail arrives for a role. Several people are entitled to answer, and any of them will do. What matters is that exactly one of them does, and that it gets picked up rather than sitting for three days while each of three people assumes one of the others has it. So the software is built around ownership: assignment, a state per conversation, and a record of who did what.
Both platforms a small firm already pays for have a version of this. Google’s is the Collaborative Inbox, built on a group. A member can “assign responsibility for a conversation to yourself or another group member”. They can mark one complete, mark one as needing no further action, or mark one as a duplicate of another. They can search by whether a conversation is assigned to them, to anyone, or to nobody. Each of those actions is gated on a group permission (checked September 6, 2026). Microsoft’s is the shared mailbox, an address that licensed users open alongside their own. It holds up to 50 GB “without assigning a license to it” (checked September 6, 2026). Above those sit the products built to do this properly, with routing, service levels and reporting, which is the category Front and Missive are in. What each of those costs a firm of your size, in money and in the afternoons somebody spends configuring it, is its own comparison.
A seat is a person inside somebody’s own mail. Gmail’s delegation and Outlook’s delegate access are the platform versions. Google defines a delegate flatly, as “someone who can read, send, and delete emails in your account for you” (checked September 6, 2026). The address is still yours. The clients still wrote to you. What changes is that a second human being is now reading the mail as it lands.
The difference that matters is a human one. A queue is anonymous on purpose, and its whole design assumes any competent answer will do. A seat exists because the answer depends on who gives it. The point of a seat is to get a second person close enough to your judgment that they can act with it rather than instead of it. Software helps a great deal with the first and hardly at all with the second. That’s worth knowing before you spend a Saturday choosing between two tools that both solve the first.
Which one your firm actually has
Three checks, and they take about ten minutes with your own mailbox open.
Where does the mail land? Go back over the last fifty client messages and read the To line rather than the body. If forty of them came to your name, what you have is one address doing the work of a department. A shared inbox tool gives you a well-organized place, and the mail keeps arriving somewhere else. This is the failure that costs firms the most. The tool works fine, the trial goes well, and your day stays exactly as it was.
Does it matter who answers? Take ten messages. Ask, honestly, whether any competent person in the building could have answered each one correctly. If the answer is yes for eight of them, a queue is genuinely the right shape. If the client wrote to you because you’re the one who knows what happened in 2023, assignment machinery leaves you where you started. What you’re looking for then is a way to bring a second person up to knowing.
Is the mail repeatable? A queue works on volume with low variety, which is exactly what a peak period produces. A quiet period produces the opposite: fewer messages, wider variety. The last chapter takes that apart, and the short version is that heavy mail is easier to cover than light mail.
Most firms that run those three checks find they’re holding both problems at once, in different proportions. That’s the useful outcome. Some slice of what reaches you personally is genuinely a queue wearing your name: the document uploads, the software invoices, the scheduling requests, the portal notifications. That slice can move to a role address and be shared cheaply, which shrinks the seat problem before you have to solve it. What’s left after the move is the part that only ever needed you, and it’s smaller than it looked at the start of the exercise.
What a second person can actually see
Here’s the part that decides how a standing arrangement actually feels, and it’s the one part people skip the documentation on.
Every platform shares in bigger units than the one you have in mind. What you want to hand over is a matter: the Halvorsen file, from March to now, with the two attachments and with the fee conversation left out. What the software offers you is a mailbox, or a folder. In both ecosystems the shareable unit is the container, rather than the thing a firm actually thinks in.
Gmail’s delegation is the clearest case. The delegate reads, sends and deletes, and the scope of that is the account. The account is the unit, whatever you had in mind: a client, a matter, a date range. A work or school Google account can carry up to 1,000 delegates and a personal gmail.com account up to 10 (checked September 6, 2026). A feature built with a thousand of anything in mind draws a broad line by design. Two further details about delegation change how a short absence goes, and they’re covered where that decision gets made. In a standing arrangement they weigh heavier still, because they apply every week rather than once.
What stays with you is the more interesting half. Google’s own list of exclusions includes Google Account settings, Drive attachments, Google Photos, Tasks, Smart Compose, Gemini in Gmail and encryption options (checked September 6, 2026). Read that as a sentence about work rather than about permissions. It says the delegate is handed the mail, and you keep the machinery you use to work the mail. Your task list, the drafting help you’ve trained, the files that live one click away from the message. They get the raw material on its own, which is a fair description of why a delegate’s first month runs slower than everybody expected.
The shared mailbox has the opposite problem, and Microsoft is admirably plain about it. The address belongs to the system rather than to a person. Every shared mailbox has “a corresponding user account with a system-generated password that isn’t known or intended for use”, and the guidance is to “always block sign-in for the shared mailbox account and keep it blocked” (checked September 6, 2026). Two consequences follow from that, and both are on the same page. Mail sent from it cannot be encrypted, “because the mailbox doesn’t have its own security context (username and password)”. And deletion stays open to everyone who can reach it: “You can’t prevent users from deleting messages in a shared mailbox.” A third line decides who is eligible at all, so it’s worth knowing before you plan around any of this. Access goes to people inside your business. People outside it, “such as people with a Gmail account”, can’t be given access, which rules out the fractional bookkeeper who sits on another tenant. The published caps that go with all this, and what the paid rungs above it cost, are in the same comparison.
Underneath all of that sits the thing to be clear-eyed about. Access is retrospective. The moment somebody is in, they’re in for everything already there. What’s already there arrived under a different arrangement, from people who wrote to you privately and were never asked. Three years of fee discussions, a client’s divorce, your candid view of a job that went badly. Whether that’s a problem is a question about your obligations rather than about the software. It’s the same question whether the second person is an employee or a tool. The guide on what a duty of confidentiality actually covers works through it, and the version that applies to hiring somebody is next to it.
The bill is not the license
A shared mailbox is free on a plan you already have, as long as it stays under fifty gigabytes and the people using it already hold licensed mailboxes of their own. Delegation is free too. So the price list tells you very little about whether a second person in the inbox is affordable. The costs that decide it sit off the invoice, and here they are.
What you stop writing. The first week after somebody joins your mailbox, you’ll catch yourself editing. The blunt assessment of a client’s plan gets softened. The note about why a fee was set where it was stays in your head. The difficult conversation moves to a phone call. All of that content survives. It relocates, to a channel that keeps no record, and the mailbox becomes a thinner account of the firm than it was before you shared it. This is a real cost, and it’s usually worth paying. Pay it deliberately rather than discover it. The cheap way is to decide in advance which conversations belong somewhere other than the shared surface.
The other person’s week. A mailbox handed to somebody who is already full moves the queue along rather than clearing it, and the last chapter has the arithmetic. In a standing arrangement the version that bites is quieter. The second person has capacity to spare. The trouble is that they’re underused. A stated remit is what turns reading into deciding. Leave it unsaid and you get somebody who reads a great deal and decides little, which costs a salary and returns a spectator.
Taking it back. Every grant has to be reversed, and the reversal is the step that falls off the calendar. The week somebody leaves is a week full of other things, and delegate settings sit at the bottom of the pile. Microsoft’s own note that you can’t prevent deletion in a shared mailbox is the same problem in the present tense. What you’ve given, you’ve given, and you find out what was in the gift afterwards. So write the removal down as part of the arrangement on the day you make it. It costs one line then, and an afternoon of uncertainty later.
There’s a fourth cost that’s really a design problem rather than a price, and it arrives about a month in. Two people who can both see a message is one thing. One of them having it is another. A firm that shares visibility and leaves ownership open has bought itself a new way to drop things. That’s exactly the failure a two-partner practice runs into, and what ends it is not a shared view but a spoken claim that lands somewhere both people read.
The seat you make the week before you go
Now the part that pays this series back. The coverage question and the team question point in opposite directions in time.
A seat created in the week before an absence is an empty seat. The person has access on the Friday and a blank history behind it. On the Tuesday they open a thread that started in April, and read every word of it correctly. Three things stay out of reach: whether the client is anxious or annoyed, whether the number in the third message was ever agreed, and whether the thing being asked for is normal for this client or the first sign of something. Access transfers text. The twelve months in which you learned what the text means stay with you.
So the useful measure of a second seat is how much ordinary time it has behind it. A person who has been in the practice’s mail for a year needs a page of instructions before you go. A person who was let in on Thursday needs a week of your attention, in the week you have least of it to give. The arrangement then costs more than it covers.
So the ordering runs the other way round from how most firms do it. The right moment to bring somebody in is the flat month, when the mail has the widest variety and the lowest volume. That’s the worst month to take leave and the best month to teach anybody anything. The two weeks before a vacation is when the decision usually gets made, because that’s when the absence becomes real. It’s the hardest moment to make it well.
That reframes what a second seat is for. The return sits in the fifty-one ordinary weeks, and coverage is what week fifty-two produces on top of them. Think of the reply that goes out at 11:00 instead of at 6:30 that evening. The document nobody had to chase, because somebody acknowledged it. The meeting somebody else booked. If a second person only earns their keep during your leave, the honest reading is that what you wanted was somebody covering for three days, which is cheaper and mostly a matter of setup rather than a person.
What has to move besides access
Three things have to get across for a second person to be useful. Only one of them is a permission.
A limit, said out loud. A figure they can commit on their own. Three or four situations with the answer already decided in the conditional. A plain instruction for anything that falls outside the list. This is the same object that makes leave work, and it’s where a well-run absence starts. In a standing arrangement the list gets edited rather than written once, and every genuinely new situation that comes up is a line to add to it.
A place a claim can live. Somebody saying “I’ve got the Halvorsen accounts, I’ll have them signed off Friday” is worth more than any amount of shared visibility. It works when it lands somewhere the other person reads in the ordinary course of the day. That means the feed they’re already in, rather than a weekly meeting, a chat app that gets opened on Tuesdays, or a status column in a tool nobody has open. Team chat and email keep drifting apart because they run on different clocks and end up in different applications, which is a problem in its own right.
A record that outlives the conversation. Whatever the two of you settle has to be written where a third person, or either of you in six weeks, can find it. This is the part that decides whether the second seat compounds or stays flat. A firm where the arrangement lives in two people’s heads has to rebuild it every time anyone leaves.
All three sit outside what access grants. Access is the cheapest thing on the list, the first thing every tool sells you, and the one that changes least about how the work actually goes.
What a seat in Point adds
Point isn’t a shared inbox and doesn’t offer one. That’s the first thing to say rather than the last, because it decides whether the rest of this section is for you.
Everyone signs in as themselves and keeps their own mailbox. Yours is still yours, still running on whichever of Gmail or Microsoft 365 the firm was already on, at the address your clients have always written to. What a firm shares is an organization: one business with several people inside it, each working their own mail on one surface. Sign-in is a magic link rather than a password, which reads less as a feature than as one fewer thing to reset when somebody’s laptop is replaced. Billing is per seat, added when somebody joins and stepped back down when they go. There’s no published price during the private beta.
The half of this that answers the section above is where a claim lands. Email and the team’s own conversations sit in one feed rather than in two applications. So the sentence about who has the Halvorsen accounts sits beside the mail it refers to, and whoever else is in the practice reads it in the ordinary course of the day. That’s a duller capability than assignment states, and a more useful one in a firm of six, because it stays current on its own.
Two boundaries are worth stating flatly, because both cut against what team software usually does. Tasks are personal. Your list is yours and your colleague’s is theirs, and each of you reads your own. That’s the arrangement rather than a gap in it. And how far Point goes on its own is held separately for every kind of action, along a range that runs from suggest-only to fully handled. The middle position, review, is where everything ships. That setting belongs to the person whose mailbox it governs, rather than to an administrator setting one level for the firm. The dial takes the positions one at a time. So your firm’s automation goes up one mailbox and one action at a time, and somebody else’s choice about their mailbox leaves yours exactly as you set it.
Membership itself is the control worth treating carefully. It belongs to a business. A person invited into one business is in that one. A person in two is in two because you decided it, which is how one business stays out of another’s mail.
And the honest limit, said once. If what your firm actually needs is a queue at info@ with routing, states, service levels and a report on how fast it’s being cleared, that’s a shared inbox product, and you should buy one. Point compared with Front is the long version of why. It comes down to what the software is trying to make less of. A support platform is built to reduce how many customers reach a human, and a practice is paid for the human reaching the customer. Everything Point does is the flat inventory.
Which business you are inviting them into
There’s a question the invitation asks before it asks anything else, and it’s easy to click past.
Which business is this person joining? For a firm that is one thing, the answer is so obvious it passes straight by. For the owner who runs the practice and one other thing, the question has sat open for years. Until now there was exactly one person in both, and it could stay theoretical. Adding a second person is the moment the line becomes real. The invite dialog is where it gets drawn, by you, in about four seconds, usually while you’re thinking about something else.
Which is the next thing this series has to deal with. How many inboxes there are, rather than who else is in one. What it takes to move between two businesses and keep the mail of each in its own place. And what the people you just invited can see when you do. That’s switching between two businesses you run, and it’s where this series ends.