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

Hello @Megan Johnson

Salesforce does not provide an out-of-the-box "Clone" button or direct feature for Agentforce Agents.  

There is an open idea you can vote: 

https://ideas.salesforce.com/s/idea/a0BHp000016Km6wMAC/provide-ability-to-clone-and-agentforce-agent

Hi , 

I managed to complete this by some weird magic:

• Deactivated the agent, then enabled it again to ensure there is a approval on slack for the PAM agent
• Enabled einstein bots, and created a new enhanaced bot (just randomly put values)

 https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000pOLjw

Hi Megan, good news, your channel is fine: Custom Lightning Types are supported on Enhanced Chat v2 (the web deployment of Messaging for In-App and Web), alongside Lightning Experience and Experience Builder. They are NOT supported on In-App Chat (the mobile SDK), WhatsApp, SMS, Apple Messages, LINE, or BYOC, but plain Enhanced Web Chat is supported. 

Your symptom, text arrives but the component never renders on the live widget, almost always means the renderer is not registered for the enhancedWebChat channel specifically. CLT rendering is channel-scoped: each channel that should render the type needs its own renderer.json in that channel's folder. If your type only has a renderer for the default context (or you were seeing it only in the Builder conversation preview), it renders in preview but stays blank on the live Enhanced Chat v2 widget, which is exactly what you describe. 

So: 

1. Add and deploy a renderer.json for your Custom Lightning Type under the enhancedWebChat channel folder, not just the default one, pointing at your LWC. 

2. Redeploy and reload the embedded deployment so the new channel config is picked up. 

3. For the tapped option arriving back as the user's reply, have the LWC dispatch the selected value as the utterance, that part is on the component, not the channel. 

The Agentforce dev guide 'Enhance the Agent UI with Custom LWCs and Lightning Types' documents the per-channel renderer setup. 

if this helps, please mark it as the Best Answer so it helps the next person, thanks 🙂

Hey Megan, 

Adding one thing to Himanshu's answer since it's mostly right but slightly understates option 2: Salesforce actually has a fully supported LWC-based header customization for Messaging (lightningSnapin__MessagingHeader target), you extend the base chat header component and can add whatever fixed text/markup you want inside it. This is documented and stays visible for the whole conversation, unlike the greeting-message approach, which scrolls away. 

So realistically you have two solid, supported paths: 

1. Custom LWC header (extends BaseChatHeader/MessagingHeader), gives you a persistent banner area inside the actual chat window that Salesforce won't overwrite on releases, since it's a supported customization point, not DOM hacking 

2. A banner on your host page around the widget (Himanshu's option 1), simplest if the disclaimer doesn't need to be inside the chat window itself 

Both are supported. The custom header route is probably closer to what you're picturing since it sits inside the widget alongside "Powered by Agentforce," not just around it. 

Reference: