Skip to main content

#Service Cloud112 人正在讨论

We have had several reports of agents having issues with the Omni channel call controls. These agents are actively answering calls via omni channel, but when voice call record opens and they try to reopen the omni channel widget to use the call controls the buttons/numbers are greyed out, and unclickable. They end up stuck with the caller on the phone but unable to transfer. 

 

Similarly, on occasions agents are able to make outbound calls via click to dial for known contacts but the keypad is greyed out/unclickable if they try to dial a number manually.

 

Has anyone else experienced similar issues? 

Thank You 

John

4 个回答
0/9000

Hi, I am looking to create a case list view that shows all cases in a queue where the user is a member of. Standard functionality only supports one queue owner at a time. In our org, a user may be a member of multiple queues. Thanks in advance :)

#Service Cloud #Salesforce Admin
8 个回答
  1. 昨天,14:01

    Long past but I found this while looking for same answer. I found you can use Alias as the filter and it will work. I combined 4 queues into one list view using that. the queue name to use it the label, not the API.

0/9000

We need to verify how Accounts and Cases are mapped for inbound calls, transfer calls, and outbound calls in the Voice Call record. When we click a phone number from an Account, an outbound call is created and the RelatedRecordId field is updated with the Account ID. If we initiate a call from a Case or Lead, the respective record ID is automatically populated in the RelatedRecordId field on the Voice Call. Could you confirm whether this is standard Salesforce behavior? If so, please share the relevant documentation.    @* Service Cloud * 

0/9000

We are deploying Enhanced Bots (Einstein Bots) on our company website using Embedded Messaging. We've enabled "Conversation Transcripts on Data Cloud" to analyze bot conversation data via reports.    **Goal:**  We want to filter out internal employee conversations from analytics/reports so we can focus on actual customer interactions.    **Challenge:**  Since Embedded Messaging is accessed via a public website (no login required), there's no built-in way to identify whether a conversation was initiated by an internal employee or an external customer. The ConversationEntry data in Data Cloud doesn't include any user identity or IP address information.    **What we've considered so far:**  1. **Hidden Pre-Chat fields** – Using the Messaging Web API to pass a hidden field (e.g., a flag set by server-side IP detection) before the conversation starts. This seems viable but requires custom web implementation.  2. **Adding a bot question** ("Are you an employee?") – Rejected because it adds friction and may reduce utilization rates.  3. **Separate deployment per audience** – Deploying different Embedded Service configurations for internal vs external pages, but this adds operational complexity.    **Questions:**  - Is there a recommended or built-in way to tag/identify user type (internal vs external) in Enhanced Messaging conversations?  - Has anyone successfully used Hidden Pre-Chat fields with Enhanced Bots to pass custom metadata that appears in Data Cloud transcript data?  - Are there other approaches we haven't considered?    **Environment:**  - Salesforce Enterprise Edition  - Enhanced Messaging channel with Enhanced Bots   - Data Cloud enabled for conversation transcript analysis  - Embedded Messaging for Web (MIAW)   

 

@* Service Cloud * @* Salesforce Einstein * 

0/9000

We are creating a new profile for some users in another region and i would like them to see records that relate to their region only  

I have created  a sharing rule  when OWD (case) is private  

 

How do i remove members of a public group from a list views in the case object?

However, these users are still able to see the list view they are not members of. 

What am I missing please? 

 

 

 

#Salesforce Admin  #Service Cloud

3 个回答
  1. 6月11日 16:54

    @Kundan Kumar Jha

    , To ensure restriction I went to the Profile of users that need restricting and unchecked 'view all  and modify all' . Once I refreshed the Sharing settings worked as expected. 

    Thank you again

0/9000

Hello everyone,

We are currently using MIAW (Messaging for In-App and Web) in Service Cloud.

Recently, we’ve been facing an issue where Salesforce freezes when a user tries to change their Omni-Channel status to "Online" via the button in the bottom-left corner right after logging in.

Restarting the browser temporarily fixes the issue and allows them to go online. However, the next day, the same freezing issue occurs again. This pattern has been happening consistently for the past few weeks.

Has anyone experienced a similar issue, or does anyone know a solution or workaround for this?

Thank you in advance for your help!

  ーーーーーーーーー   こんにちは。 Service cloudでMIAWを使っています。   Salesforceにログイン後、オムニチャネル画面で、画面左下のオムニチャネルボタンよりオンラインにしようとすると、画面がフリーズしてしまします。  なお、ブラウザを再起動するとオンラインができるようになりますが、翌日またフリーズしているような状態がここ数週間と続いています。   同様の事象が発生している方、また解決策をお持ちの方がいれば教えていただきたいです。   よろしくお願いいたします。        

