Playbooks, comparisons and field notes on running client relationships out of a shared inbox.
Every chat widget installs the same way, with one script tag. The decisions that matter come before that: who answers, what happens after hours, and where the chat lives once the visitor leaves.
Personal inbox-zero advice assumes one reader. A team mailbox needs five jobs done every day (triage, ownership, follow-through, record, review), the rules that keep them done, and the numbers that show whether it works.
A canned response saves the typing without cutting the person out, if it is short, has one job and leaves a line to write fresh. 24 templates by situation, and how to keep the library tidy.
A good auto reply says what arrived, when a person will answer, and what to do if it cannot wait. 16 templates by situation, the cases where an auto reply does harm, and setup in Gmail, Outlook, Microsoft 365 and WhatsApp.
An email thread is every message in one conversation, grouped by your mail client. How Gmail, Outlook and IMAP build threads, why they split, and the habits that keep a team's record whole.
One support@ login passed around holds for two people and breaks at three. What goes wrong, the alternatives in order of effort, and how to keep the address while retiring the shared password.
Once an admin makes you a member, the shared mailbox usually appears on its own after a restart. When it does not, here is the manual path in every Outlook client, and the seven reasons it stays hidden.
A distribution list copies one message into many inboxes. A shared mailbox is one inbox many people open. A Microsoft 365 group adds a workspace. The right one depends on whether anyone has to reply.
Sending from a shared mailbox is one control, the From field. The part that trips teams up comes after Send, when the reply files itself into your personal Sent Items. Both are fixed here.
A shared mailbox is free, and the price of free is a set of limits teams discover one at a time. The limits, the licensing cases, and the nine practices that keep a team mailbox working.
Two minutes in the admin center or one line of PowerShell creates the mailbox. The settings that decide whether the team can use it well take another five. All of them are here, including the conversion case.
Email group means three different things in Outlook. Steps for a personal contact list, a Microsoft 365 group and a distribution list in every client, and the case where a team needs a shared mailbox instead.
Google Workspace has no shared mailbox object. A Google Group with Collaborative Inbox, delegation, a shared login or a shared inbox tool each do the job for a different size of team.
A Collaborative Inbox is the closest thing Google Workspace has to a free shared inbox. How to turn it on, how assignment works, and the five limits that end it.
Delegation lets colleagues open one Gmail mailbox from their own accounts with no shared password. How to set it up, what delegates can do, and the point where a team needs more.
Gmail has no button called distribution list. A contact label does the job for one sender; a Google Group gives the team an address. Steps for both, and the point where a group stops being enough.
A shared inbox is an email address a team works together, where every message has an owner and a status. How it differs from a shared mailbox, a team inbox, a unified inbox and a help desk, and how to set one up on Gmail or Outlook.
Twelve rules for a team mailbox that stays answered: one owner per thread, few states, a typing indicator, notes on the thread. Each comes with the setting in Gmail, Outlook or a tool that enforces it.
Triage is deciding what to handle first. AI triage does that for every incoming thread, with a priority score, an intent tag and an owner. What it should never do, and how to test a tool before buying.
Eleven shared inbox tools, from Gmail extensions to help desks, compared on channels, collision detection, AI pricing and where your mail ends up living.
The category is a mess of bounce checkers and CRM lists. Here it is defined, then ten tools compared across shared inboxes, help desks and team email clients.
Intercom charges per seat plus $0.99 per Fin outcome and starts from chat. Nine alternatives grouped by the reason teams leave, with prices verified October 2026.
Zendesk's Suite starts at $55 per agent and every conversation is a ticket. Ten alternatives grouped by what you need instead, with prices verified October 2026.
The agenda with minutes per block, eight slides and what goes on each, the pre-read checklist and the questions to ask. Plus the mistakes that turn a review into a status update.
Four phases with an owner and an artifact per item, the handoff note sales has to write, and the introduction and kickoff emails. Plus the mistakes that show up in month three.
When to send the follow-up by situation, seven templates for an account (proposal, meeting, approval, overdue both ways, silence, renewal), and how to track what you are waiting on.
Five templates in order (first, second, third, breakup, re-engage), how long to wait between them, what to change each time, the subject lines that work, and the mistakes.
First response time, response time, resolution time and why the p90 matters more than the mean. Two verified benchmarks, a policy paragraph by channel, and what tracking looks like in Gmail and Outlook.
The WhatsApp Business app links four devices to one phone. Past that, a team needs the Business Platform. What each route keeps, what it breaks, and how to move a number.
Meta charges per delivered template message, by category and by the recipient's country. Replies inside the 24-hour window are free. The current rates, a worked month for a small client team, and where providers add fees.
Missive charges $14, $24 or $36 per user per month on yearly billing, with no free plan and a 30-day trial. What sits on each tier, how AI is metered, and what five and fifteen seats cost.
Hiver sells Growth, Pro and Elite at $25, $55 and $85 per user per month on annual billing, with seats bought in steps of five. What each tier holds, where the bill grows, and the five- and fifteen-seat math.
One inbox for every channel is sold as two different products: channels side by side, or one record per client. The difference shows up when a client switches channel mid-conversation.
Nobody plans to send a client two different answers in four minutes. Here is why it keeps happening in Gmail and Outlook, and the four ways teams stop it.
Follow the sun gives a distributed team coverage for free and loses context at every handoff. The handoff note, the assignment rules, and the four numbers that show whether it is working.
An ATS tracks applicants. A recruitment CRM tracks relationships. Neither is where the conversations happen. What a recruiting desk needs from each layer, seven tools compared.
Clients write on WhatsApp because it is where they are. The trouble starts when the number lives on one phone. How one number becomes shared work, what the Business Platform changes, and what a team inbox has to handle.
Microsoft 365 gives Outlook teams a shared mailbox for free, and it works until it does not. What it is, how to set it up, the Sent Items fix, and the five places it stops.
Hiver's idea is that the team never leaves its mail client. Every alternative keeps that promise or breaks it on purpose. Seven compared, prices verified October 2026.
Teams leave Missive when the team never fully moved in or the job changed. Seven alternatives, matched to the reason, with prices verified October 2026.
The headline is $25 a seat. The tier your requirements land on, the seat caps and the add-ons decide the number on the invoice. Every figure verified October 2026.
Front routes every conversation to the right person. Intercom resolves as many as it can before a person is needed. That difference decides the comparison.
One charges per seat and adds AI per resolution. The other charges per seat and per outcome. Underneath the pricing is a difference in what each desk is for.
Both are standalone apps that ask the whole team to move in. Missive is priced for a small team that wants everything in one window. Front is priced for operations at scale.
Hiver adds shared inbox controls to Gmail or an Outlook shared mailbox. Front moves the team into its own app. Where the mail lives decides the rest.
A laptop, a mailbox, and a spreadsheet of client names you have never met. Some of them are already leaving. Learning the product is the easy part.
QBRs get skipped because preparing one costs half a day of scrolling backward through Gmail or Outlook, and that cost lands on the busiest person you have. The agenda, and the prep behind it.
Every account team already runs on relationship memory. It lives inside particular people and resigns when they do. A definition, the relationship intelligence comparison, and four things it is not.
Gmelius, Drag and Keeping add team features to the Gmail screen. How they compare on price, scope and Outlook support, and the client record a layer does not keep.
Per-seat list prices for nine shared inbox and help desk tools, verified October 2026, and the costs that decide the bill once a team lands on a tier.
Front routes, Help Scout answers, Intercom deflects. What each customer communication platform is built for, and what fits when your customers are named accounts.
Eleven Front alternatives sorted by the job your team does, with channels, where your mail ends up, how AI is billed and prices verified October 2026.
Agency mail is organized by client. Help Scout, Helply, Hiver, Gmelius, Front, Missive and Sektra compared on where the team works, channels, price and fit.
AI that deflects tickets can help support and harm your top twenty accounts. On knowing which of the two jobs your inbox AI is for, before you aim it wrong.
Migration fear keeps teams on tools they have outgrown for years. If your mail lives in Gmail or Microsoft 365, that fear is a misunderstanding. Here is the two-week parallel run.
The account you lost last quarter didn't blow up in a meeting. It faded, one unanswered thread and one forgotten promise at a time. Five churn indicators, and how to see the fade early.
Hiver runs a support queue from Gmail, or from its Omni web app with Outlook. What it covers, what it costs, and what happens to a client after the ticket closes.
A team can answer every email in twenty minutes and still lose the account. What reply-time dashboards measure, what they miss, and three customer success metrics that do better.
Two weeks of notice, forty accounts, one handoff doc written from memory. The handoff problem is what gets lost when relationships change hands, from sales to success or from one owner to the next.
Help Scout runs a support queue. The alternatives, sorted by why teams leave it: AI pricing, routing, Gmail and Outlook, one app with chat, or clients who never close.
Deals rarely die from lost arguments. They die from forgotten follow-ups. On the anatomy of the promises hiding in your team's sent folder, and how to track them.
Missive puts email, messaging, team chat and tasks in one app. What it covers, what it costs, and the adoption question to answer before the whole team moves in.
A top shipper stops sending RFQs and no dashboard blinks. What a freight broker CRM holds, what a shared inbox handles, and the third thing a brokerage needs for named accounts.
Every CRM rollout begins with resolve and ends with a database of good intentions. The problem is that it asks humans to be scribes. An audit, and the alternative.
Connect a mailbox and Sektra builds the memory of your clients from the history already there.