#Email-to-case2 personnes en discutent

Context

We recently experienced an Email-to-Case outage where a mailbox forwarding configuration was updated for a Sandbox request, but the forwarding rule was actually tied to the active Production Email-to-Case process. This unintentionally disrupted Production email routing and prevented incoming emails from being automatically converted into Salesforce Cases until the routing configuration was restored.

As part of our ongoing Email-to-Case enhancement and Hyperforce migration efforts, we would like to understand what contingency options are available to ensure business continuity if email routing or forwarding configurations fail in the future.

Ask

Looking for recommendations and best practices from the community on:

• What backup or failover mechanisms can be implemented for Email-to-Case?
• How can we ensure inbound emails continue to flow into Salesforce if mailbox forwarding fails or is misconfigured?
• Are there monitoring, alerting, or health-check approaches that can proactively identify Email-to-Case routing issues before business users are impacted?
• Has anyone implemented secondary routing addresses, backup mailboxes, middleware, or other resilient architectures for Email-to-Case?
• Any lessons learned or best practices for Hyperforce migrations and Email-to-Case resilience?

We would appreciate insights from teams that have implemented a robust Email-to-Case recovery or failover strategy to minimize service disruption. 

#Salesforce Admin  #Systems Administrator  #Salesforce Developer  #Salesforce_developer  #Email-to-case  #Trailhead    #Sales Cloud  #Service Cloud 

To get data from emails in Salesforce, you can use several methods and tools depending on the specific use case and requirements. 

global class EmailService extends Messaging.InboundEmailService {

    global Messaging.InboundEmailResult processIncomingEmail(Messaging.inboundEmail email, Messaging.InboundEnvelope envelope) {

        // Get the email body and subject

        String body = email.plainTextBody;

        String subject = email.subject;

        // Extract data from the email body using regular expressions or string manipulation

        // For example, let's extract the customer name and order number

        Pattern pattern = Pattern.compile('Customer Name: (.*?)\n');

        Matcher matcher = pattern.matcher(body);

        String customerName = matcher.find() ? matcher.group(1) : '';

        pattern = Pattern.compile('Order Number: (.*?)\n');

        matcher = pattern.matcher(body);

        String orderNumber = matcher.find() ? matcher.group(1) : '';

        // Create a new record in Salesforce using the extracted data

        Account acc = new Account(Name = customerName);

        insert acc;

        Order ord = new Order(AccountId = acc.Id, OrderNumber = orderNumber);

        insert ord;

        // Return a success response

        return new Messaging.InboundEmailResult(success=true);

    }

}

📧 Unlock the power of Salesforce by learning how to extract data from emails efficiently! Our latest blog explores various methods, including Email-to-Case, Einstein Activity Capture, custom Email Services, and third-party integrations. Enhance your CRM experience by automating data capture and improving data accuracy.

Check out the full guide now!

https://fetchrecordfromemail.blogspot.com/2024/07/get-data-from-emails-in-salesforce.html

#Salesforce Developer #Salesforce #CRM Configuration #Email-to-case  #EmailMessage Object

📣📡 How To Switch To Lightning Threading

Email threading in Salesforce refers to the process of automatically grouping related emails together in the context of a specific record, typically a case. This way, you can see the entire conversation history between a customer and your support team in one place.

Salesforce offers a few different methods for achieving email threading:

📌 Lightning Threading (available since Spring ’23): This is the newest approach and relies on secure tokens embedded in outgoing emails. When a customer replies to an email with a token, Salesforce can match it back to the relevant case.

📌 Email Header-Based Threading: This method looks for a specific email header field (Message-ID) in the “In-Reply-To” and “References” fields to link replies to the original email.

📌 Ref ID-Based Threading (mostly replaced by Lightning Threading): In this older method, a reference ID was included in the email subject line to associate replies with a particular case.

Lightning threading is generally considered the most secure and reliable option, as it avoids potential issues with customers modifying the subject line and removing the Ref ID.

📒 https://sudipta-deb.in/2024/06/how-to-switch-to-lightning-threading.html

@The Blog Group @* Release Readiness Trailblazers *

#Email-to-case #Summer24

Sometimes we have noticed email to case attachments are not saving as Salesforce files.  I have checked all of our settings and settings are accurate.  To be clear, here are the settings I can confirm we have set up correctly:

• If Salesforce Admin enables "Show Email Attachments in Case Attachments Related List" from Setup | Support Settings, then the email attachments are also displayed in the case 'Attachments' related list.
• If Salesforce Admin enables "Save Email-to-Case attachments as Salesforce Files" from Setup | Email-to-Case Settings, then the email attachments are stored as Files and are displayed in the 'Files' related list on the Case record

This does not happen all the time. In fact, I tested this multiple times and the attachments moved into Salesforce just fine.  Here is one example of an email-to-case that did not save attachment as a file. It does not even show up in the attachments section of the email screen in Salesforce. (Sorry I have to cut a lot of the email out but I hope you get the idea):

Is the issue because the image is embedded sent from an iPhone? I can't find any documentation on this being a problem. In fact, I found documentation saying embedded images should get attached in Salesforce (as we are expecting them to). Thanks in advance #Salesforce Admin #TrailblazerCommunity #Help #Email-to-case