Opening a thread shows the conversation and a place to reply. What that looks like depends on the channel, deliberately.
Most channels share a reader
Email, WhatsApp, calls, SMS, voicemail, bookings and signature requests all render in the same reader: the exchange in order, with the person it is with alongside.
That consistency is worth having. Somebody moving between an email thread and a WhatsApp conversation should not be learning a second interface halfway through their morning.
Web chat is a deliberate fork
Live chat with a website visitor renders differently, and this is a design decision rather than an inconsistency nobody tidied up.
A live conversation with somebody currently on your site is not an exchange of messages you read later. It is happening now, it needs visitor and agent turns clearly separated, it arrives live rather than on refresh, and it carries context about where the visitor is on your site.
Underneath, web chat messages live in their own store, keyed to the visitor's session rather than to a mailbox. Building one component for both would have made the shared reader worse in order to serve a case it does not fit. So there are two, and the inbox picks based on the channel.
Replying
The composer matches the channel.
Email gets formatting, Cc and Bcc, attachments and a signature.
WhatsApp gets what WhatsApp supports, and respects that channel's rules, which are covered in its own section.
Web chat gets a fast, plain composer, because a visitor is waiting.
Calls and voicemail are not replied to in text. The action is a call back, and the reply is a call record.
The composer is not a choice you make. It follows the thread, because replying to a WhatsApp message by email is almost never what somebody wanted, and switching channel deliberately is a separate act.
The person, not just the thread
Beside the conversation is who it is with, and that is a record rather than an email address.
Their previous conversations, their deals, their invoices, their meetings. The thread is one moment in a relationship, and the rest of that relationship is one glance away.
Look before you reply, particularly on anything reading as a complaint. A frustrated message from a customer who has been waiting three weeks needs a completely different answer from the same words sent by somebody you spoke to yesterday, and the two are indistinguishable from the message alone.
The other common case is the reverse: somebody asking a question you are about to answer generically, who turns out to be your largest account.
Turning a conversation into work
A thread can become a task, a ticket or a record, and it stays linked.
Do it when the answer is not immediate. A conversation needing work is one that will be forgotten if it stays only a conversation. The inbox is not a task list, and using it as one is how commitments quietly expire.
The link is the point. Whatever gets created remembers where it came from, so months later the question "why did we agree to this" has an answer that is not somebody's memory.
Internal notes
A note on a thread is visible to colleagues and not to the customer.
Use it for the handover: what you have tried, what you are waiting for, what you would do next. The person picking it up at seven in the morning gets your reasoning rather than just your messages, and does not start again from the top.
Two habits. Write the note before you snooze, because the version you would write tomorrow is worse than the one you can write now. And name the person if it is for somebody specific, so it reaches them rather than waiting to be found.
When more than one person is involved
A thread has one owner and often several people reading it.
The owner replies. Everybody else uses notes. Two people answering the same thread on the same afternoon is the failure this convention exists to prevent, and it happens most often on threads that look easy.
Hand over explicitly. Reassigning silently means the new owner finds out when they next scan the list, which may be tomorrow. A note naming them, then the reassignment, takes ten seconds and removes the gap.
Attachments and documents
Something arriving as an attachment is a file somebody sent you. Something living in Documents is a file your organisation owns.
Move the ones that matter. A signed agreement sitting in an email thread is findable only by whoever remembers the thread exists. The same agreement in Documents is findable by everybody, for years, without them knowing the conversation ever happened.
Everything else can stay where it landed. Not every attachment is a document.
Signatures
Email replies carry your signature, built once and applied to what you send.
Worth setting up properly. An unsigned reply from a business address reads as a mistake, and the signature is also where a customer finds your phone number without having to ask.
Two habits worth having
Reply from the thread, not from your own mail client. A reply sent outside the platform is invisible to everybody else, the thread will look unanswered, and the next colleague to open it will answer the same question again. This is the single most common cause of a customer receiving two different answers.
Close what is finished. Resolution is a state, not a feeling. A thread left open because it is probably done is one somebody else will re-read next week.
What the reader will not do for you
It will not tell you the tone. Text has no tone, and a short reply from somebody busy reads as curt to somebody anxious. When a thread is going badly, moving it to a call is usually the fastest repair available.
It will not decide urgency. Priority is a signal a person sets. Nothing about how a message arrived makes it more or less urgent than anything else in the list.
Did this answer your question?
No, ask a person