Hi Everyone,
We are implementing Agentforce with Consumer Goods Cloud and have developed a custom Lightning Web Component (LWC) as a Custom Response Renderer to collect user inputs within the Agentforce chat.
The implementation works perfectly in Salesforce Lightning Experience (desktop). However, when we access Agentforce through the Consumer Goods Cloud Offline-First Mobile application, the custom LWC is not displayed in the chat window.
Has anyone implemented a similar solution or encountered this issue?
Specifically, we're trying to understand:
- Are Custom Response Renderer LWCs supported in the Consumer Goods Cloud Offline-First Mobile application?
- Are there any known limitations for Agentforce UI extensions on the Offline-First mobile app?
- Is there any additional configuration required to render custom LWCs in the mobile application?
- Has anyone found a workaround or alternative approach for collecting user input in Agentforce on the Offline-First app?
Any documentation, experience, or guidance would be greatly appreciated.
Thank you!
@* Consumer Goods Cloud * @* Salesforce Developers *
#Agentforce
We've looked into a similar requirement recently, and from our experience, Custom Response Renderer LWCs that work in Salesforce Lightning Experience are not always supported within the Consumer Goods Cloud Offline-First Mobile application.
The Offline-First app uses a different rendering framework and has several UI limitations compared to the standard Lightning Experience. While Agentforce itself may be accessible, certain extensibility features—especially custom UI components such as Response Renderer LWCs—may not be rendered within the mobile application environment.
A few things worth checking:
• Verify whether the LWC is supported in Salesforce Mobile and Offline contexts, not just Lightning Experience.
• Review the latest Agentforce and Consumer Goods Cloud mobile documentation for supported component types and UI extension capabilities.
• Confirm that all required component targets and mobile configurations are enabled, although this alone may not resolve the issue if the framework itself doesn't support custom renderers.
• Test the same Agentforce implementation in the standard Salesforce Mobile App to determine whether the limitation is specific to the Offline-First application.
If your goal is to collect user input on mobile, you may need to consider alternative approaches such as Flow screens, Quick Actions, or launching a dedicated mobile-supported experience from the Agentforce conversation, depending on the use case.
I'd also recommend raising a Salesforce Support case, as support for Agentforce UI extensions in the Consumer Goods Cloud Offline-First app is still evolving and the latest guidance may not yet be fully documented.
Please share an update if you find an official confirmation from Salesforce, as this would be valuable for others exploring similar implementations.
