Email collaboration for a small team
The team norms behind a shared address: who may speak for the company, how five writers sound like one, and when a thread should become a call.

Guides on support email, shared inboxes and running a support queue, from the Chirp team. RSS feed.
The team norms behind a shared address: who may speak for the company, how five writers sound like one, and when a thread should become a call.

Support escalation on a team of five is a handoff, not a promotion. The five things that get escalated, the four it needs, and the two channels you have.

An alias, a catch-all and a forward are three shapes for one support address. What each does when a message arrives, and which to pick at 20 a week and at 200.

What Hiver users praise and complain about, sourced from Hiver's dated public feedback board, a named customer and the review platforms, with links.

A thread is a set of headers a client rebuilds every time it opens a folder. How Message-ID, In-Reply-To and References build it, and what a split costs.

The routine for a shared address: who owns it this week, how two people avoid answering the same message, what done means, and the few readings worth keeping.

Full Access, Send As and Send on Behalf on Microsoft 365, delegated accounts and Groups on Google Workspace, and what to set for five people.

Support triage sets the order of the queue and decides whether a message needs a person at all. The four decisions it makes, and the signals to sort on.

What Help Scout users praise and complain about, from public threads, two named organisations that moved off it, one customer who stayed, and four platforms.

There is no convert button. Create the shared mailbox, add the members, then move the old list address onto it. The Microsoft 365 and Workspace steps.

What is worth automating on a shared address in Outlook and Gmail, the two limits you will hit, and what to do about the thread that goes quiet on day three.

Most of the time a team inbox and a shared inbox are the same thing. Where the labels differ, how to tell which one a product page means, and what to ask.

A catch-all address collects every message sent to your domain that matches no real mailbox. Where that helps, what it quietly swallows, and who should read it.

What free help desk and shared inbox tiers actually include, where each one stops, what crossing the boundary costs, and when to stay on free.

Proactive support means telling a customer about a problem, a change or a fix before they ask. The forms it takes, and the record it needs to work.

The three ways Google lets several people answer one Gmail address, in order of setup cost: a Collaborative Inbox group, delegation, and the login to skip.

What Missive users praise and complain about, from Missive's own public feedback board, review platforms and public threads, with dates and links.

A distribution list delivers one message to many inboxes and keeps nothing in the middle. Where the mail goes, and why it suits an announcement but not support.

The yearly bill for eight support tools at five people, the seat counts where the price changes, and the charges the per-seat price leaves out.

Help Scout, Zendesk, Freshdesk, Intercom and Front at the tier that does email ticketing, the free Google and Microsoft options, and when a shared inbox wins.

A roundup of what Front users praise and complain about, drawn from public threads, a named team that left and the review platforms, with every source linked.

Freshdesk's published tiers, what 3, 5 and 10 agents cost, where the free program ends, what each tier gates, and the Copilot charge on top.

One runs your email, the other runs a support function. The scope difference, the price difference, and which of the two a small software team should buy.

Freshdesk's free program ends at six months and two agents. The alternatives for a two-person team: a shared Gmail login, Missive, Front, Help Scout and Chirp.

Help Scout, Zendesk, Freshdesk, Intercom and Front, priced from each vendor's own page, with the sentence that says who should not buy each one.

Intercom's published tiers, the Fin charge of $0.99 per resolution, what 3, 5 and 10 seats cost, and what the alternatives charge for the same team.

Zendesk's published UK tiers in pounds, what 3, 5 and 10 agents cost, what each tier gates, and what the alternatives charge for the same team.

Sharing one Gmail password costs you the record of who replied, a per-person revoke and a clean recovery. The alternatives, priced and linked.

A Google Group is an address with a membership list. A shared inbox is an address with a queue. How to tell which one yours is, and who should keep the group.

A Google Group, a shared login, Gmail delegation, Hiver, Keeping, Missive, Front and Chirp, sorted by whether your mail has to stay in Gmail.

Tiered support splits answering into L1, L2 and L3 so volume routes to the cheapest skill that can close it. What each level does, and when to skip it.

A service level agreement is a contract with consequences. Most small teams want a target rather than an agreement, so this covers what to write down instead.

CSAT is the share of survey answers that land at the top of the scale. What the score counts, why response rates are low, and what a five-person team can do.

Hiver's Growth, Pro and Elite prices for both products, what 2, 5 and 10 seats cost, the 7-day trial, and what the same team pays on Chirp.

Missive's published tiers, what the API tier adds, what 3, 5 and 10 seats cost on annual and monthly billing, and what the alternatives charge.

What Gmail delegation really does, what it cannot do, and the point where a team answering one address outgrows it.

Every Help Scout tier, what 3, 5 and 10 people pay annually and monthly, where the free plan stops, and what Front, Missive and Chirp cost the same team.

Missive, Front, Hiver, Help Scout, a shared Gmail login and Chirp, priced and compared. One vendor's honest list, with the row that rules each tool out.

Keep Google Groups if the address is still a list. If it is not: a shared Gmail login, a shared mailbox, Missive, Front, Help Scout and Chirp, with prices.

Hiver at $25 per user, Missive, Front, Help Scout and Chirp at $9: which shared inbox fits a small software team, and who should stay on Hiver.

Zendesk is strong when support is a job. For a small software team that answers its own mail, here are the alternatives, with live prices.

A help desk turns support requests into tickets with owners, queues and response targets. What the category includes, who it is built for, and where it stops.

First response time measures the wait between a customer's message and your team's first reply. Which events stop that clock, and how an auto-reply distorts it.

A support ticket follows one request from arrival to close, with a state, an owner and a history. The states, the vocabulary, and when you do not need software.

Front's published tiers, what each one includes, what 3, 5 and 10 seats cost, and what Missive, Help Scout and Chirp charge for the same team.

Help Scout is the right tool for some teams and the wrong one for others. Compare Help Scout, Missive, Front, Zendesk and Chirp by price and free plan.

Front prices and gates each tier, and it is built for a support function. The alternatives for a small team that answers its own mail, with live prices.

Missive at $14 per user, Front at $25, Help Scout, a shared Gmail setup and Chirp at $9. Which to pick for a small software team.

A team of 2 to 20 people usually does not need a help desk yet. What a shared inbox handles, what a help desk adds, and the signals that mean it is time.

A shared inbox is one address several people answer from. How it differs from a shared mailbox, a distribution list and a help desk.

Which greeting to open with, how to address one person or several, and what to do when you do not know the name. With a table for every common situation.

Copy-ready out-of-office examples for a day off, a holiday, parental leave and a conference, plus the four things every auto-reply needs.

What belongs in a work signature, what to leave out, the size and format to use, and how to keep a team on one version when several people answer.

Why systems send from addresses nobody reads, what happens when you reply anyway, and how to send automated mail that people can answer.

One address, several people, shared visibility. What a collaborative inbox does well, the four ways teams build one, and the four ways they fail.

Pick the right email sign-off for the situation, see what each one signals, and decide what a team sharing one address should send.

One forwards, one stores. Which to use for support@, billing@ and announcements, and why neither tracks who is answering.

What CC and BCC do, who can see them, what happens when someone replies all, and how both behave on an address a team shares.
