Currently, Front lacks a native mechanism to "undo" a merge. Once two conversations are joined, whether manually by an agent or through automated threading logic, they are effectively locked together.
In the fast-paced world of logistics, this creates a "Merged Entanglement" that poses four significant operational risks:
• Mixed Shipment Data: If an email regarding Shipment A is merged into a thread for Shipment B, critical attachments or instructions can easily be overlooked. A single missed detail in our industry can lead to a stalled truck or a failed delivery.
• Broken Analytics: Accuracy is the backbone of our operations. When two distinct business events are tracked as one, our "Time to Resolve" (TTR) and "Messages per Shipment" metrics become skewed, providing an inaccurate picture of team performance.
We propose a native "Unmerge" feature that allows users to split conversations back into their original, distinct components. Key requirements include:
1. Split by Message: A UI option to select specific messages or a range of messages within a merged thread and select "Move to New Conversation" or "Split from Thread."
2. Metadata Restoration: Upon unmerging, messages must retain their original metadata, including unique Message IDs, original timestamps, and sender information.
3. Audit Trail/History Log: To maintain transparency, a system note should be added to the activity feed (e.g., “This conversation was unmerged by [User Name]”) so the team can track why and when the split occurred.
For Enterprise users like us, an unmerge feature isn't just about UI convenience it’s about operational safety and data integrity.
• Operational Safety: It ensures instructions for different shipments remain distinct, actionable, and error-free.
• Data Integrity: It keeps our CRM and internal logistics tools synced with accurate, clear data from Front.
In professional communication, a "Merge" should not be a point of no return. We believe providing a way to disentangle threads will make Front a significantly more robust tool for any company handling complex, high-volume operations.
Who else in the community has faced this? Let’s bring this to the attention of the Product Team! 🚛 🚀
Unmerge Feature
+3As it turns out, this feature is not currently available in Front, BUT I’m still very happy you reached out about it. In fact, I encourage you to submit a request for it at this link.
This feature submission form is linked to our Product Ideas Portal which is accessible to all users. When features are submitted, they are listed in the Ideas Portal and can be upvoted by other Front customers who may want the same feature to improve their team's workflows. You'll receive an email update if your feature is developed and shipped! Exciting 
Most of the improvements you see to Front come from ideas and suggestions like yours, so thank you for making Front even better!
Login to the community
No account yet? Create an account
Use your Front credentials
Log in with FrontEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.