#Service Cloud107 discussing

Hello Salesforce Team,

I have a question regarding the EmailMessage object relationships.

How can we reliably determine if an EmailMessage is linked to a Case?

I noticed there are two fields:

• RelatedToId (“Related To”)
• ParentId (“Parent Case”)

I would like to understand the expected behavior between these two fields:

1. Can RelatedToId be populated while ParentId is empty?
2. Can ParentId be populated while RelatedToId is empty?
3. When an EmailMessage is linked to a Case, should both fields always contain the same Case Id?
4. Are there standard scenarios where the values differ?

From the documentation, I saw the note:  “RelatedToId and ParentId should have the same value when ParentId is set. You might see unexpected results otherwise.”

Could you clarify the standard Salesforce behavior and best practice to identify whether an email is associated with a Case?

Thank you.   

@* Service Cloud * 

We have a subset of contacts that are flagged as "inactive" for various reasons. When our CS teams, who use email-to-case, email out of SF, is there a way to filter out these contacts when they are adding "to" addresses in their email? 

Hi community, Agentforce becomes much more valuable once it starts working with real customer conversations, emails, and support workflows. 

But that’s usually the point where teams begin restricting what the agents are actually allowed to see. 

The result is less context, limited workflows, and AI that ends up far less useful than originally expected. 

At InCountry, we built AgentCloak so Agentforce can work with cloaked/tokenized data while authorized users still see the original values inside Salesforce. 

That way, teams can keep the workflows fully usable without exposing sensitive customer data across the AI layer. Happy to share more if relevant. 

please can anyone help? 

The current scenario is the following:

• Case Exists and is waiting on customer, with an agent assigned as the owner at that time
• Customer responds and case transitions to 'Response Received'
• Case is picked up and put onto the queue, however the system then removes the Owner

I would like the desired flow to be as described below: 

• Case Exists and is waiting on customer, with an agent assigned as the owner at that time
• Customer responds and case transitions to 'Response Received'
• Case is picked up and put onto the queue, with the agent owner retained
• If the piece of work gets to the top of the queue and is pushed to a different agent via Omni then as per standard omni process the owner is changed

route to particular queue based on customer intent from agentforec agent.can anyone guide please.Thank YOU ! 

I’m currently setting up Email-to-Case, but I’ve hit a hard roadblock with our institutional IT policies. Our IT department enforces a strict, global block on auto-forwarding emails to external addresses for security reasons.   

Since the standard out-of-the-box Email-to-Case fundamentally relies on that forwarding rule, I need an alternative way to get our support inbox flowing into Salesforce.

For those of you in higher ed who have faced similar strict policies:   

1. What alternative architecture did you use? Did you leverage Power Automate/middleware, an AppExchange tool, or something else to "pull" the emails via API?
2. If you did successfully get an exception from IT, how did you frame the request to get them comfortable with the setup?

Any insights or specific tool recommendations would be hugely appreciated!   

@* Sales Cloud - Best Practices *  @* Service Cloud *  @* Sales Cloud - Getting Started *