When a customer writes to a team rather than a person, two questions decide whether they get a good answer: who is handling this, and what has already been said? A shared conversation view lives or dies on those two questions. This article offers a practical lens for judging any such view, and is plain about which parts the MailCircle preview shows and which are not built.
The situation: three people, one customer, one question
Imagine a small travel desk with three people answering customer emails. A family writes in about changing the dates of a booked trip. One colleague sees it and thinks, "I'll answer after lunch." Another sees it and starts drafting a reply. The third remembers the family called yesterday and was promised a call back.
Nobody did anything wrong. But the family may now receive two different emails, or none, and neither will mention yesterday's call. The problem is not effort. It is visibility.
The tension: chat is good at "what was said", email is good at records
Teams often split their work across two tools. Internally they discuss customers on a chat app, where it is easy to see the back-and-forth and tag a colleague. Externally they reply by email, where each message is a formal record.
The split means the internal discussion and the customer email sit in different places. The person drafting the reply may not see that a colleague already promised something. The person reading the chat may not know whether the email went out.
The insight: a shared view needs to answer five questions at a glance
Whatever tool a team uses, a shared conversation view earns its place only if anyone on the team can answer these questions quickly:
- Who is handling this? One clear owner, visible to everyone.
- What has been said to the customer? The actual history, in order.
- What has been said internally? Notes and mentions that should not go to the customer, kept clearly separate.
- Is this a draft or has it been sent? No ambiguity, ever.
- What is unclaimed? Items nobody has picked up yet.
Add a sixth if your team answers similar questions often: is our wording consistent? Shared, agreed phrasing reduces the risk of two colleagues telling a customer two different things.
Using the lens on the MailCircle preview
MailCircle is a concept and interface preview. Here is how it maps to each question, honestly.
Who is handling this?
The preview includes assignment surfaces for teams, and inbox-style views filtered by mine, unassigned and all. These show what a team view could look like. They are UI only: there is no live routing, and assignments are not shared between people's devices.
What has been said to the customer?
The preview's conversation views show drafts within a chat-style layout. However, because the preview does not connect to a mailbox, there is no real customer history in it, and replies do not come back into the chat. A live version would need both outgoing messages and incoming replies in the same conversation for this question to be answered properly.
What has been said internally?
Threads and mentions views exist in the preview's chat-style layout, alongside channels, groups and direct-message draft views. This shows the shape of how internal discussion and customer email could sit side by side. See the conversations preview.
Is this a draft or has it been sent?
In the preview, everything is a draft. Send is disabled. That makes the answer simple today, and it is the principle we hold for any future version: make "draft" and "sent" impossible to confuse. We explain why in a separate article.
What is unclaimed?
The unassigned filter shows where unclaimed items would appear. As with assignment, it is an interface surface rather than a live queue.
Is our wording consistent?
Local quick replies let you save reusable wording. In the preview they are stored in the browser, so they are personal rather than shared across a team. Shared quick replies would be part of any live team version.
What a live shared view would also need
Beyond the five questions, a team using customer email for real would need things the preview does not attempt:
- A connection to the team's actual mailbox, so emails go from the right address.
- Real delivery, with a visible record of what went out and what failed.
- Replies landing back in the same conversation.
- Durable, backed-up storage, not browser-local drafts.
- Attachments, which many customer emails need.
- Permissions: who can see, draft, assign and send.
None of these exist in the preview. Live routing and a live shared inbox are not built.
How to use this lens in your own evaluation
Take one realistic but invented customer conversation, such as our travel desk's date change. Walk it through whatever tool you are considering and, at each step, ask the five questions out loud with a colleague. Where the answer is "I'm not sure", you have found a gap that will cost you with real customers.
When you try the MailCircle preview, use sample names and addresses only. Look at the assignment and mine/unassigned/all views as a picture of the intended direction, and note what your team would need to be true before relying on it. The evaluation page has a fuller checklist, and the customer-facing teams page explains where we think the fit is.
