Service Console
The Service Console is the Salesforce Lightning app purpose-built for customer support agents who need to work multiple cases simultaneously without losing context.
Definition
The Service Console is the Salesforce Lightning app purpose-built for customer support agents who need to work multiple cases simultaneously without losing context. It uses a tabbed workspace layout where each case opens as a primary tab with sub-tabs for related records (the contact, the account, the related knowledge article). Agents can switch between four or five cases at a time, keeping each one's state intact, including unsaved typing, scroll position, and the open record relationships. The console is the daily-driver UI for any Service Cloud-licensed agent.
Service Console is a Lightning App, configured in the Lightning App Builder, with components like Highlights Panel, Compact Case Feed, Knowledge sidebar, and Utility Bar widgets (softphone, chat, notes). It coexists with Sales Console (a sibling app with the same tabbed framework, tuned for opportunity workflows) and with standard Lightning apps (single-record-at-a-time, no tabs). The console UX is what justifies the Service Cloud per-user license premium. Without it, agents either juggle browser tabs or lose context on every record switch.
How the Service Console actually changes agent workflow
The tabbed workspace and what it does for agents
The console workspace is a tabbed browser inside Salesforce. Each top-level tab is a primary record (a case, an account, a contact). Inside the tab, sub-tabs let the agent open related records without leaving the primary context. An agent can be working Case A in tab 1 (with the customer's contact open as a sub-tab and a draft email being composed), Case B in tab 2 (with a Knowledge article open as a sub-tab), and so on. Switching between tabs preserves scroll position, expanded sections, and any in-progress edits. The tabbed model is what makes high-volume case work feasible. Without it, an agent juggling five concurrent cases loses state every time they navigate.
Service Console vs Sales Console vs standard Lightning apps
Three Lightning App templates exist. Standard Lightning apps are single-page, no tabs, suitable for record-at-a-time work like a sales rep on their pipeline. Console apps (Service or Sales) have the tabbed workspace and a Utility Bar at the bottom. Service Console is tuned for case-driven work, with case-specific components in the default layout. Sales Console is tuned for opportunity-driven work. Both consoles share the framework. The choice of console type is mostly about the default page layouts: Service Console seeds with Case, Sales Console seeds with Opportunity. Admins can fully customize either to look like the other.
Utility Bar: persistent widgets across all tabs
The Utility Bar is the dock at the bottom of the console window. It holds utilities that stay open across tab switches: Open CTI softphone, Salesforce Notes, History (recent tabs), Macros, Quick Text, custom Lightning components. Each utility is a small icon. Clicking opens a panel above the bar without disturbing the active workspace tab. The Utility Bar is the right home for any tool the agent needs constantly: phone controls, note-taking, search-and-paste templates. It is the wrong home for full-page workflows.
Lightning Console JavaScript API
Custom Lightning Web Components and Aura components running inside the console can interact with the tabbed workspace through the Lightning Console JavaScript API. Methods include openTab, openSubtab, refreshTab, closeTab, getTabInfo, setTabLabel, setTabIcon, and isInConsoleNavigation. A custom component can open a new tab when an action runs, refresh a tab after a save, or set the tab icon based on case priority. The API is what makes custom console workflows possible: the framework gives you the workspace, the API gives you programmatic control over it.
Compact Case Feed and the email/log a call/post pattern
The Compact Case Feed is the chronological activity stream on a case record. It surfaces emails (sent and received), call logs, status changes, internal posts, and attached files in one timeline. The top of the feed has publishers for the agent's most common actions: Reply Email, Log a Call, Internal Note, Attach File. Each publisher uses Quick Actions under the hood and can be customized through the page layout. The Compact Case Feed replaces the older Classic Case Feed and is the modern pattern for agent productivity on a case.
Macros, Quick Text, and template-driven productivity
Console-driven agents repeat the same actions on hundreds of cases. Macros automate sequences of clicks (set Status to In Progress, attach Knowledge article 42, send Reply Email with template X). Quick Text inserts canned response snippets into emails and chat messages with a keyboard shortcut. Both are accessed from the Utility Bar in the console. The combination is what makes a high-volume agent fast. A team without macros and quick text spends three to four times as long per case as a team with them tuned.
Omni-Channel integration: routed work without leaving the console
The Omni-Channel widget runs in the Utility Bar and shows the agent's currently routed work: new chats, voice calls, cases assigned by skill-based routing. When work arrives, a notification appears, the agent accepts, and the case or chat opens as a new console tab automatically. Reject, transfer, and complete actions all happen through the widget. Together, Omni-Channel routing and the Service Console workspace are the agent productivity stack. Routing brings work to the agent; the console holds it without losing context.
Setting up the Service Console for an agent team
Setting up the Service Console is a Lightning App Builder exercise. Pick the console template, configure the page layouts, add Utility Bar widgets, assign the app to profiles or permission sets. The defaults are sensible; most orgs tune the Utility Bar and the case page layout to fit their team.
- Confirm Service Cloud licensing
Service Console requires Service Cloud user licenses. Setup, Company Information, confirm the org has Service Cloud licenses available. Agents need the Service Cloud user feature license on their user record.
- Create a new Lightning App
Setup, App Manager, New Lightning App. Pick App Type = Console Navigation. Name the app (Support Console, Service Console). Pick the navigation items: Cases, Contacts, Accounts, Knowledge.
- Add Utility Bar items
In the app wizard, click Utility Bar. Add Open CTI Softphone if the team uses softphone, Notes, History, Omni-Channel, Macros, Quick Text. Each utility is a small icon at the bottom of the console.
- Customize the Case Lightning Record Page
Setup, Object Manager, Case, Lightning Record Pages. Edit the default page or clone for the console. Drop in Highlights Panel, Compact Case Feed, Knowledge sidebar, Related Lists. Activate as default for the Service Console app.
- Set up Macros and Quick Text
Setup, Macros, New. Build the macros agents use most (Reset Password Macro, Refund Request Macro). Setup, Quick Text Settings, enable Quick Text. Build initial template library.
- Assign to profiles or permission sets
Back in the app, App Settings, assign user profiles or grant via permission set. Only users with access can switch to the console from the App Launcher.
- Train the agents
The console is unfamiliar to agents coming from Lightning Experience or Classic. Schedule a one-hour training: tab navigation, sub-tabs, Utility Bar, Macros, Knowledge sidebar. Agents who skip training will use the console as if it were a standard app and miss the productivity gains.
The Lightning App template that enables the tabbed workspace. Cannot be changed after app creation; clone the app to switch.
The bottom dock for persistent widgets. Open CTI, Notes, History, Omni-Channel, Macros, Quick Text are the common choices.
The chronological activity stream on a case. Includes publishers for Email, Log a Call, Internal Note, and Quick Actions.
JavaScript API for opening, refreshing, and managing console tabs from custom Lightning components.
The page assigned as the default view for an object in the console. Can differ from the same object's default in a standard Lightning app.
- Service Console requires Service Cloud user licenses. Salesforce Platform licenses cannot use the console even if the admin assigns the app.
- The tabbed workspace can be confusing for agents used to single-page navigation. Plan training time. Skipping training means agents work in the console without using its productivity features.
- Custom Lightning components must explicitly support console navigation. A component built for a standard Lightning app may not behave correctly in console tabs. Use the Lightning Console JS API for tab-aware logic.
- The Utility Bar holds persistent components. A buggy utility (memory leak, slow load) drags down every console tab. Audit utility performance before adding to production console apps.
- Switching from Classic Console (the legacy Aura-based console) to Service Console requires re-creating the app in Lightning App Builder. Legacy console configurations do not auto-migrate.
Trust & references
Straight from the source - Salesforce's reference material on Service Console.
- Lightning Service ConsoleSalesforce Help
- Utility Bar in the Lightning ConsoleSalesforce 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 is the primary advantage of the Service Console over standard Salesforce navigation?
Q2. Which feature of the Service Console provides agents with quick-access tools at the bottom of the screen?
Q3. How does the Service Console typically receive new customer interactions?
Discussion
Loading discussion…