I am attempting to raise awareness about a specific end of life feature that I believe impacts more Customers than Salesforce Product Team believes. If you are using Service Cloud, and specifically Email-To-Case, please READ THIS!

Salesforce announced with the Winter release the introduction of a new feature to prevent case duplication. The feature will be using the "email coded header" to determine if there is already an existing case to link to versus creating a new one altogether. This is a great improvement over the current logic and there is absolutely no disagreement there. This feature is needed.

However, in introducing this feature, Salesforce has also announced the end of life for the case thread id, stating that the new functionality will adequately replace the need for a case thread id. What does this mean for you? Well, if you currently run an org that has built endless case email automation and were leveraging the case thread id as your means to control where that email goes (back to original case instead of creating new), you are now scrambling to find alternate solutions before they officially turn this off.

For those taking advantage of this current thread id functionality, it is not difficult to see that Salesforce is now introducing a huge product gap. There is absolutely a need for something that can steer an email reply back into a case.

I am doing my best to raise this awareness to Salesforce, but I unfortunately cannot do this alone. I am asking for a moment of your time (especially if this impacts you), to upvote and comment on this idea: https://trailblazer.salesforce.com/ideaView?id=0874V0000015Jh2QAE

Appreciate your time, and hoping we can drive some change before it is too late!