Skip to main content
Featured group

* Service Cloud *

Welcome! This group is dedicated to your success with Salesforce Service Cloud. Join the conversation here to stay up to date on the product, learn best practices, and everything in between. Use this group to review resources, ask questions, help each other, and share experiences. --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx

I'm setting up Service Plans on Cases. I'd like the Service Assistant to explain the customer's issue to the service rep somewhere in the Service Plan using a specific statement I supply.  

 

I put the statement into the Service Assistant's subagent's Scope (see below), but the agent won't say the statement anywhere in the Service Plan.  

 

"Your job is to assist service reps in identifying the reasons behind customer's hairdryers not turning on and providing the necessary steps to get the hairdryer to turn on.  

 

You must tell the service rep the following statement in the service plan, "When a hairdryer doesn't turn on the hair will remain wet." 

 

Similarly, I've added Instruction, "Review helpful guides, "How To Turn on Your Hairdryer" and "My Hairdryer Won't Turn On," but the agent won't say it either. 

 

Is this not possible? 

2 answers
  1. Yesterday, 2:02 PM

    @S N, Service Assistant is different than the other agent types, is grounded in subagent topics and instructions, and can't have subagent actions. The output of the Service Assistant is the Service Plan, so I don't think that approach will work.

0/9000

Track Service Rep First Response Time Automatically  A feature in Summer '26 is the above new metric which was designed to "Eliminate complex workarounds, uphold customer satisfaction KPIs, and ensure SLA compliance with a new metric that captures the exact moment a service rep sends their first reply in a messaging session. Service Rep First Response Time is now a value on the MessagingSessionMetricType field of the MessagingSessionMetrics object. Previously, identifying the actual moment a rep sent their first message required complex LWC development or API callouts to the ConversationEntry object."      However, testing of this appears to show the figure measures the time from the Messaging Session being created, to the moment a human agent first replies - so this includes the customer's initial interactions with the bot, customer inactivity time, time sat in the queue etc.  Should it not be the time difference between the first message minus the time it was assigned to the agent, to measure the individual Service Rep's service, similar to the other metrics?   Alternatively would a better design not have been to simply capture the date/time of the first human message and then we could have used formula fields to calculate the two metrics using the existing created, assigned and accepted date/time fields in Omni (1. total wait time to speak to a human & 2. how long the human took to send a message after accepting the MS).      In short, is there an easy way to derive how long a human took to send a message after accepting a MS, as this is what we were hoping "Service Rep First Response Time" metric would show us but it doesn't.    @* Service Cloud * 

1 answer
0/9000

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 * 

4 answers
0/9000

Hi everyone,   

We are experiencing an issue with inbound routing and are struggling to find the root cause. Hoping someone in the community has seen this before or can help troubleshooting this!   

Our Tech Stack:

  • Salesforce Service Cloud Voice (Partner Telephony)
  • Enhanced Omni-Channel
  • Genesys Cloud CX

The Issue: For specific agents (not all, but the affected ones experience it randomly), when a call rings in the Omni-Channel widget, they are unable to accept it. Clicking the "Accept" button does not connect the call.   

The call eventually times out, is routed back to Genesys, and pushed to the next available agent. Oddly, if it reroutes back to the same agent (after switching status), it might work perfectly the second time.

  Symptoms & Observations:

  • Agent Suspicion: Some agents feel this happens right around a status change or when their presence is flipping, but we have not been able to reliably reproduce this.
  • Because it only affects a handful of users repeatedly, we suspect a localized issue rather than a global routing failure.

  Could this be a browser-level WebRTC/headset issue where Omni cannot establish the audio path, causing the "Accept" click to fail? How to debug this?   

 

Any guidance or pointers on where to investigate next would be greatly appreciated. Thank you!   

 

@* Service Cloud Voice *  @* Service Cloud * 

1 answer
  1. Jun 2, 3:58 PM

    Hi @Mario Zoske

     

    If agents are able to reproduce or encounter the error, try collecting browser console logs using the browser's Developer tool.  

     

    Check the logs for any No Pickup event or WebRTC Microphone error. If found, try running a WebRTC Diagnostic Test. You may need to contact Genesys support for further investigation. 

     

    Additionally, try checking with a different browser or by clearing history or cache.  

     

    Also, there are several relevant threads within the Genesys community that might provide additional context or potential resolutions for this behavior.

0/9000

Hi Trailblazers! We're excited to share the the Summer ‘26 Release Overview Deck! For those of you who are new to this asset, it's a visual companion to the Release Notes and walks you through many of the newest enhancements. Use the quick links to jump through the deck to review new features and functionality for various clouds. 

 

11 comments
  1. May 31, 11:11 AM

    Is there any way to see these documents exaample in customer success or private groups as ouur company blocked the google slides or google drive accessing.

0/9000

We are migrating our Zoho Servicedesk to Service Cloud and looking for assistance with the data migration, specifically for case and emails associated to those cases. Is there anyone out there with recommendations of a vendor to use?

2 answers
  1. May 30, 11:27 PM

    We did a similar migration from another help desk platform into Service Cloud a few years back. The cases are usually the easy part, the email history, attachments, and maintaining the relationship between records tend to be where the real work is. 

     

    If you're evaluating vendors, I'd look for someone with specific Salesforce Service Cloud migration experience rather than a generic data migration shop. We’ve also used Skyvia for some cross-platform migrations and ongoing integrations, so it may be worth a look depending on how much transformation and email-related data needs to be preserved. The key question I'd ask any vendor is how they handle email threads, attachments, and case history, because that's often where surprises show up.

0/9000

We are seeing confusing behavior in the Case Activity / All Updates timeline where field updates and related actions are not appearing in a clear chronological story of what happened on the case.

In our scenario, multiple queue/status changes are happening through Flow automation, and Salesforce groups those field updates under a single “System” activity entry.

Example: System updates the case:

  • Queue changed from A to B
  • Queue changed from B to C
  • Queue changed from C to F

However, between some of those updates, other important activities (such as outbound emails) actually occurred, but those appear separately elsewhere in the timeline.

So the real sequence was something like:

  1. Queue changed from A to B
  2. Queue changed from B to C
  3. Email sent to customer
  4. Queue changed from C to F

But the Activity Timeline / All Updates view visually groups the queue changes together and makes it appear as though they happened continuously without interruption.

This is creating operational confusion because support users are unable to reconstruct the actual sequence of events on the case by looking at timestamps and grouped updates.

Questions:

  1. Is this expected Salesforce behavior in Activity Timeline / All Updates?
  2. How does Salesforce decide which field updates get grouped together?
  3. Is there any configuration or customization available to:
    • prevent grouping of updates,
    • show exact chronological ordering,
    • or improve visibility of interleaved actions like emails + field updates?
  4. Has anyone implemented alternative approaches for clearer case audit/history tracking?

We are mainly trying to improve the ability for support teams to understand the exact progression of a case without manually opening each activity entry.    

 

@* Service Cloud * @* Sales Cloud - Best Practices *  @Salesforce Flow Automation 

1 answer
  1. May 30, 9:24 AM

    Yes, that's expected. The All Updates feed batches consecutive system field updates under one "System" entry, and there's no setting to force strict chronological interleaving with emails. So rather than fight the feed, use the source built for this: Field History. 

     

    Turn on Field History Tracking on Case for the fields that matter — Status, Owner/Queue, anything your Flow updates. Each change then lands in Case History with its own timestamp and old/new value, ungrouped and in true order. The Case History related list (or a report on it) lets support reconstruct the exact sequence, and since emails carry their own timestamps you can cross-reference to see where an email fell between two queue changes. 

     

    So: keep the feed for the readable story, but point support at Case History when they need to prove what happened in what order. 

     

    One catch — because your queue changes come from Flow, double-check those fields are in the Case field-history tracking list. Untracked fields won't show, and there's a cap on how many you can track per object, so prioritise the ones that matter for the audit trail.

0/9000

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 * 

1 answer
  1. May 28, 2:08 PM

    The fun of EmailMessages... 

     

    EmailMessage.ParentId in a link to Case only.  

    EmailMessage.RelatedToId is only added when Enhanced Email is activated.  

    When EmailMessage.ParentId is Case, EmailMessage.RelatedToId is also case.  

     

    EmailMessage.RelatedToId provides a What Id relationship (for example Account, Opportunity). However, it is not the only relationship to other objects (especially Who Ids). For that, you need to look at EmailMessageRelate. This object provides all the relationships. 

     

    Rule of thumb. If you are specifically looking for Email Messages related to Cases, stick to the ParentId field.

0/9000

Hi everyone,

I need to implement a workflow for the following requirement:

  1. Inbound: Clients email their dedicated Account Managers directly to their personal corporate inboxes (no generic support inbox).
  2. Creation: The manager needs to convert that email into a Case under their ownership, including all attachments.
  3. Lifecycle: Once created, the manager handles the entire thread from Salesforce. Replies must go out from their individual email, and client replies must route back to the same Case automatically.

Our first thought was using Email-to-Case, but since emails go to individual AM inboxes, creating unique routing addresses for dozens of managers is not scalable and feels like trying to force the system (adding/removing addresses every time an AM joins or leaves is a maintenance nightmare).  

 

Based on your experience, what is the best architectural approach for this? 

It feels like a fairly common business workflow. 

 

Thank you!

3 answers
  1. May 28, 11:21 AM

    There is an Outlook integration but that really is meant for someone who never goes into Salesforce much and is continuing to tie emails to Salesforce.  The UI of that for us is clunky for a user and with our architecture and sharing/ownership models it doesn't work well. 

     

    I see two options for you.  Right now once it hits their inbox they just forward it on and it on to the e2c address.  It would tie to their contact record and they would have to remove and add the right person.  Then when they email for the first time they would have to remove their email address from the TO field and add the customers email. 

     

    You could try having each AM have a redirect rule on their mailbox but you'd have to be able to have a filter that finds only the right emails which likely could be tough. 

     

    In the first example I'll guess the manual work there is too much of a hassle but you can always right some apex or maybe even a flow to do the manual steps I mentioned.

0/9000
1 comment
0/9000