Troubleshooting Scenario Questions

Standard Case Comment related list

Why wrong: Case comments are unstructured text boxes and do not provide dynamic step-by-step guidance.

Quick Actions with predefined field values

Why wrong: Quick actions execute predefined field updates or record creations, not interactive conditional questionnaires.

Entitlement Processes

Why wrong: Entitlement processes manage SLAs and time-based milestones, not agent scripting interfaces.

Cases created outside business hours immediately trigger escalation actions upon creation.

Why wrong: Creating cases outside business hours pauses or delays the start of the business hours timer until business hours resume.

The escalation rule will throw a system exception due to timezone mismatch.

Why wrong: Timezone mismatches cause scheduling shifts, not system exceptions.

Escalation rules ignore business hours entirely and always use 24/7 calendar time.

Why wrong: Escalation rules can be tied to business hours, meaning timers only increment during business hours.

ServiceChannel

Why wrong: ServiceChannel defines the object type, not the specific work record ID.

AgentWork

Why wrong: AgentWork is created after routing is initiated, not passed into the initial flow trigger.

User Presence ID

Why wrong: User presence tracks agent availability, not incoming work item context.

Check that the Debug Log level for Workflow is set to Maximum.

Why wrong: Flows are debugged via Flow Debugger, not workflow log levels.

Verify that external API endpoints are configured for native queue routing.

Why wrong: Native queue routing does not require external API endpoints.

Case Team members were not assigned read permissions on the escalation queue.

Why wrong: Queue permissions do not directly prevent escalation rule execution.

The case was created via Email-to-Case, which bypasses escalation rules entirely.

Why wrong: Email-to-Case cases are fully eligible for escalation rules.

Chatter post frequency limits for external users.

Why wrong: Chatter limits do not impact Email-to-Case ingestion.

The number of active Case Assignment Rules in the recycle bin.

Why wrong: Items in the recycle bin do not affect live email processing.

Business hours are not assigned to the User profile.

Why wrong: Incorrect. Business hours are assigned to the entitlement process or account/case, not directly defaulted strictly via user profiles for milestone generation.

The Entitlement is associated with a Service Contract instead of an Account.

Why wrong: Incorrect. Entitlements can be associated with either accounts or service contracts.

The Entitlement Template has not been applied to the Contact record.

Why wrong: Incorrect. Templates are only used during initial creation; active entitlements already exist on the account.

Omni-Channel Supervisor real-time metrics dashboard.

Why wrong: Incorrect. Omni-Channel supervisor monitors agent workloads, not backend API integrations.

Knowledge article version history.

Why wrong: Incorrect. Knowledge article history tracks publishing revisions, not external API transactions.

Standard Case History related lists on individual records.

Why wrong: Incorrect. Case history tracks standard field modifications, not API integration transport errors.

Use Web-to-Case to automatically attach knowledge articles.

Why wrong: Web-to-Case captures web forms; it does not attach internal files to outbound emails.

Paste the file URL into the subject line of the email.

Why wrong: Pasting URLs does not attach the actual file document.

Use a Macro to upload the file from the agent's desktop.

Why wrong: Macros execute instructions, they don't replace standard file attachments.

Create a custom approval process that routes to tier-2 agents upon submission for publication.

Why wrong: Incorrect. Approval processes handle the review workflow, not the fundamental permission to publish within data categories.

Set the sharing model for Knowledge to Private and use manual sharing rules.

Why wrong: Incorrect. Knowledge uses Data Categories and sharing rules rather than standard object-level manual sharing for publishing permissions.

Modify the record types assigned to the tier-1 support profile to exclude hardware articles.

Why wrong: Incorrect. Record types control layout and picklist values, not category-level publishing permissions.

Queues are automatically deleted from the system.

Why wrong: Queues remain intact; only the routing channel link is disabled.

Agents cannot log into Omni-Channel.

Why wrong: Agents can log in, but no work for that channel will be routed.

Existing open work items are automatically closed.

Why wrong: Open work items remain on agent tabs but routing is halted.

It relies entirely on manual tagging performed by agents when closing previous cases.

Why wrong: Incorrect. While attached articles help machine learning, the base system performs keyword and text analysis.

It requires custom Apex triggers that query articles using SOSL and push them to a custom related list.

Why wrong: Incorrect. Recommendations are handled natively by the Lightning Knowledge component.

It uses Assignment Rules configured in Setup to match case categories to data categories.

Why wrong: Incorrect. Assignment rules do not power Lightning Knowledge search recommendations.

Create a custom Lightning component override for the New Article button.

Why wrong: Incorrect. Overriding standard buttons with custom components is unnecessary since feed actions support mapping.

Use Workflow Rules with field updates on the Knowledge object.

Why wrong: Incorrect. Workflow rules execute after save and cannot pre-populate values during the creation dialog.

Write an Apex trigger on the Case object that inserts a Knowledge record on creation.

Why wrong: Incorrect. Triggers cannot easily launch interactive console article creation workflows.

Knowledge translation is only supported for internal users with a full Salesforce license.

Why wrong: Knowledge translations are fully supported in Experience Cloud sites for community users.

Translated articles automatically default to 'Archived' status when viewed by community license holders.

Why wrong: Article status does not dynamically change based on the license type viewing it.

The Knowledge component in Experience Cloud must have hardcoded language codes defined in URL parameters.

Why wrong: Language selection in Experience Cloud sites is handled via site settings and locale mappings rather than URL parameter hardcoding.

The organization has exceeded its daily limit of custom Service Channels.

Why wrong: Service channel limits are rarely the primary cause and service channels are standard platform definitions.

The agent's profile lacks access to the Omni-Channel utility in the Lightning Console app.

Why wrong: Console app utility access affects visibility of the widget, but queue routing still attempts assignment (though acceptance fails if the widget isn't used). However, missing presence status or queue membership are primary direct routing failures.