Service Console practice questions

Flow utility component

Why it fails: Flows can guide processes but do not natively provide persistent telephony timing without custom development.

Recent Items utility component

Why it fails: Recent items only shows recently visited records, not call timers.

Feed Item utility component

Why it fails: Feed items relate to Chatter or case feeds, not call timing.

An inbound email service configuration

Why it fails: Inbound email services handle external emails coming into Salesforce, not internal macro execution.

A custom Apex trigger invoked via macro

Why it fails: Macros cannot directly invoke custom Apex triggers as instruction steps.

A workflow rule field update

Why it fails: Workflow rules fire automatically on record save, not as manual macro instruction steps.

Write an Apex trigger to intercept single-object macros and execute secondary DML.

Why it fails: Apex triggers do not intercept macro execution directly.

Create a separate macro for each object and chain them using custom URL parameters.

Why it fails: Macros cannot be chained via URL parameters.

Use Process Builder to listen for macro execution and update related records.

Why it fails: Process Builder cannot detect macro execution events specifically.

User Interface settings

Why it fails: User Interface settings control global elements such as density, navigation, and supported languages, not console-specific branding. Branding colours and header logos for the Lightning Service Console are set in the app's own branding configuration, so this location cannot satisfy the requirement.

Lightning Experience Branding page

Why it fails: Lightning Experience Branding applies global theme colors, but console-specific headers are managed in App Manager.

Company Information setup page

Why it fails: Company Information manages corporate identity and licenses, not app console logos.

Override the List View button with a custom Aura component.

Why it fails: A custom Aura component overriding the List View button replaces standard navigation behaviour entirely, requiring bespoke code to open subtabs and losing declarative control. It is tempting for full flexibility, but the Console's primary tab and subtab routing is configured through the app's navigation rules, not a button override.

Modify the List View filter criteria to include subtab parameters.

Why it fails: List view filters control record data criteria, not UI navigation behavior.

Apply a custom Lightning page template with forced subtab navigation.

Why it fails: Page templates determine region layouts, not tab opening behavior.

Use custom permissions on the User Profile detail page to hide the utility icon.

Why it fails: Utility bar items cannot be hidden via profile custom permissions.

Modify the global header XML configuration file.

Why it fails: Salesforce does not use global header XML files for app configuration.

Apply component-level visibility rules directly inside the utility bar configuration.

Why it fails: Standard utility bar items in App Manager do not support granular user profile visibility filters directly in the footer setup.

Convert the utility bar into a top-level navigation menu.

Why it fails: The utility bar renders as a fixed footer strip of tools within the console app; it cannot be repurposed as top-level navigation. It is tempting because both provide app-wide access points, but top-level navigation is configured through the app's navigation items, not the utility bar.

Remove the utility bar entirely from specific record detail pages.

Why it fails: Utility bar visibility is set per Lightning app or console app, not per record detail page, so it cannot be removed from selected record pages. It is tempting because page-level control sounds granular, but per-page removal would be correct for components placed on the record page itself.

Assign different utility bars to individual workspace tabs dynamically.

Why it fails: Utility bars are assigned per Lightning app, not per workspace tab, so no per-tab dynamic assignment exists. It tempts because tabs do vary by app and workspace, and admins expect granular control there; the actual mechanism is app-level utility bar configuration in App Manager.

The macro owner is inactive.

Why it fails: An inactive owner does not prevent other users with sharing access from running shared macros.

The macro was created in Lightning but executed in Salesforce Classic.

Why it fails: Macros have separate architectural implementations in Classic and Lightning.

Scheduled Macros

Why it fails: Macros cannot be scheduled to run at specific future times automatically.

Inbound Email Macros

Why it fails: Macros are agent-driven and do not execute directly on inbound email triggers.

Visualforce Macros

Why it fails: Visualforce macros do not exist in Lightning Service Console.

Administrators can create custom keyboard shortcuts with distinct keystroke combinations for custom actions.

Why it fails: Custom keyboard shortcut creation is generally restricted to predefined standard console shortcuts.

Keyboard shortcuts require agents to have a CRM Analytics license.

Why it fails: Keyboard shortcuts are a standard console feature independent of Analytics licenses.

Configure the Console to use the Utility Bar for record navigation

Why it fails: The Utility Bar is designed for tools like softphones, notes, or history, not for navigating between records. It cannot replace multi-tab or Split View for working on multiple records. Using it for navigation would be unconventional and would not meet the requirement efficiently.