3 个回答
0/9000

Linking Multiple Salesforce Cases to One Jira Epic

 

 

If your support and engineering teams use both Salesforce and Jira, you've probably run into this: the same product issue gets reported by multiple customers, and each one becomes its own Case. Engineering ends up either creating a duplicate Jira ticket per Case, or loses track of how many customers are actually affected. 

 

One pattern that's worked well for our team is linking all related Salesforce Cases to a single Jira Epic (or Story/Bug), instead of 1:1 ticket creation. Support keeps managing SLAs and customer communication in Salesforce as usual, and engineering works from one consolidated Jira issue.

 

Where this pattern helps:

  • Product defects after a release – e.g., a payment failure generates Cases from 10 different customers. Link them all to one Epic (like PAY-301 – Payment Failure Issue) so engineering can see total customer impact while working a single fix.
  • Major incidents/outages – Support still opens individual Cases per customer for SLA tracking, but engineering only has to work from one linked Epic.
  • Escalations – When a Case turns out to be a known product-level issue, link it to the existing Epic instead of opening a new ticket.
  • Recurring/known errors – Keep one Jira issue as the source of truth and attach new Cases to it as they come in.
  • Enterprise accounts – Multiple concurrent Cases from the same account, same root cause, tracked centrally under one Epic.

Why it's useful across roles:

  • Support reps aren't chasing engineers for status — Case resolution is tied to Epic progress.
  • PMs can prioritize by customer impact, not raw ticket count.
  • Engineers get full context without leaving Jira.
  • Post-incident reviews are cleaner since everything's already linked.

How we set this up:

 

We're using a

Salesforce-Jira connector app that supports many-to-one linking directly from the Jira side (no Groovy scripting or middleware). Rough flow:

  1. A release causes 3 customers to report the same issue > 3 Salesforce Cases get created.
  2. Engineering opens one Jira Epic for the underlying problem.
  3. All 3 Cases get linked to that Epic from within Jira.
  4. Support can see the linked Epic's status without leaving Salesforce.
  5. When the Epic resolves, all linked Cases reflect it.

 

 

 

#Service Cloud  #Salesforce Admin  #Integration  #Jira Integration

0/9000

Hi 

I am trying to create the Case Hierarchy coupling that we have in the Case object. 

Creating an Ultimate Case Hierarchy

There are 8 cases related to the Original Case 

  

The Parent Case number doesn't display all the Related Case 

 

I create a formula field - Case Hierarchy  

 

BLANKVALUE(Parent.Parent.Parent.Parent.Parent.CaseNumber,  

BLANKVALUE(Parent.Parent.Parent.Parent.CaseNumber,  

BLANKVALUE(Parent.Parent.Parent.CaseNumber,  

BLANKVALUE(Parent.Parent.CaseNumber,  

BLANKVALUE(Parent.CaseNumber,  

CaseNumber))))) 

 

but this does not capture all related cases

related Cases.jpg

 

I can't figure out a way to capture on the linkage - any advise who be appreciated 

 

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

 

 

#Service Cloud

2 个回答
  1. 6月22日 12:55

    The standard Salesforce Case Hierarchy only displays records based on the Parent Case relationship. From your screenshot, the cases are linked in a chain rather than all pointing to the original case, so Salesforce is behaving as expected.

    If the requirement is to show all 8 cases directly under the original case, each record must have the same Parent Case value. If the chained relationship must be preserved, you'll need a custom solution such as an Ultimate Parent Case field populated via Flow or Apex, since formula fields cannot recursively build a complete hierarchy.

0/9000

We just enabled enhanced notes in our org and some profiles can't upload images (System Admin can). Wondering if there is specific permission I need to give the profiles in order for them to upload images/files.

 

The images are well in the dimensions and size Salesforce allows stated in the docs

 

Thanks in advance.

#Trailhead #Sales Cloud #Salesforce #Trailhead Community #Service Cloud

 

Users can't upload images in Enhanced Notes

 

image.png

1 个回答
0/9000

Morning  Our company has contacts within an Account who share the same email address.  We have web forms integrated with SF and we are finding that a Contact is submitting a form and his name name and email address are submitted as part of the form. However, the Case is assigned to another colleague who shares that generic email address.    I thought that Contact names were only populated on a 1-2-1 match and it more than 1 contact shared the same email address then the contact name field would be blank and the user would update the field when taking ownership of the case   

1 个回答
  1. 6月22日 12:19

    Hi, I am unable to understand the question. Can you mention what is the ask or review your question description? Thanks

0/9000