Service Cloud Consultant Interview Questions

Case Assignment Rules automatically route cases to the appropriate user or queue based on criteria. Each rule consists of multiple rule entries evaluated in order — the first matching entry wins. Assignment can be triggered when a case is created or edited, and can be invoked from Web-to-Case, Email-to-Case, or when an agent manually checks "Assign using active assignment rules." Only one assignment rule can be active at a time. When no rule entry matches, the case is assigned to the default case owner defined in Support Settings.

Escalation Rules automatically escalate cases that haven't been resolved or actioned within a defined time period. Each rule entry specifies criteria, a time trigger (age over X hours), and the escalation action — which can reassign the case to a new owner/queue and/or send a notification email. The "business hours" setting on an escalation rule determines whether non-business hours count toward the escalation timer. Like assignment rules, only one escalation rule can be active per org at a time.

Web-to-Case generates an HTML form that customers fill out on a website; on submission, Salesforce creates a case directly from the form data. Email-to-Case creates a case from an inbound email sent to a designated email address. On-Demand Email-to-Case uses a Salesforce-managed forwarding address — no local agent is required. Standard Email-to-Case requires a local agent installed behind the firewall to download emails via POP3/IMAP. Both methods support auto-response rules and can trigger assignment rules on case creation.

Entitlements define the support level a customer is entitled to (e.g., 24/7 phone support, email support within 8 hours). They are associated with Accounts, Contacts, Assets, or Service Contracts. Milestones are required, time-based steps within an Entitlement Process — for example, "First Response within 4 hours" or "Resolve within 24 hours." Milestone action types include: time-trigger warning actions (approaching deadline), violation actions (deadline missed), and completion actions. Milestone statuses are: Open, Completed, or Violated. Entitlement processes can be paused using Business Hours and Holiday records so that weekends and holidays do not count toward SLA timers.

The Service Console is a multi-tab app optimised for high-volume case handling. Key features include: (1) Workspace Tabs — multiple records open simultaneously as tabs. (2) Split View — a collapsible list panel alongside a detail pane for faster navigation. (3) Utility Bar — a persistent bottom bar housing components like History, Macros, Softphone, and Omni-Channel widget. (4) Case Hovers — hover over related records for quick detail without full navigation. (5) Keyboard Shortcuts — custom shortcuts for navigation and actions. (6) Macros — automated multi-step actions that agents can run with one click.

Macros automate repetitive tasks in the Service Console, allowing agents to perform multi-step sequences with a single click. The three types are: (1) User-Activated Macros — agents manually run these from the Macros widget or utility bar; they can include conditional logic. (2) Background Macros — run without displaying step-by-step actions to the agent; faster for non-interactive tasks like field updates or sending predefined emails. (3) Bulk Macros — applied to multiple selected cases simultaneously from a list view, ideal for mass updates or communications. Macros are built using the Macro Builder and can perform actions on cases, emails, chatter posts, and more.

Salesforce Knowledge is a knowledge base for storing articles that agents and customers can use to resolve issues. The article lifecycle is: Draft (article created, visible only to authors) → In Review (submitted for approval/review by editors) → Published (visible to designated audiences). Articles can be versioned — when a published article is edited, a new draft version is created while the published version remains live until the new version is published. Knowledge supports Data Categories for classification and access control, article voting for quality tracking, and the Knowledge Sidebar in the Service Console for contextual article suggestions.

Category Groups are the top-level containers that organise Data Categories — for example, "Products" or "Geography." Each Category Group defines a dimension of classification. Data Categories are the individual classification values within a group — for example, under "Products": "Cloud Storage," "CRM," "Analytics." Articles can be assigned to one or more categories. Data Category Visibility (set via profiles or permission sets) controls which categories — and therefore which articles — users can see. Category Groups can also be used to control article visibility in Experience Cloud communities.

Omni-Channel supports three routing models: (1) Most Available — routes work to the agent with the highest ratio of open capacity to total capacity. Best for even workload distribution. (2) Least Active — routes to the agent with the fewest open work items, regardless of capacity percentages. Best for equal work-item count distribution. (3) External Routing — integrates with a third-party routing engine via the Omni-Channel API; Salesforce passes work item details to the external system, which determines assignment. Additionally, Skills-Based Routing (an enhancement) matches work items to agents based on required skills defined on the queue or routing configuration rather than just availability.

