When using Email‑to‑Timeline with Salesforce Cases, emails that clearly belong to the same Case can show up as multiple separate conversations in Timeline. This happens because Timeline relies on Microsoft Exchange’s Conversation ID for threading, and that ID isn’t preserved when emails are generated or replied to via Salesforce. Salesforce can create parallel reply chains for the same Case, Exchange assigns new Conversation IDs, and Timeline then fragments what is logically a single support conversation.
This isn’t a bug in Gainsight or Exchange, and it’s a known limitation of cross‑system email threading. However, from a user perspective, the Case is the real unit of work — not the underlying email conversation metadata.
The idea is to introduce Salesforce‑aware grouping in Timeline:
- For emails associated with a Salesforce Case, group Timeline entries by Case ID or Case Number
- Do not rely solely on Exchange Conversation ID in this scenario
- Apply this only to Salesforce Case–linked emails (no change to Outlook or Salesforce behaviour)
- Ideally make this optional or configurable
For example:
- A single Case generates agent replies, system notifications, and follow‑ups
- All emails relate to the same Case, but arrive with different Conversation IDs
- Timeline currently shows multiple fragmented conversations
- With Case‑based grouping, those emails would appear as one cohesive Case thread
This would:
- Preserve business context for CSMs
- Reduce noise and fragmentation in Timeline
- Align Timeline more closely with how support interactions are actually managed when Salesforce Cases are involved