Service Cloud Solution Design practice questions

Utilize standard Case Escalation Rules with criteria based on Last Modified Date and Region

Why it fails: Case escalation rules do not integrate cleanly with Omni-Channel agent status and capacity tracking.

Write an asynchronous batch Apex job that queries unaccepted cases every 15 minutes and updates ownership

Why it fails: Batch Apex runs on a schedule, so reassignment waits up to 15 minutes after the query, exceeding the stem's 15-minute acceptance window and risking duplicate updates. It tempts because batch Apex suits bulk, non-urgent record maintenance. Escalation timing here demands time-dependent workflow or scheduled flow logic.

Implement Einstein Next Best Action with automated record updates via Process Builder

Why it fails: Einstein Next Best Action recommends actions to agents rather than automating queue reassignments.

Service Cloud Console Workspace Tabs

Why it fails: Console Workspace Tabs organise records and utilities for agents but provide no supervisor monitoring or whisper capability for messaging sessions. It is tempting because supervisors use consoles, yet session monitoring and whisper require the Omni-Channel supervisor interface, not workspace tab configuration.

Case Feed collaboration groups

Why it fails: Case Feed collaboration groups post internal messages on a case record; they do not surface live messaging sessions or allow whispering. It is tempting because both support internal collaboration, but whisper and session monitoring need the Omni-Channel supervisor interface, not feed-based case discussion.

Live Agent Supervisor Panel

Why it fails: Live Agent Supervisor Panel belongs to the legacy Live Agent chat product, not Messaging for In-App and Web. It is tempting because the name describes the required capability, but messaging sessions are monitored through the Omni-Channel supervisor interface instead.

Export cases to an external data lake weekly and delete them from Salesforce using Data Loader.

Why it fails: Weekly export and deletion is manual, batch-based and risks data loss between runs, and Data Loader cannot sustain millions of records reliably. It is tempting as a low-cost offload pattern, but it suits small one-off migrations rather than continuous high-volume archiving with retention and search requirements.

Store closed cases in standard custom objects and enable skinny tables on the custom object.

Why it fails: Skinny tables replicate indexed fields to speed queries, but they do not remove records from primary storage, so the storage limit and search performance problems persist. It is tempting because skinny tables optimise large-object queries, yet they are a query-tuning measure, not an archiving strategy.

Utilize Platform Cache to retain historical case summaries in memory.

Why it fails: Platform Cache stores temporary session or org data in memory with expiry, offering no durable archive, no queryability and no reduction in case storage consumption. It is tempting for performance-sensitive lookups, but it suits transient caching of frequently accessed values, not long-term retention of millions of closed cases.

Assignment Rules

Why it fails: Assignment rules only set the owner or queue on case creation; they cannot route work to Omni-Channel agents based on region. They are tempting because they are the standard declarative mechanism for automatically assigning incoming cases, and would be correct if the requirement were ownership rather than routing.

Process Builder

Why it fails: Process Builder automates field updates and record creation, but it does not distribute work items to Omni-Channel agents by region. It is tempting because it is the general-purpose automation tool for case logic, and would suit scenarios needing custom field updates or notifications rather than routing.

Escalation Rules

Why it fails: Escalation rules act on cases already owned, reassigning or notifying after time-based criteria are met; they cannot route new web-to-case submissions by region. They are tempting because they are the standard tool for time-driven case action, and would be correct for ageing or SLA-breach scenarios.

Service Cloud Voice with Amazon Connect integration

Why it fails: Service Cloud Voice with Amazon Connect handles voice calls and contact routing, not inbound SMS self-service deflection links. It is tempting because it integrates IVR with Salesforce, but the stem requires ingesting an SMS interaction, which needs a messaging channel such as Enhanced Messaging or Digital Engagement.

Live Agent chat deployment with pre-chat forms

Why it fails: Live Agent chat handles web-based text sessions with pre-chat forms, not inbound IVR-triggered SMS deflection. It is tempting because both are digital engagement channels, but chat requires a browser session, whereas the scenario needs telephony-driven messaging ingestion.

Email-to-Case with automated auto-response rules

Why it fails: Email-to-Case processes inbound emails, not inbound SMS or IVR text triggers.

Write a scheduled Flow that updates the Skill Requirements related list every 3 minutes.

Why it fails: A scheduled Flow cannot react within the 3-minute window or modify skill requirements mid-routing; it runs on a fixed schedule. It is tempting because it automates skill updates, but Omni-Channel's native skill-based routing with skill expiry and priority handles time-based skill relaxation directly.

Use standard queue-based fallback routing configurations.

Why it fails: Standard queue-based fallback only reassigns to another queue when no agent is available; it cannot progressively strip skills from the routing criteria after a timed interval. It is tempting because queue-based routing suits simple overflow between teams, but skill-priority decay requires Omni-Channel skill-based routing with a custom routing configuration.

Deploy an Einstein Bot to re-evaluate customer skills periodically.

Why it fails: An Einstein Bot converses with customers and cannot alter Omni-Channel routing work items or strip skills from a pending case's routing criteria. Bots suit deflecting or triaging enquiries before case creation, yet the requirement is timed skill decay within the routing engine itself, not conversational re-evaluation.