Enable the Console's 'Pin' feature for tabs

Why it fails: Pinning tabs is a feature that keeps certain tabs always open, but it does not by itself allow working on multiple records simultaneously; it is more for persistent access to frequently used items like Home or a specific list view. It does not provide the side-by-side or multi-tab working capability required.

Enable the Console's 'Recent Items' component in the sidebar

Why it fails: The Recent Items component shows a list of recently viewed records for quick access, but it does not allow working on multiple records at once. It is a navigational aid, not a multitasking feature. It does not provide the simultaneous record interaction that the manager wants.

Related Cases list

Why it fails: The Related Cases list shows Cases related via a lookup or master-detail relationship, not necessarily similar ones. It does not use machine learning to find similar Cases based on content. It would only show Cases explicitly linked, which may not include relevant past solutions, so it does not meet the requirement.

Knowledge Search component

Why it fails: The Knowledge Search component allows agents to search Knowledge articles, which may contain solutions, but it does not automatically show similar Cases. It requires agents to perform searches and does not leverage Case similarity. It is a different tool for knowledge access, not for finding similar Cases.

Case Milestones component

Why it fails: The Case Milestones component displays entitlement milestones and their statuses, not similar Cases or solutions. It is focused on tracking time-based commitments, not on finding resolutions from past Cases. It does not provide the similarity analysis or solution suggestions that the manager wants.

Add Knowledge to the console's Utility Bar and configure the utility item to open articles in a new browser window.

Why it fails: The Utility Bar is designed for tools like Softphone, Notes, and History, and its items open as panels within the console, not as record subtabs. Adding Knowledge there would not create the subtab article view. Utility Bar configuration does not govern how Knowledge record links open from a Case.

Add the Knowledge component to the Case page layout and enable "Open in console subtab" on that component.

Why it fails: The Knowledge component on a record page displays and searches articles inline; it does not have an "Open in console subtab" setting. To open an article as a subtab, the behavior must come from console navigation rules, not from a property on the Knowledge component. This approach would not produce the side-by-side article view the team needs.

Enable "Split View" on the Case page and add the Knowledge component to the secondary pane.

Why it fails: Split View is a console feature that shows a list view and a record side by side, and it is configured at the app level, not by adding components to a page. It does not control how Knowledge article links open. Using Split View here would not give agents the requested subtab article behavior alongside the Case.

Enable "Split View" for the Case object and add the Contact related list to the secondary pane.

Why it fails: Split View displays a list view and a record side by side; it does not control how search results open or create subtabs for Contact records. Adding a related list to a secondary pane is not how Split View works. This configuration would not let agents open a searched Contact as a subtab under the Case.

Add the Contact object to the console's Utility Bar and enable "Search" on the utility item.

Why it fails: The Utility Bar hosts tools such as Softphone and Notes, not standard object search. Adding Contact there does not make Contact search results open as subtabs. Utility items cannot be configured to open record subtabs, so this would not meet the requirement of opening a Contact as a subtab under the Case.

Create a custom Lightning component that opens Contact records in a new browser window and add it to the Case page.

Why it fails: Opening records in a new browser window is not the same as opening a subtab within the console, and a custom component would not integrate with console navigation rules. This approach adds development overhead and does not produce the native subtab behavior. It also bypasses the console's tab management, which is not what the consultant should configure.

Add the 'Notes' tool to the Utility Bar.

Why it fails: The 'Notes' tool in the Utility Bar allows agents to take notes related to a record or a call, which can be useful for capturing information. However, it is not a frequently used tool for handling phone, email, and chat inquiries in the same way a softphone or chat component is. While it can improve efficiency in note-taking, it does not provide quick access to the communication channels themselves or reduce tab switching for those channels.

Enable the Console's 'Split View' for the Case object.

Why it fails: Split View allows agents to see a list view and a record detail side by side, which is useful for working with multiple records, but it does not provide quick access to tools like a softphone or chat. It is a navigation feature, not a tool access feature. While it can improve efficiency in some workflows, it does not address the need for persistent tools or reducing browser tab switching for phone, email, and chat interactions.

Configure the Console to display the 'Recent Items' component in the sidebar.

Why it fails: The 'Recent Items' component shows a list of recently viewed records, which can help agents quickly return to a record they were working on. However, it does not provide access to tools like softphone or chat, nor does it reduce the need to switch browser tabs for those tools. It is a navigation aid, not a productivity tool for multi-channel interactions. Therefore, it does not meet the stated requirements.

