Skip to main content
Featured group

* Digital Engagement *

Welcome! This group is dedicated to your success with Salesforce Digital Engagement. 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

messaging end user related list not available on lead and contact despite the object having a relationship with those objects? Why? Thanks

2 answers
  1. Aug 26, 9:12 AM

    Thanks Kundan, I tried that as well but not available at all. i think it is a salesforce limitation. I ended up creating a small lwc on both lead and contact

0/9000

First off, thank you to this amazing platform for enabling us to ask questions and share ideas — it's incredibly valuable! 

 

We’re currently implementing a brand new WhatsApp integration via Digital Engagement, and I was hoping to gather some best practices from those who’ve done this before.

Specifically, I have a few questions: 

 

  1. Meta Business Account setup  

    Is it best to register a

    Meta Business Account under the client’s business entity rather than using a personal Meta account? - I think this is a "No brainer - Yes"  

      

     

  2. Phone number strategy  

    Is it a good practice to:

    • Use one phone number for the Production setup, and
    • Get a separate number linked to the same Meta Business Account for the Dev/Sandbox environment to support development and testing? I believe we should not test using the Number that is in use for day-to-day business purpose.
  3. General setup advice  

    What are some “must-do” items or best practices when setting up WhatsApp for Salesforce? 

 

Any recommendations, advice and suggestions would be of great help.

5 answers
  1. Aug 25, 9:33 AM

    is the video out? I just came to know about this group thanks

0/9000

I am using flow to send SMS to a customer. This works fine, but for new Messaging End Users, it can take up to 10 minutes before the SMS is sent and the Messaging Session is created.

I need to link the messaging session to the case where the users started the flow from, but the session isn't available right away.

 

I tried to use a record triggered flow on Messaging Session, but the flow isn't triggered. Any ideas to why the new Messaging Session doesn't trigger the flow?

11 answers
  1. Aug 19, 10:12 AM

    Hi Team,

    I faced the same issue and found a solution that worked for me.

    My requirement was to link a newly created Messaging Session to the Case from which the session was initiated using a Screen Flow.

    Solution:

    Enable Change Data Capture (CDC) for the Messaging Session object in Setup. This publishes a change event whenever an action occurs on a Messaging Session record, such as create, update, or delete. The event message provides the Messaging Session record ID and its field values, including the Messaging User ID.

    First, store the Case ID on the Messaging User record within the Screen Flow (or from wherever you are initiating the Messaging Session).

    Since a Messaging Session change event is published whenever an event occurs on the record, subscribe to it using either a Platform Event-Triggered Flow or an Apex Trigger on the Messaging Session Change Event. Then perform the required logic:

    1. Retrieve the Messaging User ID from the Messaging Session event.
    2. Use the Messaging User record to get the Case ID that was stored earlier.
    3. Update the Messaging Session record using the Messaging Session ID received in the event and the Case ID which we get by query the messaging user.

    This will successfully link the Messaging Session to the Case.

    If you need code samples or additional guidance for implementing this solution, please reply to this comment. 

     

    Thanks.

0/9000
3 answers
  1. Aug 17, 6:09 PM

    I agree that branded short links are a better choice for customer-facing SMS. They look more trustworthy and can help avoid confusion around unknown shortened URLs. The time-zone point is also easy to overlook when setting up Business Hours.

0/9000

@* Digital Engagement *

 

We have a use case where we need to enable an agent to send a six-digit One Time Password (OTP) to a member’s phone directly from Salesforce. The agent should then validate the OTP shared by the member over the call and store the OTP verification result in Salesforce.

We are exploring whether Salesforce Digital Engagement SMS can be used for sending OTP messages as part of this flow.

Has anyone implemented a similar solution using Digital Engagement SMS?

Specifically looking for guidance on:

  •  Whether Digital Engagement SMS is suitable for OTP use cases 
  •  Best practices for generating and sending OTP securely from Salesforce 
  •  Any limitations or considerations (compliance, throttling, delivery reliability, etc.) 

Would really appreciate any insights or lessons learned from your implementations.

4 answers
  1. Jul 30, 9:49 AM

    Hey @ganesh pelluri

    try SMS Magic this is something that can be achieved with just the out of the box capabilities.. so need for any external gateway or API integration..  

    Happy to connect with you if you need further help. 

0/9000