Case Escalation Summary Report

Why it fails: Case Escalation Summary reports track escalation age and rule activity, not Knowledge article attachment or resolution outcome. It would be the right report for monitoring overdue or escalated cases, but the stem requires linking articles to cases closed without reopening.

Omni-Channel Agent Workload Report

Why it fails: The Omni-Channel Agent Workload Report shows capacity consumption and work item distribution across agents. It would suit staffing and routing analysis, but it carries no Knowledge article linkage, so it cannot show whether attached articles resolved cases without reopening.

First Contact Resolution Trend Report

Why it fails: First Contact Resolution Trend measures whether cases close on the first interaction, typically via case origin or handle time. It would fit a channel-effectiveness review, but it does not report Knowledge article attachment, so it cannot evidence article-driven resolution.

Write an assignment rule with formula criteria evaluating User.CurrentCapacity.

Why it fails: Assignment rules execute upon record creation/update, not continuous real-time agent capacity shifts.

Create a scheduled Flow that checks agent capacity every minute and reassigns cases.

Why it fails: A scheduled Flow polling every minute cannot react to capacity-change events, so assignment lags and races with Unified Routing's real-time capacity checks. Flows suit bulk record operations, such as nightly reassignment of stale cases. Unified Routing assigns work items the moment an agent's capacity drops below the threshold and their skills match.

Utilize Einstein Next Best Action to prompt agents to pull cases from queues.

Why it fails: This relies on manual pull behavior rather than automated push routing.

Einstein Prediction Builder component

Why it fails: Prediction builder displays predictive analytics scores, not related child records.

Omni-Channel utility widget

Why it fails: Omni-Channel routes incoming work items to agents; it does not surface related record data on a record page. It is tempting because it lives on the utility bar alongside record-page components, and would be correct when the requirement is workload distribution or agent presence management rather than displaying related customer asset details.

Global Search result component

Why it fails: Global Search returns matching records across objects in a results list, not the assets related to the open case. It is correct when agents need to locate records by keyword rather than view a case's related list.

Case Escalation Rules with custom survey email templates.

Why it fails: Case Escalation Rules trigger on escalation criteria such as case age or priority, not on a status change to Closed, and they cannot schedule a delayed send. They would be correct for notifying managers of at-risk cases, not for a 24-hour post-closure survey.

Chatter post automatic notifications with survey links.

Why it fails: Chatter posts notify internal followers within Salesforce; they cannot email an external contact, and Chatter has no 24-hour delayed trigger tied to case closure. Chatter would suit internal case collaboration, not automated customer survey delivery.

Standard Email-to-Case auto-response rules with survey links.

Why it fails: Email-to-Case auto-response rules fire on inbound email receipt, not on a case status change, so they cannot trigger 24 hours after closure. They suit acknowledging new cases. The requirement needs a time-based workflow or flow scheduled off the Closed status.

Visualforce controllers with email messaging classes

Why it fails: Visualforce controllers require a custom page or component to execute, so they cannot react to a field change on their own. They tempt because Apex can reassign owners and send email, and would be correct if the escalation needed a bespoke user interface.

Workflow Rules and Email Alerts

Why it fails: Workflow Rules cannot change the case owner; owner reassignment needs a flow, assignment rule or escalation rule. Email alerts alone also cannot deliver the owner change. It tempts because workflow plus email alert is the classic notification pattern, and would suffice if only an email were required.

Case assignment rules triggered via manual button clicks

Why it fails: Manual button clicks require an agent to act each time, so escalation would not fire automatically when the status changes. Assignment rules are tempting because they route cases to queues and owners, but they run on case creation or edit via criteria, not on a user-triggered button.

Deploy a custom Visual Workflow triggered by inbound emails.

Why it fails: Visual Workflow cannot be triggered by case creation; it runs only when a user launches a flow from a button or link, so no automatic entitlement lookup occurs. It suits guided data-entry screens, not record-triggered automation, which requires a before-save flow or Process Builder on Case.

Write a complex trigger on Contact to update Case upon insert.

Why it fails: A Contact trigger fires on Contact insert, not Case insert, so creating a case never executes it; the entitlement lookup would only run when the contact record itself changes. Contact triggers suit keeping contact fields synchronised, not populating a child Case's entitlement at creation.

Use Workflow Rules to populate lookup field values across relationships.

Why it fails: Workflow Rules cannot set lookup field values by traversing relationships; they only assign values already available on the triggering record or its parent. Cross-object lookup population needs a before-save record-triggered flow, which resolves the customer's active contract directly.

Use validation rules to prevent users from typing credit card numbers.

Why it fails: Validation rules stop user entry, but cannot prevent external customers from submitting credit cards via Web-to-Case forms.

Configure Field-Level Security to hide the description field from all agents.

Why it fails: Hiding the description entirely prevents agents from reading the customer's actual inquiry.

Rely on standard browser page encryption protocols (HTTPS)

Why it fails: HTTPS encrypts data in transit, but once stored in Salesforce, agents can view plaintext unless masked.