The Omni-Channel Supervisor dashboard gives service managers real-time visibility into their team's activity. It displays: agent presence status (available, busy, offline), current capacity and work assignments, queue backlog (items waiting to be routed), average wait time per queue, and agent performance statistics. Supervisors can drill into individual agent views to see all active work items. The dashboard uses Streaming API for live updates without page refresh. It is accessible from the Service Console as a utility bar component or as a standalone tab.

Open CTI is a JavaScript API that allows third-party telephony providers to integrate their softphone directly into the Salesforce Service Console without requiring a desktop adapter. Configuration steps: (1) Define a Call Center record in Setup using the provider's CTI Adapter XML definition file. (2) Add users to the Call Center. (3) Create a Softphone Layout to define what information appears in the softphone panel for incoming/outgoing calls (screen pop objects, related records). (4) Assign the Softphone Layout to profiles. Key Open CTI events include onClickToDial, onCallBegin, onCallEnd, and refreshView for screen pop automation.

Einstein for Service includes: (1) Case Classification — automatically predicts and populates case fields (Priority, Reason, Type) based on case content. (2) Case Routing — routes cases to the right queue/agent using AI predictions. (3) Reply Recommendations — suggests email/chat responses drawn from past resolved cases. (4) Article Recommendations — surfaces relevant Knowledge articles on open cases. (5) Recommended Actions / Next Best Action — presents agents with contextual action suggestions using Einstein Next Best Action. (6) Einstein Bots — NLP-driven chatbots built in Bot Builder that handle routine questions, collect information, and hand off to live agents; bots use Variables to store session data and Dialog-based flows for conversation management.

Einstein Bots are NLP-based chatbots configured in Bot Builder using Dialogs — conversation flows that handle user intents. Each dialog contains Steps (messages, questions, actions). Bot Variables store data collected during the conversation (e.g., case number, customer name). When bot resolution fails or the customer requests a human agent, the bot performs a Transfer to Agent step, which routes the conversation to an Omni-Channel queue. The full conversation transcript is transferred to the agent's console. Bots can be deployed on messaging channels (web chat, SMS, WhatsApp) and integrate with Salesforce data via SOQL queries or Apex actions within the bot flow.

Experience Cloud powers self-service portals where customers can search the Knowledge base, submit and track cases, and participate in community forums — reducing inbound support volume. Key capabilities: (1) Knowledge Search — federated search surfaces articles based on data category visibility for the guest or authenticated user. (2) Community Cases — customers can create, view, and update their own cases from the portal. (3) Case Deflection — before case submission, relevant articles are suggested, reducing unnecessary case creation; case deflection rate is a key metric tracked in community reports. The Customer Service template is pre-built for self-service use cases.

Social Customer Service (SCS) connects Salesforce with social media platforms (Twitter/X, Facebook, Instagram) via Social Studio (Radian6) integration. When a customer posts or mentions the brand on a connected social channel, SCS can automatically create a case or lead in Salesforce. Agents respond directly from the Service Console, and responses are posted back to the social channel. SCS uses Apex-based routing rules to determine which social posts become cases. Social cases appear in queues like any other case and can be subject to the same assignment, escalation, and Omni-Channel routing rules.

Salesforce Surveys allow you to build multi-page surveys with branching logic, rating scales, and text questions natively in Salesforce. Survey responses are stored as Survey Response objects and can be reported on. Surveys can be triggered automatically using Flow — for example, a Record-Triggered Flow fires when a case is closed (Status changed to Closed) and invokes the Send Survey action, emailing the survey link to the case contact. Survey response data can be used to calculate CSAT scores, tracked on dashboards, and linked back to the originating case or contact for analysis.

Key contact center metrics include: (1) AHT (Average Handle Time) — average duration of a customer interaction from start to completion, including wrap-up time. (2) FCR (First Contact Resolution) — percentage of issues resolved on the first contact without follow-up. (3) CSAT (Customer Satisfaction Score) — post-interaction survey rating. (4) NPS (Net Promoter Score) — likelihood of customer recommendation, tracked via surveys. (5) SLA Compliance — percentage of cases meeting milestone deadlines. These metrics are surfaced via Service Cloud reports, dashboards, and Omni-Channel Supervisor analytics.

