Service Console Configuration and User Experience
The agent's cockpit
The Lightning Service Console is an app type, not a page. Its building blocks: a highlights panel for key fields at a glance, split view (list plus record), console tabs that stay open for parallel work, the utility bar for always-available tools (Omni-Channel, history, notes, keyboard shortcuts), the docked composer for email and messaging, and console components such as Knowledge search, CTI, and Omni-Channel.
Know the productivity trio: quick text (reusable snippets with merge fields), macros (one-click sequences of updates, emails, and quick texts), and email templates (structured, merge-field-driven messages). Macros automate actions; quick text inserts words; templates format email.
Also relevant: Omni-Channel component settings for capacity and presence, Lightning page customization in App Builder, record types and page layouts for role-based views, and console navigation choices that cut clicks for high-volume agents.
Traps: expecting utility bar items to appear in a footer; assuming macros run for users who lack the permission; assuming the docked composer works for every channel; designing a single layout for every agent role.
Rule of thumb: measure clicks. Every field an agent does not need on the highlights panel costs handling time multiplied by thousands of contacts.
Worked example: Agents paste the same three paragraphs sixty times a day. A quick text with merge fields plus a macro that updates status and sends it cuts AHT and variance - with no code and no deployment.