The pattern: configure org-wide defaults that match the common agent workflow, layer per-app Console Layout variations on top, audit quarterly. The cost is low; the agent-productivity gain compounds across thousands of console sessions.
- Open Console Settings in sandbox
Setup, Feature Settings, Service, Console Settings. Document current state. Sandbox lets you test changes against the agent team before production.
- Decide on Reopen Tabs on Restart
Enable for high-volume service teams that benefit from session continuity. Disable for teams that prefer fresh sessions. Test with agents before flipping.
- Configure push notifications for critical events
New case assignment, work item arrival, escalations. Avoid over-notifying; alarm fatigue undermines the value.
- Confirm Macros and Quick Text enablement matches workflow
Both ship enabled by default. Disabling cleans up agents who do not use them; leaving on is harmless if no one uses them.
- Promote keyboard shortcuts in agent onboarding
The shortcuts dramatically improve power-user speed but require learning. Include in onboarding training; agents who learn them in week one use them for years.
- Push from sandbox to production through normal pipeline
Change sets, source-tracked sandboxes, DevOps Center. Treat Console Settings as production config.
- Schedule the quarterly Console Settings audit
Bundle with Account, Activity, Calendar settings audits for a single ops review session per quarter.
Session continuity vs fresh session preference. Org-wide toggle.
Maximum primary tabs an agent can have open. Default is generous; tighten for performance-sensitive orgs.
Which events trigger desktop notifications in the console.
Productivity feature toggles. Default on; disable if unused.
Default plus custom shortcut assignments. Power-user productivity feature.
- Console Settings is org-wide. Per-app variation lives in Console Layout, not here.
- Reopen Tabs on Restart can surface stale closed cases. Test with the agent team before enabling in production.
- Push notifications can produce alarm fatigue if over-configured. Subscribe agents to only the critical events.
- Disabling Macros or Quick Text removes the feature from every console app, regardless of per-app Console Layout.
- Custom branding is limited compared to standalone web apps. Console is not a full white-label surface.