Chat Console
The Chat Console was the Salesforce Service Cloud surface that support agents used to send and receive real-time chat messages with website visitors.
Definition
The Chat Console was the Salesforce Service Cloud surface that support agents used to send and receive real-time chat messages with website visitors. It was one of the four parts of the older Chat product (formerly Live Agent), alongside Omni-Channel, Embedded Service, and Einstein Bots. Omni-Channel routed each incoming chat to the right agent, and the agent worked the conversation inside the console next to the customer record, transcript history, and Knowledge articles. Supervisors used the same console to monitor live chats, send whisper messages, and report on chat session records.
This term is legacy, and the product behind it is now retired. Salesforce retired Legacy Chat on February 14, 2026, and the recommended replacement is Enhanced Chat, also known as Messaging for In-App and Web. New work uses the standard Service Console with the Omni-Channel widget, where chats and messaging conversations share one routing engine and one agent workspace. Treat any older documentation that says Chat Console as a pointer to that modern Service Console setup.
How the Chat Console worked and what replaced it
Where the Chat Console fit in the Chat product
Salesforce documentation described Chat as four parts working together. The Chat Console was the agent-facing piece. Omni-Channel handled routing, Embedded Service rendered the chat window on a website, and Einstein Bots could deflect or qualify a request before a human joined. An agent did not configure routing inside the console. Routing decisions came from Omni-Channel presence and capacity settings, and the console simply received whatever conversation those rules assigned. The console gave the agent a text panel to type replies, a view of the customer record when one was matched, and access to support tools like Quick Text and Knowledge. This separation mattered because it kept the conversation surface stable while admins tuned routing behind it. An admin could change skills, capacity, or queues without touching the agent layout. The console was where the customer-facing work happened, and the other three parts decided which agent saw which chat and how the chat reached the browser in the first place.
The Classic console versus the Lightning Service Console
In Salesforce Classic, Chat lived in a dedicated console layout with chat panels placed in fixed regions of the page. Agents saw the incoming chat, the active conversation, and the customer record together, but the layout was rigid and customization happened through console component settings rather than a drag-and-drop builder. Lightning Experience changed the model. Instead of a separate Chat Console, chat folded into a standard Lightning console app. Admins added the Omni-Channel utility to the utility bar and added Chat Transcripts to the navigation items, so accepting a chat opened it inside the same workspace agents already used for cases and other records. The Lightning approach was more flexible because the console page was just a Lightning app that an admin could shape per service team. The same workspace held a chat in one tab, a phone call in another, and a case in a third. That consolidation is the reason modern guidance points to the Service Console rather than a standalone chat screen.
Handling several chats at once
Chat scales differently from voice. A phone agent takes one call at a time, but a chat agent commonly runs three to five conversations together. The console supported this by giving each active chat its own tab with an indicator for new messages, so an agent could glance across tabs and answer whoever was waiting. Omni-Channel capacity settings controlled how many conversations routed to a single agent, which is the real lever for concurrency. Set capacity too high and agents fall behind, replies slow down, and customer satisfaction drops even though utilization looks impressive on a report. Set it sensibly and agents stay responsive. The console also kept each conversation in context, so switching tabs did not lose the thread or the matched record. Keyboard shortcuts helped agents move between chats quickly without reaching for the mouse. The design goal was simple. Let one person carry several conversations without confusing them, and let the routing layer, not the agent, decide how heavy that load should be.
Transcripts and the data the console left behind
Every chat handled in the console produced a record. In Legacy Chat that record was the Live Chat Transcript, which stored the full conversation, timing, the agent who handled it, and links to any case or contact involved. The console wrote this context automatically, so an agent did not have to copy and paste the conversation anywhere. After the chat ended, the transcript remained available for follow-up, quality review, or reporting. Supervisors built reports and dashboards on these session records to measure handle time, concurrent-chat utilization, after-chat work, and customer satisfaction. Because the transcript captured what actually happened, it became the basis for coaching and for spotting where agents got stuck. The newer Enhanced Chat keeps a similar idea but uses Messaging Session records instead of Live Chat Transcripts, since the conversation can now pause and resume asynchronously. Either way, the principle holds. The agent works the live conversation, and the platform persists a durable record that the rest of the support operation can analyze later.
Quick Text, Macros, Knowledge, and screen pop
The console earned its keep through the tools placed around the text panel. Quick Text gave agents canned snippets they could insert with a few keystrokes, which cut typing on common answers and kept wording on brand. Macros bundled multiple steps into one action, so a routine sequence ran with a single click. Knowledge lookup let agents pull a help article into the conversation without leaving the chat. Screen pop surfaced the matched Account, Contact, or Lead as the chat connected, using data from the pre-chat form, so the agent had context before the first reply. Together these affordances are what separated a fast chat operation from a slow one. An agent with curated Quick Text and a clean Knowledge base resolved chats quickly. An agent staring at a blank record and an uncurated snippet list did not. In the Lightning Service Console, admins place these components on the Lightning page where they help the workflow, which is more adjustable than the fixed regions of the old Classic console.
Why Legacy Chat retired and what to use now
Salesforce retired Legacy Chat on February 14, 2026, and named Enhanced Chat, also called Messaging for In-App and Web, as the replacement. The driver was capability. Legacy Chat was synchronous, so a session ended when the customer closed the window. Enhanced Chat adds asynchronous conversations that a customer can leave and pick up later, which fits how people actually message today. It still routes through Omni-Channel and still runs inside the Service Console, so the agent experience is familiar, but it unifies web chat with in-app messaging under one model. Salesforce published a Chat Transition Readiness Report to help teams gauge how much work the move required. For anyone reading older material, the translation is direct. A reference to the Chat Console means the agent worked chats inside the console, and the current equivalent is the Service Console with the Omni-Channel widget handling Enhanced Chat. Standing up a new chat channel today should target Enhanced Chat, not the retired Legacy Chat product this term originally described.
Trust & references
Cross-checked against the following references.
- Chat with Customers on Your WebsiteSalesforce
- Legacy Chat Is Being RetiredSalesforce
Straight from the source - Salesforce's reference material on Chat Console.
Hands-on resources to go deeper on Chat Console.
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 the legacy Chat Console in Salesforce?
Q2. In modern Salesforce releases, where does Chat functionality live for agents?
Q3. Which agent-productivity tools does the Chat Console surface inline during a conversation?
Discussion
Loading discussion…