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.