Agent Console
The Agent Console is the multi-pane Salesforce Classic UI designed for service representatives to work cases efficiently.
Definition
The Agent Console is the multi-pane Salesforce Classic UI designed for service representatives to work cases efficiently. It splits the screen into a list view (top left), a detail view (top right), and a related-records mini-view (bottom) so an Agent can scan a queue, open a case, and review the parent Account or Contact without leaving the page. The Console preceded Lightning Experience and was the original answer to how do we make Service Cloud reps faster than the standard one-record-at-a-time UI. It also introduced tabbed navigation for case work, where each open case becomes a primary tab and related records open as sub-tabs.
Most Salesforce orgs moved off the Classic Agent Console to the Lightning Service Console between 2018 and 2022. The Lightning Service Console retains the multi-tab idea but uses Lightning Components, supports Utility Bars, integrates Omni-Channel natively, and offers richer customisation through App Builder. New orgs no longer receive the Classic Agent Console; it remained available as a backwards-compatibility surface for orgs that had not migrated. Documentation now treats Agent Console as a legacy term and points to the Lightning Service Console for current implementations.
How the Agent Console worked and how it gave way to the Service Console
The three-pane layout in Classic
The Classic Agent Console split the browser window into three resizable panes. The list view (top left) held the current queue or list view of work to do. The detail pane (top right) showed the selected case in full. The mini-view at the bottom showed related Account, Contact, and Case History records inline. Agents stayed on one URL through an entire shift, swapping cases in the detail pane and parents in the mini-view.
Tabbed navigation, primary versus sub-tabs
Opening a case became a primary tab inside the Console. Clicking the Account in the related records opened a sub-tab under that primary tab, so the customer's full context was a click away without losing the case. Agents could juggle five or six cases simultaneously by switching primary tabs. The pattern was the direct ancestor of the Lightning Service Console's workspace tabs and is the part of the design that survived the most intact.
The related records mini-view
Beyond tabs, the mini-view at the bottom was where Agent Console differed most from a standard record page. Admins picked which related objects appeared and which fields displayed inline, so Agents could see Contact phone and email, recent cases, and Account industry without clicking. The mini-view was configured per profile, which gave admins room to tailor the experience by role.
Why the Agent Console mattered before Lightning
Standard Salesforce Classic moved one record at a time. The Agent Console was the first sanctioned high-density layout for case work and the only way to get a real service representative workflow without writing a Visualforce app. For a decade it carried Service Cloud productivity expectations, and most enterprise deployments shipped it as the default app for service users.
The shift to the Lightning Service Console
Lightning Experience introduced the Service Console with App Builder, Utility Bars, and Lightning Components. The new console kept the tabbed model and added native Omni-Channel, Macros, Knowledge One, and Einstein for Service. The migration story was usually a profile flip plus a Lightning record page redesign, since most data and configuration came across. Some advanced Classic Console JavaScript customisations had to be rewritten as Lightning Components.
Compatibility and migration
Salesforce kept the Classic Agent Console available longer than most Classic surfaces because Service Cloud customers were among the slowest to migrate. The compatibility window included Lightning App Builder support for hybrid orgs and a Lightning Console Migration Tool that translated Classic Console layouts into Lightning record pages. Most orgs finished migration well before 2024.
What Agent Console did not support
The Classic Agent Console never picked up several features that landed only in Lightning. Native Omni-Channel routing needed Lightning. The Macro builder UI worked in both but with reduced functionality in Classic. Einstein Reply Recommendations, Knowledge One, and Service Cloud Voice were Lightning-only from the start. Orgs that stayed on Classic for too long missed the entire next decade of service investment.
Where the term lives in current documentation
Current Salesforce Help articles redirect Agent Console references to the Lightning Service Console. The Setup search no longer offers Agent Console as an option in new orgs. The phrase still appears in old certification material and partner blogs from the 2015 to 2022 era. Treat any current documentation that uses Agent Console as either legacy reference or as shorthand for the Lightning Service Console.
How to migrate from Agent Console to the Lightning Service Console
Migration is mostly a profile flip plus a Lightning record page redesign. The fiddly parts are translating any Classic Console JavaScript customisations to Lightning Components and validating Omni-Channel routing in the new surface.
- Inventory the current Agent Console setup
Document the Classic Console app, the page layouts used by each profile, the mini-view configurations, and any Console.js customisations. The inventory is the migration scope.
- Create a Lightning Service Console app
App Manager, New Lightning App, choose Console navigation, add the relevant items to the navigation bar. Save as a Lightning Service Console app.
- Design Lightning record pages per object
Use App Builder to recreate the high-density layout: tab sections, related lists, knowledge sidebar, custom Lightning Components. Aim for parity with the Classic mini-view, not exact replication.
- Translate Classic Console JavaScript customisations
Console.js calls have to be rewritten as Lightning Component events or workspace API calls. Common patterns (open new sub-tab, refresh primary tab, set tab label) have direct Lightning equivalents.
- Flip profiles and validate
Update profiles to default to the new Lightning Service Console app. Pilot with a small group, validate Omni-Channel routing, Macros, and Knowledge access, then roll out to the rest of service.
- Console.js does not run in the Lightning Service Console. Any Classic Console customisations need to be rewritten against the Workspace API.
- Omni-Channel works only in the Lightning Service Console. Staying on Classic forfeits native routing.
- Mini-view configurations do not migrate automatically. Admins recreate them as compact layouts or sidebar components in App Builder.
- Profile defaults control the landing app. Users will keep seeing Classic if their profile default is not updated.
Trust & references
Cross-checked against the following references.
- Service ConsoleSalesforce Help
- Salesforce Classic ConsoleSalesforce Help
Straight from the source - Salesforce's reference material on Agent Console.
- Workspace API ReferenceSalesforce Developer Docs
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 is Agent Console?
Q2. What layout does Agent Console use?
Q3. What is the modern Salesforce replacement for Agent Console?
Discussion
Loading discussion…