Enable the console's "Recently Viewed" list in the navigation menu so agents can reopen Cases they worked on earlier.

Why it fails: Recently Viewed helps agents return to records they have previously opened, but it does not allow multiple Cases to be open and active at the same time. It is a navigation aid, not a multi-tab workspace. The requirement is to work on several Cases simultaneously, which requires primary tabs rather than a history list.

Add the Case object to the console's Utility Bar so agents can access recent Cases from a utility panel.

Why it fails: The Utility Bar is for tools like Softphone and Notes, not for opening and managing multiple record tabs. Adding Case there would not create the multi-tab workspace the manager wants. Utility items do not provide the same tab management as primary tabs, so this would not meet the requirement for simultaneous Case work.

Configure the Case object's navigation rule to open records as subtabs under a single primary tab.

Why it fails: Opening Cases as subtabs would group them under one primary tab, which is useful for related records but not for working on multiple independent Cases. Subtabs are tied to their primary tab, so closing that primary tab closes all subtabs. This does not support the requirement to switch quickly between separate Cases as independent work items.

Use the Console's 'Open in new window' option for the Contact link.

Why it fails: Opening in a new browser window takes the agent outside the console, breaking the console navigation model and losing the integrated tab context. The requirement is to open the Contact in a new tab within the console, not a separate browser window. This would disrupt the agent's workflow and is not the intended console feature.

Enable split view on the Case record page.

Why it fails: Split view is a console navigation feature that displays a record list alongside a selected record's details, but it does not open a Contact record in a new tab. It is designed for list-detail navigation, not for opening related records in separate tabs. This would not allow agents to view the Contact in a new tab while preserving their Case context.

Add the Contact record to the utility bar as a pinned component.

Why it fails: The utility bar is designed for persistent tools like phone, notes, or history, not for displaying full record details. Pinning a Contact record to the utility bar is not a standard feature and would not provide the full record view. It also would not open the Contact in a new tab within the console, so it fails to meet the requirement.

Add a 'Related Cases' related list to the Case page layout.

Why it fails: A related list shows Cases related to the current Case, such as child Cases or Cases with a lookup relationship. However, it does not provide a way to quickly switch between them without opening new tabs, nor does it display key fields side-by-side for comparison. It is limited to showing related records, not similar ones based on criteria.

Enable the 'Split View' on the Case record page.

Why it fails: Split view displays a list view alongside a record detail, but it is primarily for list-detail navigation within a single object. It does not allow agents to see multiple similar Cases' key fields simultaneously or switch between them quickly without opening new tabs. It is more suited for navigating a list of records, not for comparing similar Cases side-by-side.

Create a custom Visualforce page that lists Cases with matching subject.

Why it fails: A custom Visualforce page could list similar Cases, but it would require development effort and would not integrate with the console's tab navigation. Agents would need to open the page separately, and switching between Cases would likely open new tabs or require manual navigation. This does not meet the requirement for quick switching within the console without new tabs.

Update the User Profile tab permissions

Why it fails: Profile tab permissions control which tabs a user can see or set as default, not whether a record opens as a primary tab or subtab. They are tempting because tabs are involved, but profile settings would be the right choice when hiding an object's tab from a group of users.

Modify the Case object page layout related lists

Why it fails: Page layout related lists control which related records display on a Case, not the tab behaviour when a Contact is opened from the console. They are tempting because the Contact is reached via a related list, but layouts would be correct when adding or reordering related lists themselves.

Set the component visibility filter on the Contact record page

Why it fails: Component visibility filters hide or show individual Lightning components based on field values; they do not govern tab navigation. They are tempting because both are record-page settings, but visibility filters would be correct when showing a component only for certain record types or criteria.

Pre-chat Forms

Why it fails: Pre-chat Forms collect information before a chat session begins, so they cannot populate console fields or send an email on an agent's click. They are tempting because they genuinely gather customer data for chat routing, but this scenario concerns agent-initiated console actions on records, not pre-session intake.

Flow Actions

Why it fails: Flow Actions launch an autolaunched flow from a console button, but they cannot themselves send an email or set field values without the flow containing those elements; the question asks for the one-click feature providing both. They are tempting because Flow Actions genuinely automate record updates from the console.

Quick Text

Why it fails: Quick Text inserts predefined message snippets into a single field; it cannot populate multiple standard field values nor send an email in one click. It is tempting because Quick Text genuinely speeds agent replies with reusable wording, but the scenario requires combined field population and email dispatch, which it does not perform.