Skip to main content

#Service Cloud83 discutindo

We created a new email-to-case configuration and new organization-wide email address in a sandbox. The configuration was done by our Release Management user (which doesn't have the System Administrator profile).    End users received their respective verification emails but were unable to complete the verification process. They clicked on the link in the email which opened up a browser window with the Verify Email Address button. After clicking on the Verify Email Address button, the browser screen appeared to be refreshing or reloading for several minutes and never displayed a confirmation message. We confirmed the verifications were still pending in setup.    We worked with multiple users and retriggered the verifications multiple times (ensuring that links in the email were only clicked on once) but the only way we could get a successful verification was if the person retriggering the verification and clicking on the link in the email had the System Administrator profile.    I submitted a Salesforce Support case to inquire if there was a process change. The resolution indicated that there might be an issue with a Summer '26 patch and timing of user verification of email addresses on their own user record in our sandboxes. We did some light experimentation in other sandboxes but still couldn't get the verifications completed without a System Administrator. Given the resolution we had been provided, it seemed that we shouldn't encounter the issue in production so we moved forward and created the email-to-case and organization-wide email address in production.    Unfortunately, we had the same issue in production so someone with the System Administrator profile both retriggered the verification emails and clicked on the verification link in those emails.   

Has anyone else encountered this behavior?    TL;DR, someone with the System Administrator profile had to trigger the verification email AND click on the verification link in that email in order to successfully verify new email-to-case and organization-wide email addresses.

 

7 respostas
0/9000

Hi, 

When emails are sent from cases, don't receive any out-of-office messages or failed email messages.  In one case there was a typo error in the email address, but didn’t receive an error message like the one you get when you send an email incorrectly in Outlook. Can Salesforce capture and display Out-of-Office responses or email bounce-back messages for emails sent from Cases? Are there any email settings, Email-to-Case configurations, or deliverability options that need to be enabled to receive these notifications? 

 

Thanks. 

 

#Salesforce Admin  #Salesforce Developer  #Service Cloud  #Case Management  #Email Deliverbility  #Email

2 respostas
  1. Ontem 18:39

    One important nuance to add to Kundan's answer, because this trips people up on Cases specifically: 

     

    Bounce Management (Setup > Deliverability) flags the Contact/Lead/Person Account record, not the Case. Even with it enabled you will not get a bounce badge on the Case's email message itself, and 'Return bounced emails to sender' delivers the bounce notice to the sending user's own inbox, not onto the Case timeline. It also only kicks in reliably when the recipient resolves to a Contact/Lead/Person Account email, a free-typed typo address that matches no record can bounce with nothing flagged in Salesforce at all. That is most likely why your typo case showed nothing. 

     

    How OOO replies and bounce (NDR) messages actually behave: they are just inbound emails sent back to whatever From/Reply-To you used. If you send from the Case using your Email-to-Case routing address, those replies DO come back into Salesforce, but by default they usually create a brand-new Case rather than attaching to the original, unless threading matches them up (Lightning header-based Email-to-Case threading, or the legacy Ref ID token in the subject/body). So the first thing I would check: search for Cases created from the mailer-daemon or the recipient's mail server around that time. Your OOO and bounce messages are probably sitting there as separate cases. 

     

    If what you actually need is a reliable per-message 'did this bounce?' status shown on the Case, native Case email sending does not expose that. For that, route sending through an external email service/relay that reports bounces via webhook (e.g. SendGrid, or Email Relay with a mail server that returns delivery status), or use Marketing Cloud / Account Engagement for tracked sends. Those give true delivered/bounced status per message. 

     

    Quick checklist: 

    1. Setup > Deliverability: Bounce Management ON (flags Contact/Lead recipients). 

    2. Confirm you are sending with the Email-to-Case routing address as From/Reply-To so replies return to Salesforce. 

    3. Verify Email-to-Case threading (Lightning threading or Ref ID) so OOO/bounce replies attach to the original Case instead of spawning new ones. 

    4. For guaranteed per-message bounce status, use an external relay with bounce webhooks or MC/Account Engagement. 

     

    If this helps, please mark it as the Best Answer so it is easy for the next person to find. Thanks :)

0/9000

Does anyone know what could prevent pre-chat values from populating on the Messaging Session?    Chatters are entering the information - you cannot begin a chat without values in the fields and we have seen the greeting, which uses the entered first name, populated in the Messaging Session transcript.    We are missing the First Name, Last Name, Email fields but the Drop down field we have is being captured.  We have a few hidden fields for contact matching and information for our Customer Service group.    The Case registers the person as a Guest. The Initial question entered by the chatter is captured in the case Subject and the conversation is on the Messaging Session related list - Around 17 in the past few months with a case load of 50-100 per day depending on the season.  We have peaks near admission deadline and graduation ceremonies.    Any insight is welcome.   

 

@* Service Cloud * 

9 respostas
  1. Ontem 22:52

    Hi @Pam Willis-Tozier, what was your workaround/solution to this? Did you update the Pre-Chat Display Frequency to "Every Conversation"? Were there any implications for switching over from "Every Session"?

0/9000

