Service Console
The Service Console is the Lightning console app Salesforce ships for support agents, built around a tabbed workspace that holds several cases open at once without losing their state.
Definition
The Service Console is the Lightning console app Salesforce ships for support agents, built around a tabbed workspace that holds several cases open at once without losing their state. Each record opens as a workspace tab, with related records nested underneath it as subtabs. A utility bar pinned to the bottom holds tools that survive every tab switch.
More than one app carries that label in the App Launcher, and which ones you see depends on when the org was created.
Access is gated by one permission, Lightning Console User, which Sales Cloud and Service Cloud licenses turn on by default.
In plain English
“Picture sticky notes on a desk, one per customer you are helping. You can set one down mid-sentence, pick up another, and come back to find your half-written note exactly where you left it. The Service Console is that desk.”
Worked example
Priya is a tier-one agent at an appliance retailer. Omni-Channel routes her Case 00041892, Subject "Dishwasher leaking after install", Priority High, Origin Phone, and it opens as a workspace tab. Inside it she opens the Contact and a Knowledge article on drain hose checks as subtabs, then starts a Reply Email. A chat request lands as a second workspace tab. Twelve minutes later she clicks back to Case 00041892. Both subtabs are still there. The draft email still holds her half-typed paragraph, and the record is scrolled where she left it. She runs her Escalate to Field Service macro and sets Status to Escalated.
How the console keeps five cases open without dropping one
Workspace tabs, subtabs, and the state they hold
Open a record in a console app and it becomes a workspace tab. Open something related from inside it, a contact or a Knowledge article, and that becomes a subtab nested underneath. Switch away, switch back, and scroll position, expanded sections, and in-progress edits are all still there. Opening from a list view flips the app into split view, with the list pinned left. Parity with the Classic console is still incomplete: split view cannot be resized, and interaction logs and pop-out workspaces never made the move to Lightning.
Three apps, one name, and only the icon tells you which
Foundations Service Console, Lightning Service Console, and the Service Setup Assistant Console all carry the same label. Salesforce Help publishes an icon table because the icon is the only thing separating them on screen. The Setup Assistant flavour has a hard boundary: orgs created before Spring '26 only. What varies is the default component set, not the framework, so an admin following a colleague's screenshot can lose an afternoon hunting a component that was never on their layout.
The utility bar and what deserves a slot in it
The utility bar is the fixed footer. Each item opens a docked panel and keeps running while the agent moves between tabs, which makes it the right home for anything with continuous state: an Open CTI softphone, Omni-Channel, Macros, Quick Text, Notes, History. Anything that wants a full page belongs in the navigation bar instead. This is also the one strip every agent sees on every screen, so treat a slot in it as expensive.
Who can actually open a console app
Everything hangs on the Lightning Console User permission. Sales Cloud and Service Cloud user licenses enable it by default, and no admin can switch it back off. Salesforce Platform licenses do not include it. The remedy is a Lightning Console permission set license, which Salesforce marks as available for an extra cost with some restrictions, so it is a budget line rather than a checkbox. It cannot go to Customer Community, Customer Community Plus, or Partner Community users at all. Someone holding the profile but not the permission gets a tile that opens without a workspace, which looks like a broken app.
Loaded Console Tab Limit, the setting nobody turns on until it hurts
Agents leave tabs open. Thirty loaded tabs is thirty Lightning pages sitting in browser memory, and that is the real source of most complaints that the console feels slow. The limit caps how many stay loaded, not how many stay open: tabs past it unload least recently used first and rebuild when clicked. Four kinds of tab are exempt. The one in front, anything opened in the last thirty seconds, anything holding unsaved changes, and anything built on a pinned region template.
Driving the console from code
A Lightning web component controls the workspace by importing from lightning/platformWorkspaceApi, which needs API version 59.0 or later. The methods read as you would expect: openTab, openSubtab, focusTab, refreshTab, closeTab, getTabInfo, setTabLabel, setTabIcon. Wire adapters IsConsoleNavigation and EnclosingTabId tell a component whether it is running inside a console at all, which matters because the same component usually ships to standard apps too. The Aura lightning:workspaceAPI component still runs, but the developer reference now files it under Legacy Components.
Set up and tune the Service Console
The app ships with the org, so setup means editing what is already there in App Manager rather than building a console from scratch.
- Open the right app in App Manager
From Setup, enter App Manager in the Quick Find box and select it. Find the Service Console row, open its dropdown, and click Edit. If two rows share the name, check the icon first.
- Trim the navigation items
In App Settings, open Navigation Items and keep what agents touch daily: Cases, Contacts, Accounts, Knowledge. Remove the rest, because every surplus item pushes a useful tab into the overflow menu.
- Stock the utility bar
Open Utility Items and add Omni-Channel, Macros, Quick Text, History, and an Open CTI softphone if you have telephony. Each item gets its own panel width and height in pixels.
- Assign the profiles that need it
Under User Profiles, add each profile that should see the app in the App Launcher. Assignment alone does not grant the Lightning Console User permission.
Per app, not per user. Decides whether a related record opens as its own workspace tab or as a subtab under the one you are already in.
A utility loaded with no icon in the bar. Right for event listeners, wrong for anything an agent has to click.
One positive integer for the whole org, on its own Setup page. Enter the name in Quick Find, and save 0 to switch the feature off.
- A Classic console app cannot be upgraded to Lightning. You rebuild it or customize a shipped one.
- Agentforce Service Assistant is not a utility bar item. Salesforce ships it as a panel for Case and Messaging Session record pages, so hunting under Utility Items comes up empty.
- Visualforce overrides only partly survive the move to Lightning console apps: the delete action is not supported.
Prefer this walkthrough as its own page? How to Service Console in Salesforce, step by step
How organizations use Service Console
Agents hold four to six cases open across chat and email. Omni-Channel pushes work in as workspace tabs, and Macros in the utility bar absorb the repetitive status steps.
Phone dominates, so the Open CTI softphone sits in the utility bar and stays connected through every tab switch. Knowledge opens as a subtab, so repair steps and the case share a screen.
Only the contact centre holds Service Cloud licenses. Lightning Console permission set licenses open the same workspace for the back office, at their own cost rather than free.
Trust & references
Cross-checked against the following references.
- Lightning Service Console (opens in new tab)Salesforce
- Service Console Versions (opens in new tab)Salesforce
- Identifying Your Service Console Version (opens in new tab)Salesforce
- Who Can Access Lightning Console Apps? (opens in new tab)Salesforce
- Limit the Maximum Number of Loaded Lightning Console Tabs (opens in new tab)Salesforce
- What Features Are Available in Lightning Console Apps? (opens in new tab)Salesforce
- Agentforce Service Assistant (opens in new tab)Salesforce
Straight from the source - Salesforce's reference material on Service Console.
Hands-on resources to go deeper on Service Console.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He writes and edits salesforcedictionary.com, published by KineticBit Inc., to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
+5 pts / dayQ1. An agent on a Salesforce Platform user license has the Service Console app assigned, but opening it produces a page with no workspace tabs. What is the most likely cause?
Q2. You set Loaded Console Tab Limit to 5 and an agent opens nine workspace tabs. What happens?
Q3. Your App Launcher lists more than one app named Service Console. What distinguishes them?
Discussion
Loading discussion…