#Service Cloud64 人がディスカッション中

Hi Christoffer, 

A lot of the existing Digital Engagement/Omni-Channel architecture can be reused, such as queues, routing configurations, Omni-Channel flows, and business-hours handling. However, WhatsApp has some channel-specific setup and Meta/WhatsApp requirements, so I’d validate each component rather than assuming the Messenger configuration can be copied directly.  

For the migration itself, I’d plan for someone to have access to the WhatsApp number and the required Meta Business Manager/WABA permissions during the setup, since verification and migration steps can require access to the number.  

For the cutover, I’d also treat the connection/migration and the actual channel activation as separate steps in your runbook and test the complete flow in a non-production environment first. The exact behavior can depend on the WhatsApp/Meta setup and the existing provider.  

Since you have several production-cutover questions around 2-step verification, activation timing, downtime, and rollback, I’d recommend confirming those specific points with Salesforce/Meta for your exact migration scenario before scheduling the cutover. If you can share the Salesforce WhatsApp setup/documentation you’re following, the community can also comment on the specific steps. 

Hi Jeremy,

This sounds like the existing plugin/customization that was populating the Event Log dates may no longer be firing correctly. I’d first check whether the automation/plugin is still active and whether any recent Salesforce changes affected the Event/Event Log fields or automation. 

Also check the debug logs when creating an Event to see whether the customization is being triggered and whether there are any errors. 

If you can share the name of the plugin/customization and the Event Log object/fields being populated, it would help narrow this down. If the issue persists after checking the configuration, you may want to create a case with Salesforce. 

Hi @Garrett Smith

, 

I managed to make it work by uploading the image as Channel menu button icon (Embedded Service > Channel Menu > Branding). I first uploaded the image as a static resource (with cache control: public) and then pasted the URL in the Custom button icon URL field. Supported formats are .jpg, .gif, .png, or .svg file, 32 x 32 pixels. 

Hope this helps!

Hi Vikrant, autocomplete="off" isn't supported directly by lightning-input-field because it doesn't expose the underlying <input> element's autocomplete attribute. 

If you need to control autocomplete, you can use lightning-input instead of lightning-input-field and set: 

<lightning-input
    type="text"
    autocomplete="off"
    name="myField">
</lightning-input>

If you need to keep lightning-record-edit-form and lightning-input-field, you generally can't reliably disable the browser's autocomplete through the component attribute. 

If you can share which field you're trying to disable autocomplete for and what browser you're testing in, I can suggest a more specific workaround. 

Hi Nisha, this can happen if there is an issue with the Classic Email Template folder page or if the required permissions aren't available.  

Please check that you have the “Manage Public Classic Email Templates” permission (or the appropriate email template management permissions) and that you have access to the Classic Email Templates folder functionality.  

Also try refreshing the page or accessing Setup → Classic Email Templates → Create New Folder again from a fresh Salesforce session.  

If the same error persists after verifying the permissions, I recommend creating a Salesforce Support case and providing the URL and exact error message, since the error itself suggests Salesforce Support investigate the page request 

Hi Svetlana,

The short answer is that you cannot manually construct a valid ConversationId via standard Apex/Flow DML because in Messaging for In-App and Web (MIAW) and Enhanced Channels, the Conversation record is managed by Salesforce's backend Service Cloud Real-Time (SCRT2) fabric, not core Salesforce DML. Inserting a raw MessagingSession record without an underlying SCRT conversation context leaves it orphaned and unusable in Omni-Channel.

However, depending on whether you want an automated greeting sent or a completely silent assignment, here are two tested patterns for this use case:

Solution 1: Outbound Messaging Template (Recommended)

Instead of generating an artificial "blank" session, trigger an outbound template message to initiate a real session.

• How it works:
  1. Trigger an Auto-Response / Outbound Messaging Flow from your record trigger using an approved Messaging Template (e.g., "Hi [Name], an agent is reviewing your account and will connect shortly.").
  2. Because the message is sent via the standard messaging engine, Salesforce automatically creates the Conversation, provisions the ConversationId, and initiates an active MessagingSession.
  3. Route this newly initiated session through your Omni-Channel Flow to the agent queue.

• Why it works: The agent receives an active session in their Omni-Channel widget, the conversation thread links seamlessly (for both new and existing customers), and the SCRT2 backbone recognizes the session.

Solution 2: Agent-Initiated "Start Conversation" Quick Action

If your business requirement strictly forbids sending an automated outbound text to the customer before the agent connects:

• Use the Standard Enhanced Outbound Capability:
  • Route a custom Task, Case, or Work Order to the agent via Omni-Channel when the trigger condition is met.
  • Embed the "Send SMS" / "Start Conversation" Quick Action on the record page layout.
  • When the agent accepts the work item from Omni-Channel, they click the action to send their first custom message. Salesforce immediately opens the active MessagingSession console tab for the agent.

Solution 3: SCRT2 / Connect REST API Outbound Trigger

If you have developer resources and need complete headless automation:

• Use the Connect REST API for Outbound Messaging (/connect/conversation/messages / Enhanced Channel API).

• By calling the internal service endpoint rather than attempting an insert new MessagingSession(), the platform spins up the actual conversation payload and routes the resulting session to Omni-Channel as designed.