Inbox: Option to separate conversations by channel after merge
J
Jesús Cadena
Business Problem
Currently, when the same contact messages a business through multiple channels within the same workspace, Respond.io automatically merges all messages into a single conversation.
While this is useful in some cases, it creates significant operational challenges for teams managing high volumes across multiple channels.
Pain Points
- Loss of context for agents: Messages from WhatsApp, Facebook Messenger, Instagram, Webchat, etc. are mixed into one thread, making it harder to:
- Follow the conversation flow: Quickly identify which channel a message came from, Respond with the correct context and tone
- Operational conflicts: A conversation may be assigned to one agent or team, The same contact then engages via another channel (e.g. a different ad), Instead of creating a new case, the message merges into the existing conversation and inherits the previous assignment
- Mismatch with customer experience: Customers experience separate conversations per channel, but internally the team sees everything as a single thread.
- Reporting and scalability issues - Mixed conversations make it harder to: Track performance by channel, Maintain clean histories
- Scale omnichannel operations without errors
Desired Outcome
Introduce a workspace-level configuration to display conversation merging behavior.
N
Nabilah Binti Salleh
Merged in a post:
Channel-Specific Conversation Threads
Infinite Wireless
Current Behavior
When the same customer contacts us through multiple connected channels (for example, two different WhatsApp Business numbers), respond.io merges all messages into a single conversation timeline under one contact.
While a unified customer profile is valuable, it becomes difficult to organize conversations when each channel represents a different department or business function.
Requested Behavior
Keep one contact, but separate the conversation history by channel.
For example:
John Smith
WhatsApp Business – Sales
WhatsApp Business – Technical Support
Facebook Messenger
Each channel should maintain its own conversation thread and history while remaining linked to the same contact.
Why Workspaces Are Not a Suitable Solution
We understand that using multiple workspaces can separate conversations, but this creates several operational challenges.
Our business has a manager who oversees all customer communications across departments. With multiple workspaces, the manager would need to constantly switch between workspaces to monitor conversations, assign chats, and manage agents. This makes supervision less efficient and increases the risk of missing important conversations.
Additionally, many of our agents work across multiple departments. If each department is placed in a separate workspace, those agents would also need to continuously switch between workspaces throughout the day. This interrupts their workflow, slows response times, and creates unnecessary friction.
Using separate workspaces also means:
Separate settings and workflows to maintain.
Separate dashboards and reports.
Separate agent management.
Increased administrative overhead.
In short, workspaces solve the conversation separation problem by sacrificing the operational advantages of having a single, centralized workspace.
Benefits of Channel-Specific Conversation Threads
This feature would allow organizations to:
Keep departmental conversations organized.
Prevent Sales, Support, Billing, and other conversations from becoming mixed together.
Allow agents to focus only on conversations relevant to the department they are currently serving.
Reduce confusion when customers contact multiple departments.
Maintain a single customer profile without losing context.
Keep managers, agents, reporting, automations, and administration centralized within one workspace.
Why This Matters
Many businesses operate multiple WhatsApp Business numbers for different purposes, such as Sales, Technical Support, Billing, and General Inquiries. It is common for the same customer to interact with more than one department over time.
Currently, all interactions are merged into one timeline. As organizations grow, this becomes increasingly difficult to manage because unrelated departmental conversations become intertwined.
Channel-specific conversation threads would preserve respond.io's unified contact philosophy while providing the organizational structure needed by businesses that manage multiple customer-facing channels.