
Getting customers to the right help.
Connecting customer context, agent expertise, and the support workspace in Salesforce Lightning.
PRODUCT MISSION
Help customers reach useful support, and help agents handle the conversation in one workspace.
Problem & goal
Support teams were moving from Salesforce Classic to Lightning, but their familiar chat workflow still pulled them back into the older console. Chat-button and queue configuration also shaped where incoming conversations landed.
The goal: improve routing and case handling in Lightning while making the change manageable for agents already comfortable with the existing workflow.
Solution
Use pre-chat information to personalize Einstein Bot greetings, route conversations by configured skills through Omni-Channel, and let agents handle them in the Lightning Service Console.
User journey
My role
I personalized the bot greetings, configured service resources and skills, and worked on the move from Live Agent to Omni-Channel. I also used Omni Supervisor to give the team visibility into active chats and a way to support agents during a conversation.
Decisions
Design for both sides of the conversation.
The customer needed a relevant starting point; the agent needed work they could help with. Pre-chat personalization and skills-based routing addressed those connected needs.
Make Lightning a workable daily home.
Moving the interface was only useful if agents could handle the chat there. Bringing the conversation into the Service Console reduced the need to return to Classic for the familiar workflow.
Give superusers a smaller change to try.
I favored testing a smaller change with superusers before moving every chat button. A staged transition gave experienced users a clearer way to try the workflow and provide feedback.
Impact
Agents could handle the workflow in Lightning, with more deliberate routing and a more personal start to the customer conversation.
Reported outcome for the combined workflow changes. The contribution of bot personalization alone was not isolated.
How I would measure the support experience
Track time to the first qualified agent, transfers between agents, and end-to-end resolution time. Compare similar issue types and team coverage, and use customer satisfaction and agent workload as guardrails.
Proposed follow-up measures. The historical measurement window is not specified here.
What I took away
The customer’s context and the agent’s workspace need to work together. Adoption also depends on giving experienced users a clear path into the new workflow.