Working the Shared Inbox in Call: A Daily Routine
How a shared inbox keeps every customer message and phone inquiry in one list, with views, ownership, saved replies and a simple routine so nothing is missed.
When customer messages arrive in personal inboxes, three things go wrong. Two people answer the same message. Nobody answers a message because each assumed someone else would. And when a person is away, their messages wait. A shared inbox solves all three by making the work visible to the whole team.

This guide describes a practical way to run one: how to structure the work, how to reply well, and how to keep an eye on what is slipping. For the bigger picture of combining channels, read the unified inbox and help desk tickets.
What goes into the inbox
The more channels you merge, the more important discipline becomes. In Call the inbox collects customer messages from the channels you have connected, together with phone inquiries, the questions callers asked on your lines. Easy mode shows the same work in two tabs: phone inquiries and messages.
The parts of the inbox
- Conversation listEvery conversation on the left, filterable by state, channel and owner.
- ThreadThe customer's messages and your replies, in order, on the right.
- CountsHow many are in this view, how many are waiting on you, past the first-response target or unassigned.
- Reply boxWhere you write, attach and send, with saved replies and matching articles.
- Resolve / ReopenThe way to close a conversation and bring it back if the customer writes again.
Counts are the quiet hero. A glance at "waiting on us" and "unassigned" tells a supervisor in seconds whether the day is under control.
Working by view
Do not read the inbox top to bottom. Work by state, in an order that protects customers who have waited longest.
A good order of work
- OpenStart with open conversations. These need a first or next reply from you.
- Only mineFilter to your own conversations and clear those you own.
- UnassignedTake unowned conversations so none sits unclaimed.
- PendingCheck conversations waiting on the customer; chase politely or close.
- ResolvedSpot-check a few closed items to see that they were really finished.
The default view is Open. You can narrow by channel, by "only mine", and with the search box, which finds a conversation by name, phone number or words in it. The search is the fastest way to find the earlier thread when a customer says "I wrote to you last week".
Ownership and response targets
Shared does not mean ownerless. Every conversation needs one person responsible for the next reply. Agree a simple rule, for example: whoever replies first owns it until it is resolved, or the supervisor assigns it.
| Situation | Rule of thumb |
|---|---|
| New message, nobody working it | The first available agent takes it |
| Customer replies on an owned thread | The owner replies, or hands over with a note |
| Owner is away | A supervisor reassigns; do not wait for their return |
| Two people typed at once | The one who took ownership sends; the other stops |
| Complex or sensitive message | Assign to the most experienced person |
Agree a first-response target and watch the count of conversations that are past it. The target should be one you can really meet; a promise you cannot keep is worse than a longer promise you do keep.
Replying well and quickly
Speed and quality pull in opposite directions, and the answer is preparation. Write a small set of strong replies once, and spend your attention on the personal parts. In Call, the reply box offers saved replies that match the channel and, where one exists, the customer's language. It also suggests help articles matching what the customer asked; choosing one adds a line pointing to it. You can attach a file, within the allowed size and types.
- Answer the question in the first line, then add detail.
- Use the customer's name and one detail from their message so it reads as personal.
- Keep paragraphs short; people read messages on phones.
- End with the next step and who will take it.
- Read the reply once before sending; pasted text often needs a small edit.
For help writing reusable texts, see message templates in Call. When a thread is done, press Resolve; if the customer writes again, Reopen brings it back to the top of your work.
Checking that the reply arrived
After you send, read the line that follows. It tells you whether the message was sent, whether it was only saved, or whether the carrier accepted it without confirming delivery to the phone. A banner can also warn that replies on a channel are saved in the thread but not delivered.
Handling the difficult conversations
Most messages are routine. A few are not, and they decide how customers remember you. Slow down for these.
Three kinds of difficult message
| What it looks like | How to handle it | |
|---|---|---|
| An angry customer | Long, emotional, often repeated | Acknowledge the problem first, then give a concrete next step and a time |
| A vague message | "It does not work" | Ask one specific question rather than a list; make it easy to answer |
| A message that belongs elsewhere | Billing, legal or technical matters | Assign it to the right person, and tell the customer who will reply and when |
For an angry customer, resist the urge to explain what went wrong before you have said you are sorry it did. A hypothetical reply might begin: "Thank you for telling us. I can see the appointment was moved twice, and I understand why that is frustrating. Here is what I will do today." It names the facts, shows you read the thread and commits to action.
If a message needs a phone call, say so and offer a time. The call-back flow is covered in call-back requests. Add the outcome of the call as a note on the conversation, so the next person knows what was said.
Phone inquiries alongside messages
Phone inquiries are the questions callers left or asked on your lines, for example when the AI agent or voicemail took the details. They are easy to neglect because they feel like calls rather than messages. In the inbox they sit next to written messages, which makes it clear that they too need an owner and an answer.
- Treat a phone inquiry as seriously as a written message; the customer took the effort to call.
- Reply on the channel the customer used where you can, and by phone when they asked for one.
- Mark an inquiry as handled only when the customer has an answer, not when you have read it.
- Use the conversation history to avoid asking for details they already gave.
The same discipline helps your reporting. When every inquiry ends as handled or resolved, you can count them, spot the busiest days and plan staffing. See analytics overview for how to read those numbers.
A daily routine for a small team
Start-of-day and end-of-day checks
- Read the counts: waiting on us, past target and unassigned
- Claim or assign every unassigned conversation
- Clear open conversations, oldest first
- Review phone inquiries and mark each as handled when done
- Look for messages marked not sent and follow up another way
- Resolve finished conversations so the open list stays short
Small teams often combine the routine with a short hand-over note when staff change shifts. A line such as "three open, one waiting on a customer, one needs a supervisor" is enough to avoid duplicate effort. If your inbox is also fed by calls that need a call-back, link the two with call-back requests.
Frequently asked questions
What is the difference between Pending and Open?
Open conversations need a reply from your team. Pending conversations are waiting for something else, such as the customer's answer. Keeping them apart stops the open list from filling with items you cannot act on.
Can I see only my own conversations?
Yes. The Only mine filter shows the conversations assigned to you, which is the quickest way to clear your own work.
What does Resolve do?
It closes the conversation. If the customer writes again you can Reopen it, so nothing is lost.
Why does my reply say it was saved but not sent?
The channel could not deliver it. Common reasons are that the channel is not sending or the customer's details are incomplete. Read the reason shown and contact the customer another way.
Does the inbox send text messages?
Only when an operator has turned text sending on. Until then, messages on a text channel are saved in the thread but not delivered.
How do I find an old conversation?
Use the search box and enter a name, a phone number or words from the message. Set the view to All so resolved conversations are included.