Agentforce Service Console and Case Feed

Why This Topic Matters

The Salesforce Advanced Administrator exam dedicates a meaningful portion of its Cloud Applications section to Service Cloud, and the Service Console together with Case Feed sits at the heart of that domain. Service agents live inside the console every day, and administrators are expected to design and configure that workspace so agents can resolve cases faster, see the right context, and collaborate without switching screens. Salesforce has rebranded and extended the traditional Service Console experience under the Agentforce umbrella, which brings AI-assisted capabilities such as Einstein-powered recommendations, Agentforce Service Agent for autonomous case deflection, and Agentforce Assistant for agents working inside the console. On the exam, however, the foundational configuration knowledge of the Lightning Service Console app and Case Feed remains the core of what is tested. Understanding how these pieces fit together helps you answer scenario questions about agent productivity, case management, and user experience design.

What Is the Agentforce Service Console?

The Service Console is a Lightning console app designed for high-volume case handling. Unlike a standard navigation app where each record opens in a full page, a console app uses workspace tabs and subtabs. When an agent opens a case, it opens as a workspace tab; related records such as the contact, account, or knowledge articles open as subtabs beneath that case. This keeps all context for one customer interaction grouped together while allowing the agent to work several cases simultaneously.

Key components of the console include:

• Console Navigation: a tab-based layout with a navigation menu listing the objects and pages available to agents.
• Utility Bar: a persistent footer that can hold tools such as Omni-Channel, Macros, Notes, History, Softphone (Open CTI), and Agentforce Assistant. Utilities can be configured to load in the background and remain available regardless of which tab is active.
• Split View: a collapsible list view panel on the left side of the console that lets agents move through a queue of records without losing their current tab.
• Lightning Record Pages for Cases: built in Lightning App Builder, these pages commonly use a three-column layout with Highlights Panel, Case Feed or Chatter, Related Lists, Knowledge, and the Path component.
• Agentforce and Einstein features: Einstein Case Classification, Einstein Article Recommendations, Einstein Reply Recommendations, Agentforce Assistant for summarizing cases and drafting replies, and Agentforce Service Agent for handling customer conversations autonomously before escalating to a human.

The console is created and managed through the App Manager in Setup. When you create a new Lightning app you choose between Standard navigation and Console navigation; this choice cannot be changed after the app is saved. Salesforce also provides a prebuilt Service Console app that most organizations customize rather than rebuild.

What Is Case Feed?

Case Feed is a Chatter-based, chronological view of everything that happens on a case. Instead of scrolling through separate related lists for emails, call logs, and status changes, agents see one unified stream of feed items showing emails sent and received, internal posts, case status changes, field updates, attached files, and other activities. Case Feed is enabled by default in Lightning Experience and is surfaced through the Chatter component and, more importantly, the Quick Actions (publisher actions) configured on the case page layout.

In Lightning Experience, agents interact with Case Feed through feed actions such as:

• Email: sends an email from the case; requires Email-to-Case to be enabled and the Email action to be added to the page layout.
• Log a Call: records a completed call as a task related to the case.
• Post: creates an internal Chatter post for collaboration.
• Change Status, Change Owner, Update Case: custom or standard quick actions that update fields directly from the feed.
• Send Text (SMS) or Community Post when Digital Engagement or Experience Cloud is configured.

Case Feed also supports feed filters, allowing agents to see only emails, only internal posts, or all activity. Administrators control which filters appear and in what order, and they can set a default filter.

How It Works: Configuration Details You Must Know

1. Enabling and Configuring Case Feed
Case Feed in Lightning depends on Feed Tracking for the Case object. In Setup, under Chatter > Feed Tracking, you select the Case object and enable tracking for key fields such as Status, Priority, and Owner. Any tracked field change appears as a feed item. Next, you configure quick actions in the Salesforce Mobile and Lightning Experience Actions section of the case page layout. The order of actions here determines their order in the publisher.

2. Page Layouts and Record Types
Each case record type can have its own page layout, which means different quick actions, feed filters, and fields can appear for different types of cases. This is a frequent exam theme: when a scenario asks how to show different actions to agents handling different kinds of cases, the answer typically involves record types with separate page layouts.

3. Lightning App Builder
The Case record page is built with components. Common components tested include the Highlights Panel (compact layout fields shown at top), Path (guided status progression with key fields and guidance text), Related Record (editable contact or account details inline), Knowledge (article search and suggestions), and Chatter (the Case Feed itself). Component visibility can be controlled with filters based on field values, user profile, or device.

4. Macros
Macros automate repetitive multi-step tasks in the console, such as selecting an email template, inserting a greeting, sending the email, and changing the case status. Macros require the Macros utility in the utility bar and the Feed-based page layout actions to be present. Users need the Run Macros on Multiple Records permission for bulk macros and Manage Macros Users Can't Undo for irreversible macros. Macros are object-specific and respect the actions available on the page layout.