According to the documantation, the best practice of sending outbound messages is by creating a flows. is there a way to send bulk messages to a selected list of users (bulk)?

we do have thier consent of communicating with them via whatsapp so we can create them as opted in messaging users

6 answers
  1. Sep 1, 2022, 8:06 AM

    @Larry Hall @Kermit Del Rosario was surprised there is no out of the box functionality for bulk message sending. What I did > created a list view button on messaging user object, which launches screenflow, and allows the user to select a template, then sends outbound message.  hope that helps  

0/9000

Hola. 

Al crear el componente en SF y vincularlo con la plantilla de whatsapp aprobada por META, en la sesion de mensajeria creada aparece este error: 

 

Este componente de mensajería y su plantilla de mensajes asociada contiene números de parámetros diferentes. Solicite a su administrador de Salesforce que compruebe los parámetros del componente. 

 

Le ha pasado a alguien y me puede decir cual es el problema? 

Gracias

0/9000

We're trying to send out unique links to each contact as a text message from flow action - something like

"Hi John Doe, Please fill out Survey by clicking the below link

{Contact Specific Unique Link}"

I don't see an option to send the combination of text message & a contact specific unique link embedded in the text message. Did anyone try to achieve this? Please let me know as this is blocking our text message initiative to be able to send text + Unique links. Thanks!

9 answers
0/9000

Hi all and all the best to wherever you are,  

 

i run out of ideas regarding passing hidden pre chat values from embeeded service deployment (enhanced chat) to a messaging session record. I setup everything in messaging settings, the custom parameter, mapped it in parameter mappings, i use the exact same flow variable, which is of same data type and available for input. In the flow i have an update element which should write the pre chat value to the messaging session before routing the session to the bot in the Inbound Flow. 

 

In embeeded service deployments pre chat is active and the hidden field is selected. I added according to documentation the method.  

 

"window.addEventListener("onEmbeddedMessagingReady", () => { 

    embeddedservice_bootstrap.prechatAPI.setHiddenPrechatFields({ 

        "preChatWebsite": "Austria" 

    });"  

But the value is not passed. However the flow itself fires. So i can write hardcode "test" into the field on messaging session object via flow everytime i start a conversation. It as well does not get overwritten from another flow. I test this in dev console with a VF page.  

 

Is there something i am missing? Do i have to create a case first maybe? 

 

Would be happy for help here. Thanks a lot in advance.  

Best 

3 answers
  1. Jun 5, 11:38 AM

    Hi @Sven Riemer

    I am also at same situation and I tried reverting Embedded Service Deployment to v1 but still no luck. Did you manage to get this working with v1, if so was there any additional change needed? 

     

    Thank you.. 

    Manoj

0/9000

 Hi, I’ve been trying to use the ConversationEntry object in a Flow (Get Records). I couldn’t get it to work as expected.    

To investigate, I used Salesforce Inspector Reloaded to query the ConversationEntry object. I noticed that the CreatedDate of the most recent record is October 22, 2025, which seems unusual.   

It looks like ConversationEntry records stopped being created after that date. Everything was working fine up until then, and I haven’t made any changes to channels or configurations (at least none that I’m aware of). 

Could you help me understand what might be causing this issue? 

4 answers
  1. May 23, 7:42 AM

    The specific date (October 22, 2025) strongly suggests that this issue might be related to a Salesforce Release (like Winter '26) or a platform-wide update that rolled out around that time. 

     

    Here are a few things to consider and investigate: 

     

    1.Data Retention Policy / Messaging Data Archiving: Salesforce has strict data retention limits for messaging objects. It's possible that older ⁠ConversationEntry⁠ records are being archived or that new conversations are now being routed differently. 

     

    2.API Versioning in Flow: Check the API version of the Flow you are using. If the flow is running on a newer API version, ensure that ⁠ConversationEntry⁠ hasn't been restricted from direct "Get Records" queries without specific filter contexts (like ⁠ConversationId⁠). 

     

    3.Release Notes Check: Search the Salesforce Release Notes around October 2025 for any changes related to "Messaging for In-App and Web" or ⁠ConversationEntry⁠ behavior. Salesforce occasionally changes how system entries or transcript fragments are stored to optimize performance. 

     

    If your production channel is actively running but no new rows are appearing in Inspector, opening a Salesforce Support case to check if there is a backend synchronization issue for this specific object might be the quickest way.

0/9000