A customer writes to info@yourcompany.com with a problem. The message lands in three inboxes. One person assumes another will answer. Another forwards it to the person they think handles it, who is out this week. Four days later the customer writes again, a little less patient, and this time copies your owner.
Nobody did anything wrong. The email worked exactly as it was set up to. The trouble is that it was set up for correspondence, and the customer needed a request handled.
Two jobs that look the same
Regular company email is built for correspondence. A person, or a group, receives messages and replies. It's how your staff talk with vendors, partners, each other and the occasional customer. It works because each conversation belongs to the person in it.
Customer-service email is built for managing requests. Each incoming message becomes a case that can be tracked, with an owner, a status, a history and a resolution. It works because the request belongs to the team, not to whoever happened to open it first.
Both arrive as email, and both look the same in the customer's mail app. Behind the address, they need different tools.
One address, one queue
A single customer-service channel gives customers one address, such as support@yourcompany.com, and gives your team one shared queue behind it. Every request goes into the same place, and everyone who handles requests works from that list.
Most businesses get there a different way: a group address here, a forward there, an alias for billing, a distribution list for the service team. Each piece routes mail somewhere, but none of them manages the work once it arrives. Here's how the two compare.
- Who has the message. With forwards and groups, a message may be copied to several people or passed along by hand. In a shared queue, one request has one record and a clear owner.
- Whether anyone replied. With forwards and groups, it can be unclear who answered, or whether anyone did. In a shared queue, the team can see each request's status and every reply sent.
- Where the history lives. With forwards and groups, the context sits in individual inboxes and leaves when someone does. In a shared queue, it stays with the request when staff change or someone is out.
- What happens next. With forwards and groups, follow-up depends on each person's habits. In a shared queue, unanswered and overdue requests come to the surface on their own.
Accountability the customer never has to think about
The main reason to choose a shared queue is accountability, without asking the customer to work out whom to contact. They write to one address. Your team decides who owns it, and everyone can see that it's being handled.
That matters most at the moments customers remember: when the usual person is on vacation, when an issue needs to go to someone more senior, or when a reply was promised for tomorrow.
When a shared mailbox is enough
Not every business needs a service queue. If one or two people answer a handful of requests a week, a shared mailbox may be all you need.
A queue earns its place when:
- Several people handle requests
- Issues regularly need escalating, or handing from one person to another
- Customers expect a reliable reply and follow-up
- You want to know how many requests come in, and how quickly they're answered
Keep the two separate
Customer service works best when it's separate from company email. Your staff keep their own inboxes for correspondence, and customer requests go to a queue built for them.
Alpine Desk
That's why we built Alpine Desk, a shared inbox for customer service. We built it for Alpine's own support first, and we use it every day.
- One queue for the whole team. Shared addresses like support@ and info@, and each person sees only the mailboxes they've been given.
- An owner and a status for every request. Assign a conversation to a teammate, tag it, snooze it until a set date, or give it a due date. You'll see when a teammate is already replying.
- The history stays with the customer. Each customer has a profile with their full history with you, and internal notes sit beside the conversation where the customer never sees them.
- More than email. Texts, voicemail and (yes, even) fax can land in the same queue, each linked to the customer who sent it.
- AI help, with a person in charge. Every conversation gets a short summary and a next step, and suggested replies in your voice. Nothing is sent automatically: a person reviews every reply and presses Send.
Alpine Desk is in beta, and we're setting it up for clients who want it a few at a time through November, so each team gets proper help moving their service mail over. If your service/support email has outgrown its forwards and aliases, let's talk.