5. Quick Text
Quick Text provides predefined messages agents insert into emails, posts, and chat. It must be enabled, shared via folders, and is available in supported channels such as Email, Chat, Messaging, and Knowledge articles.

6. Email-to-Case
Case Feed email actions depend on Email-to-Case or On-Demand Email-to-Case being enabled with routing addresses. Inbound emails appear as feed items and as EmailMessage records. Administrators configure the default From address, email templates, and whether agents can select a From address that corresponds to an org-wide email address.

7. Omni-Channel Integration
Omni-Channel routes work to agents based on presence status, capacity, and skills. Cases routed through Omni-Channel open automatically in the console. The Omni-Channel utility must be in the utility bar for agents to set presence and accept work. The exam frequently combines console configuration with Omni-Channel scenarios.

8. Agentforce and Einstein for Service
Einstein Case Classification predicts field values on new cases; Einstein Article Recommendations suggests knowledge articles in the console; Einstein Reply Recommendations suggests chat responses. Agentforce Assistant, when licensed and enabled, offers case summaries, draft replies, and knowledge grounding directly within the console utility or record page. For the exam, remember that these features are additive and layered on top of the standard console—they do not replace page layout, quick action, or feed tracking configuration.

Common Troubleshooting Scenarios

• Agents cannot see the Email action in Case Feed: check that Email-to-Case is enabled, the Email quick action is on the page layout in the Lightning Experience Actions section, and the user has the relevant permissions.
• Status changes do not appear in the feed: Feed Tracking for the Status field on Case is not enabled.
• Macro fails to run: the required action is missing from the page layout or the Macros utility is not in the utility bar.
• Records open as full pages instead of tabs: the user is in a standard navigation app rather than the console app, or the object is not included in the console app's navigation items.
• Omni-Channel work does not auto-open: the Omni-Channel utility is not configured in the utility bar, or the agent presence status is not set to accept work.
• Different teams need different actions: assign distinct page layouts via record types and profiles.

Exam Tips: Answering Questions on Agentforce Service Console and Case Feed

Tip 1 – Identify the configuration layer. Most scenario questions are really asking which Setup area controls the behavior described. Memorize the mapping: quick actions and feed filters live on the page layout; components and column arrangement live in Lightning App Builder; tabs, utilities, and navigation items live in App Manager; feed item visibility for field changes lives in Feed Tracking.

Tip 2 – Watch for the word "automate." If a scenario describes an agent performing the same several clicks repeatedly, the answer is usually Macros. If it describes inserting the same text repeatedly, the answer is Quick Text. Do not confuse the two.

Tip 3 – Record types drive variation. When different groups of agents or different kinds of cases need different layouts, actions, or picklist values, think record types plus page layouts. Profiles control which record types are available, and page layout assignment is made per record type per profile.

Tip 4 – Console versus standard app. Remember that navigation style is chosen at app creation and cannot be switched. If a question involves tabs, subtabs, or split view, it must be a console app. If users complain records open in full-page mode, verify the app type.

Tip 5 – Utility bar items are prerequisites. Omni-Channel, Macros, Softphone, and Agentforce Assistant all need their utility added to the console app's utility bar. Many "why doesn't this work" questions are solved by adding the utility.

Tip 6 – Email actions have dependencies. Email in Case Feed requires Email-to-Case, the Email quick action on the layout, and appropriate email permissions. Org-wide email addresses control the From options.

Tip 7 – Einstein and Agentforce are enhancements, not replacements. If a question asks how to recommend knowledge articles automatically, the answer is Einstein Article Recommendations or the Knowledge component, not a workflow. If it asks about autonomous customer conversations, that is Agentforce Service Agent. Human agents working in the console use Agentforce Assistant. Always verify the scenario is about recommending, summarizing, or automating before choosing an AI feature.

Tip 8 – Eliminate answers that require code. The Advanced Administrator exam favors declarative solutions. Apex, Visualforce, or Lightning Web Component answers are almost always distractors unless the scenario explicitly states that declarative tools were exhausted.

Tip 9 – Read for the minimum necessary change. Salesforce exam answers prefer the simplest correct fix. If adding a quick action to a layout solves the problem, do not choose creating a new app or new record type.

Tip 10 – Know the permission names. Permissions such as Run Macros on Multiple Records, Manage Macros Users Can't Undo, Service Cloud User license, and Lightning Console User feature appear in answer choices. Be ready to recognize them.

Summary

The Agentforce Service Console is a tab-based Lightning app that consolidates case work, related records, knowledge, and tools in one workspace, while Case Feed provides a unified, chronological stream of case activity driven by feed tracking and quick actions. Administrators shape the agent experience through App Manager, Lightning App Builder, page layouts, record types, Feed Tracking, Macros, Quick Text, Email-to-Case, Omni-Channel, and Einstein or Agentforce features. On the exam, success comes from quickly identifying which configuration layer a scenario touches, choosing the simplest declarative solution, and remembering the prerequisites each feature depends on.