All I am trying to add description field on Asset related list it's quite strange the field description (its standard field with type =text area) is not available in available filed section   Ill Appreciate your thought Field Not available to add in related list

 Thanks, intkhab Samani.

1 resposta
0/9000

The chatbot says "no agents are available" and fails to route even when agents are online and have capacity. I've already looked at this article and I do not believe that any of these issues: https://help.salesforce.com/s/articleView?id=000320363&type=1  Anyone have any ideas about why this may be happening?

1 resposta
  1. 18 de ago., 07:00

    Can you please provide me  the Omni channel Configuration page so that i can verfiy it  

    ,Beacuse i think its not problem of chatbot ,Kindly check  Omni-Channel routing configuration. 

    Thanks

0/9000

Need help on what field to choose so that I can send it to campaign members.

Survey Invitation to campaign members

1 resposta
0/9000

Hi Team, 

 

I am looking out for a hand-on trailhead for the following scenario. I have been able to find one but not able to find the others. 

 

Below is the scenario which i am looking for, 

 

Do we have any trailhead which can help me with the above scenario.

 

Regards, 

Umang Shah 

 

#Trailhead Challenges  #Agentforce  #Trailhead  #Service Cloud

1 resposta
  1. 18 de ago., 05:14

    Hi @Umang Shah

     

     

    Here are the most relevant Trailhead links:

    1. Messaging + Agentforce Service Agent + Human Handoff 

      Build with Agentforce Builder 

      Agentforce for Service supports escalation to live agents.

    2. Service Assistant + Service Plans + Case Catch-Up + Service Replies 

      Service Assistant Dynamic Experience
    3. Service Assistant Setup 

      Onboard and Set Up Agentforce Service Assistant
    4. Unified Knowledge 

      Get Started with Unified Knowledge
    5. Complete Agentforce Service Trail 

      Discover Agentforce Service

    Closest match to your complete scenario:

     

    Messaging → Agentforce → Human Handoff → Case Catch-Up → Service Replies → Service Assistant/Service Plan → Unified Knowledge. 

0/9000

I have inlucded the activity tab on the Case object. But the email action is visible even after adding the email action on the page layout. I have attached the screenshot for reference.  

I don't face this issue on the Account object.  

Help me to fix this issue.  

On activity tab the email action is not visible

 

image.png

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

 

 

#Service Cloud

6 respostas
  1. 15 de ago., 07:42
    The key point is: Case does not use the Activities component to display the Email action. For Case records, Salesforce displays activity actions such as Email / Log a Call through the Chatter Publisher / Case Feed, even when the Activities tab is present
0/9000

Hi, i am logging in Salesforce Developer org after 6 months, to learn about manufacturing cloud.

 

As part of learning, i need to have access to Service setup under the Setup gear(icon). but i am not seeing that Service setup, only setup is existing.

 

Is this issue due to inactivity or old org? or still i can activate/get Service setup in my dev. org?

 

Thanks in advance!

2 respostas
0/9000

I would like to know a process where I can create a notification functionality over a case queue that I'm handling.    Use case: If a new case has been added to the queue i'm working in, it will give me a notification on my email ID That there is new case in the queue!    email notification should work as I'm getting emails when i assign a new case or do something on the cases within the same queue.  

1 resposta
  1. 11 de ago., 22:06

    Hi Nitin — two solid ways to do this: 

     

    1) Native, no-code — Queue email notification. 

    Setup - Queues - edit your queue - set a Queue Email and check "Send Email to Members." When a case is assigned to that queue, Salesforce emails the queue members (and/or the queue email address). 

    Caveat: this fires when the case is routed in via active assignment rules (or saved in the UI with "Assign using active assignment rules" checked). If cases land in the queue another way — a manual owner change, or an API insert without the assignment/email headers — the built-in email may not fire. That's where option 2 is more dependable. 

     

    2) Record-Triggered Flow (most reliable + flexible). 

    - Object: Case. Trigger: "A record is created or updated." Optimize for: Actions and Related Records. 

    - Condition Requirements: Owner ID Equals your Queue's Id. (A queue owns records through a Group, so the Case OwnerId becomes the queue's Id — it starts with 00G. Get it from Setup - Queues, or SOQL: SELECT Id, Name FROM Group WHERE Type = 'Queue'.) 

    - When to Run the Flow for Updated Records: choose "Only when a record is updated to meet the condition requirements" — that way it fires exactly once, the moment a case enters the queue (and also when a case is created directly in it). 

    - Action: Send Email (to your address, or add the specific people who watch the queue as recipients). 

    Because it keys off the owner being the queue, it fires no matter how the case got there, and you can add filters (priority, origin, record type) so you only get pinged for the cases you care about. 

     

    Tip: if several people monitor the queue, either list them as recipients in the Send Email action or use an Email Alert with a template for nicer formatting. 

     

    Refs: 

    - Queue "Send Email to Members" behavior:

    https://help.salesforce.com/s/articleView?id=000384841&type=1

     

    - Walkthrough of Queue Email setup:

    https://www.simplysfdc.com/2021/01/salesforce-queue-email.html

0/9000