| Value | ★★☆ | Effort | ★★☆ |
Seriously, email chains can touch all sorts of topics. With ability to communicate over a specific thing like customer property or a sales opportunity, it becomes possible to limit a number of in-between entities cluttering UX and the org itself.
Speaking of cluttering, Threading Tokens Are Exempt From Salesforce Org Storage Policy. Pretty nice opportunity to relieve a burden of overfilled storage.
But [please!] don’t forget to come up with a data retention strategy if you don’t have one yet.
Salesforce: “Previously, threading tokens were restricted to Cases. Now they’re a platform feature, and you can use them to thread responses to emails for any object that supports activity tracking.
[…]
To set up token-based threading for objects other than Case, create an Apex Email Service. Use the EmailMessages.getRecordIdFromEmail function to find the record that matches the token“
Sources: Use Threading Tokens with More Objects, Threading Tokens Are Exempt From Salesforce Org Storage Policy