Queues hold cases, leads, or other records until an agent picks them up or they are assigned via Omni-Channel. Overflow routing handles situations where queue capacity is exceeded or no agents are available: (1) Cases can be routed to a secondary/overflow queue via assignment rules when the primary queue exceeds a threshold. (2) Omni-Channel routing configurations include a Routing Overflow setting (available in Enhanced Omni-Channel) that re-queues or reassigns work when no agents are available. (3) Escalation Rules provide time-based overflow by reassigning cases that sit in a queue too long. Priority settings on routing configurations ensure high-priority work reaches agents first.

End-to-end SLA configuration: (1) Create Business Hours and Holidays in Setup. (2) Build an Entitlement Process with milestones (e.g., First Response: 4 hours, Resolution: 24 hours) and define milestone actions for warnings and violations. (3) Create Entitlement records linked to Accounts/Contacts/Assets, referencing the Entitlement Process and Business Hours. (4) Configure the Case page layout to include the Entitlements related list and the Milestone Tracker. (5) When a case is created, agents associate the appropriate Entitlement, and the milestone timers begin. The SLA escalation matrix is built using milestone violation actions that reassign or notify managers when deadlines are missed.

Live Agent (now part of Messaging for Web/In-App) enables real-time chat between customers and agents. Setup involves: (1) Enable Live Agent in Setup. (2) Create a Live Agent Configuration defining agent capacity, routing, and chat settings. (3) Create a Deployment (generates a JavaScript snippet for the website). (4) Create Chat Buttons linked to queues or skills. Omni-Channel routes incoming chats using routing configurations — agents must have the "Routing Configuration" assignment on their profile/queue. Wait time estimates can be displayed on the pre-chat form. Chat transcripts are saved as cases with the full conversation, supporting case merge and threading for follow-ups.

Case Merge allows agents to combine up to 3 duplicate cases into a single master case. Activities, emails, and comments from merged cases are transferred to the master. Merged cases are closed and marked as duplicates. Email Threading keeps all email replies on a case connected by embedding a thread ID (e.g., ref:_00D..._500...:ref) in email footers. When a customer replies, Salesforce matches the thread ID to the original case and appends the reply as a new email activity rather than creating a duplicate case. Email threading tokens are configured in Email-to-Case settings under Support Settings.

Auto-Response Rules automatically send an email reply to a customer when a case is created via Web-to-Case or Email-to-Case. Each rule has multiple entries with criteria — the first matching entry determines which email template is sent. Common uses: (1) Sending a case confirmation email with the case number. (2) Sending different responses based on case priority or origin (e.g., a premium support acknowledgment for high-priority cases). (3) Providing self-service links or Knowledge article suggestions in the auto-response. Only one auto-response rule can be active per object at a time. If no rule entry matches, no auto-response is sent unless a default is configured.

Salesforce Files allows agents and customers to attach files directly to cases. Files are stored in Salesforce Content and linked to cases via the Files related list (Content Document Link). Key features: (1) Files can be shared across multiple records simultaneously without duplication. (2) Version control allows uploading new file versions while preserving history. (3) Files can be attached to email messages on cases. (4) Customers can upload attachments via Experience Cloud portals. (5) File size limits (default 2 GB per file) and storage quotas apply. Files differ from legacy Attachments (binary large objects tied to a single record) — Files are the preferred modern approach.

Routing priority determines the order in which work items are assigned to agents when multiple items are queued. Each Routing Configuration has a Priority value (lower number = higher priority) — when an agent becomes available, the system first assigns the highest-priority work item across all queues the agent belongs to. Wait time estimates in Live Agent/Messaging are calculated based on current queue depth and average handle time from historical data. Agents can also have a Capacity setting (units of work they can handle simultaneously) and a Capacity Weight per channel type, allowing fine-grained control over agent workload.

Service territories in the context of digital channels (as opposed to Field Service Lightning) refer to organisational groupings used to route digital interactions — such as chat and messaging — to the right team based on geography, language, or business unit. In Messaging for In-App and Web, territories can be applied through routing configurations that restrict which agents or queues handle work from specific channels or regions. This ensures, for example, that French-speaking customers are routed to French-speaking agents, or that EMEA cases go to the EMEA support queue. Territories can be combined with skills-based routing for precise, multi-dimensional matching.