Auto-response rules configured with queue override parameters

Why it fails: Auto-response rules only send automated replies to senders; they cannot reassign cases or route them to a queue or owner. They suit acknowledging receipt. Domain-based assignment to a named Account Manager requires case assignment rules with a matching email-domain condition.

Omni-Channel routing configurations based on IP white-listing

Why it fails: IP whitelisting controls network login security, not email-based queue bypasses.

Standard assignment rules referencing Email Message fields directly

Why it fails: Standard case assignment rules evaluate Case fields, not child EmailMessage fields directly upon initial insertion without flow assistance.

Custom Apex trigger performing SOSL queries on every keystroke

Why it fails: A trigger firing SOSL on every keystroke issues a query per character, exceeding governor limits and returning unranked matches without engagement signals. Triggers suit server-side logic on record save, not real-time predictive article and case suggestion.

Standard global search bar in the utility bar

Why it fails: A global search bar only returns results after the agent submits a query, so it cannot surface articles or cases from text as it is typed. It is tempting because it searches across objects from the utility bar, and would suit an agent who already knows what to look for and searches deliberately.

Scheduled batch reports emailed to agents daily

Why it fails: Daily batch reports deliver static, pre-run data by email, so nothing is suggested against the live case text in real time. Scheduled reporting is genuinely useful for trend analysis and backlog monitoring, which is why it appears here, but it cannot respond to typing.

Assignment Rule criteria evaluation

Why it fails: Assignment rules only route or assign a case based on criteria; they cannot block case creation or display a validation failure when the purchase date falls outside warranty. They suit automatic ownership routing, but date-range validation against the product's purchase date needs a validation rule.

Entitlement Process milestone warning action

Why it fails: Milestone warning actions fire on entitlement milestone timers to alert or escalate, not to validate a product's purchase date at case creation. Entitlement processes suit tracking service-level timelines, whereas blocking a case whose purchase date exceeds the 2-year warranty requires a validation rule.

Process Builder scheduled action

Why it fails: A scheduled action runs at a future time after the record is saved, so it cannot prevent or flag an invalid case during entry. Scheduled actions suit time-delayed follow-ups, but immediate purchase-date validation against the 2-year warranty window requires a validation rule firing on save.

Rely on standard browser tab refresh events triggered by Apex controllers.

Why it fails: Browser tab refresh events fire on page reloads and cannot be triggered by Omni-Channel call acceptance, so no case tab opens. Tempting as a lightweight scripting approach, it would be correct for refreshing stale console data, not for event-driven tab opening tied to a routed voice call.

Write a custom Open CTI JavaScript adapter utilizing legacy Workspace API methods.

Why it fails: Open CTI adapters integrate external telephony and expose call events, but legacy Workspace API methods are deprecated and do not open primary tabs in the modern console. Tempting because CTI adapters handle softphone events, they would be correct for screen-pop of external systems, not for native case tab routing.

Use Entitlement milestone actions to force window navigation.

Why it fails: Milestone actions fire on entitlement milestone completion, not on voice call acceptance, so they cannot pop a case tab when an agent answers. Entitlement processes are tempting because they automate case actions against service-level targets, and would be correct for triggering time-based workflow on entitled cases.

Convert all Case reports to joined reports with zero common blocks

Why it fails: Joined reports with zero common blocks cannot aggregate millions of Case records into weekly volume summaries; they exist to present separate report blocks side by side, each with its own filters. That structure suits dashboards comparing unrelated datasets, not summarising one object's volume, so it leaves the degraded query performance unaddressed.

Enable Platform Cache partitions for Case reports

Why it fails: Platform Cache stores session or org-wide data in memory, which cannot aggregate millions of Case records at query time; it caches computed results rather than accelerating SOQL aggregation. It is tempting because caching genuinely reduces repeated report load, and would be correct for frequently requested, slowly changing datasets — not for weekly summaries over the full Case object.

Export half the data to CSV and delete it from the primary database daily

Why it fails: Deleting core data destroys historical reporting context.

Entitlement Processes with milestone warnings

Why it fails: Entitlement milestones measure progress against service-level targets on entitled cases; they do not record arbitrary lifecycle stages or duration per stage. They tempt because they track time-based case events, and would be correct for enforcing support terms and warning before an SLA breach.

Salesforce Knowledge article feedback ratings

Why it fails: Article feedback ratings capture usefulness votes on published Knowledge articles; they record no case stage transitions or time-in-stage metrics. They tempt because they report on Knowledge performance, and would be correct for measuring whether self-service articles resolve customer questions.

Chatter feed tracking for system logs

Why it fails: Chatter feed tracking posts field-change notifications to a record feed; it stores no structured stage history or duration reporting. It tempts because it surfaces case changes, and would be correct for alerting followers to updates, not for measuring lifecycle stage durations.

Execute all migration inserts using synchronous SOAP API single-record calls in real time

Why it fails: Synchronous single-record SOAP calls cause massive performance bottlenecks and timeouts for large migrations.

Load all legacy attachments directly into standard task description fields as plain text blobs

Why it fails: Storing file attachments in task description fields destroys file formats and attachment relationships.