Chat Console
The Chat Console (also called the Live Chat Console in older documentation) is the Salesforce Service Cloud surface that agents use to handle incoming chat conversations alongside other case work.
Definition
The Chat Console (also called the Live Chat Console in older documentation) is the Salesforce Service Cloud surface that agents use to handle incoming chat conversations alongside other case work. In Salesforce Classic, it was a dedicated console layout with chat panels embedded. In Lightning Experience, the Chat Console folds into the standard Service Console, with the Omni-Channel widget surfacing incoming chats and the chat panel opening as part of the active workspace tab. Agents see the active chat transcript, the customer's record details, related Knowledge articles, and any concurrent chats they are handling, all within one consolidated UI.
The Chat Console matters because agent productivity on chat scales differently than on calls. A chat agent handles three to five concurrent conversations; the console must surface each one without confusion. Salesforce's modern Service Console with the Omni-Channel widget handles this well: each active chat lives in its own tab, the agent switches between them with keyboard shortcuts, and the console state preserves context per chat. The legacy Chat Console pattern was a more rigid multi-panel layout; the modern approach is more flexible. Reading any pre-2020 Salesforce documentation that references the Chat Console should translate to the Service Console plus Omni-Channel for current implementations.
The Chat Console across Salesforce generations
The Classic Chat Console
Salesforce Classic shipped a dedicated Chat Console layout with chat panels in fixed regions of the page. Agents saw their incoming chat queue, the active conversation, and the customer record all in one view. The layout was hardcoded; admins customised through component placement but not through Lightning App Builder.
The modern Service Console plus Omni-Channel
Lightning Experience replaces the Classic Chat Console with the Service Console plus an Omni-Channel utility widget. Incoming chats appear in the Omni-Channel widget; accepting one opens it as a workspace tab. The flexibility lets admins design console layouts per service team without inheriting the Classic Chat Console's constraints.
Concurrent chat handling
Agents on chat handle multiple conversations simultaneously. The console gives each active chat its own tab with an indicator for unread messages. Keyboard shortcuts let agents switch quickly. Capacity caps in Omni-Channel control how many chats route to one agent.
Live Chat Transcript records
Each chat creates a Live Chat Transcript record (legacy) or Messaging Session record (Digital Engagement) with the conversation history. The console persists context to the record automatically; agents can return to a transcript later for follow-up or coaching review.
Quick Text, Macros, and Knowledge in chat
The console surfaces Quick Text snippets (canned responses), Macros (multi-step automation), and Knowledge article lookup inline. Agents resolve chats faster when these tools are within reach. The Service Console's Lightning page customisation lets admins place these components where they help most.
Customer context and screen pop
When the chat connects, the console pops the customer's record (Account, Contact, or Lead) if matched from pre-chat form data. The screen pop gives agents context before typing the first response. Without it, agents start cold and resolution is slower.
Reporting on agent chat productivity
Reports measure handle time per agent, simultaneous-chat utilisation, after-chat-work, and CSAT. The Chat Console's UI affordances (Quick Text, Macros, screen pop) feed into the metrics; better UI produces better metrics over time.
Common console design pitfalls
Three patterns recur. Console layouts cluttered with components agents do not use slow chat handling. Capacity set too high overwhelms agents. And Quick Text catalogues that have not been curated accumulate stale or off-brand canned responses. Each is addressable with deliberate design and regular review.
How to design the Chat Console for agent productivity
Modern Chat Console design is part of Service Console configuration. Each design decision affects agent throughput and customer experience.
- Build the Service Console Lightning page
App Builder. Configure a Service Console layout that surfaces Omni-Channel, the active workspace tab, Knowledge sidebar, and Quick Text where agents need them.
- Configure Omni-Channel capacity
Setup, Omni-Channel, Presence Configurations. Set chat capacity per agent role. Three to five concurrent chats is the practical range.
- Add Quick Text and Macros
Set up Quick Text snippets for common chat responses. Build Macros for repeated multi-step workflows (verify customer, attach Knowledge, send follow-up email).
- Configure pre-chat form to populate customer context
Pre-chat forms collect basic info that powers screen pop. Without screen pop, agents cold-start every chat.
- Iterate based on agent feedback
Run a weekly agent feedback session in the first month. Console layouts often miss the agent's actual workflow on the first pass; iteration tightens the design.
- Console layouts cluttered with unused components slow chat handling. Test layouts with actual agents before launch.
- Capacity set too high overwhelms agents; three to five concurrent chats is the practical range.
- Quick Text catalogues drift toward off-brand or stale content. Curate and prune regularly.
- The Classic Chat Console layout no longer applies. Documentation that references it is legacy.
Trust & references
Cross-checked against the following references.
- Salesforce ChatSalesforce Help
- Service ConsoleSalesforce Help
Straight from the source - Salesforce's reference material on Chat Console.
- Omni-Channel OverviewSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What was Chat Console?
Q2. Where is Chat functionality available in modern Salesforce?
Q3. What features did the legacy Chat Console provide?
Discussion
Loading discussion…