You Had Me at Hello: Design Better Greetings in Agentforce Builder
The article explains how to overcome the default 800-character limit for Agentforce Builder welcome messages by creating a custom Long Text Area field with over 131,000 characters capacity. It guides Salesforce teams through exposing this field as a context variable, dynamically populating it using Omni-Channel Flows, and applying custom styling via Experience Cloud. This approach removes previous technical constraints, allowing branded, accessible, and flexible greetings that enhance the customer experience and reduce engineering dependencies. Salesforce professionals can implement this pattern to gain full control over agent greetings while supporting dynamic, styled content at runtime.
- Create a custom Long Text Area field to store dynamic welcome messages exceeding default limits.
- Expose the custom field as a Context Variable in Agentforce Builder for runtime access.
- Reference the context variable in the agent's system welcome message to enable dynamic content.
- Use Omni-Channel Flow with Text Templates and Custom Labels to generate and assign messages.
- Inject custom CSS via Experience Cloud to style agent greetings without changing core logic.
Key Takeaways Welcome messages build trust – First impressions establish customer confidence in the agent experience. Custom labels enable admin control – Configuration over code lets customers update content without engineering. Small details drive adoption – Thoughtful UX decisions like welcome messages impact customer willingness to deploy agents. This summary was created with AI and reviewed by an editor. As an engineer, I’m used to working within constraints. But sometimes, a constraint highlights an opportunity. When Williams Sonoma faced one such challenge, I took the extra step to improve the implementation. The requirement was to configure the default greeting shown when customers initiate an Agentforce chat session. This first message needed to reflect Williams Sonoma’s brand standards across regions while supporting structured formatting and dynamic content. But the field powering that first message had an 800-character limit, including HTML styling.