Section 5 · Cloud Applications · 11% of exam
5.3 Knowledge, entitlements, and service channels
Exam objective
Explain how to create and maintain Salesforce Knowledge, service entitlements and processes, and customer-support interaction features.
Salesforce Knowledge organizes reusable articles for agents and, when configured, customers or partners. Article record types can support distinct article processes or types, while data categories classify and filter content for browsing and access. Authors create and update draft content, reviewers approve it, and publication controls when an article becomes available. Establish ownership, versioning, review dates, and retirement rules so outdated instructions do not continue to guide support work.
A well-designed article model starts with the audience and the question the article should answer. Use clear titles, concise procedures, troubleshooting steps, and metadata that make articles discoverable. Data category groups can organize content, and category visibility controls which users can see articles in those categories. Article permissions and audience access matter as much as article text. Do not place confidential customer details or credentials in reusable knowledge content. Test search terms, category filtering, language behavior, and visibility using agent and external-user personas. Entitlements represent a customer's service rights, such as support coverage or response commitments. Entitlement processes define milestones and criteria for tracking service obligations. They can be associated with accounts, assets, or cases depending on configuration. Milestones can measure time-sensitive obligations and may have warning, violation, or success actions. Business hours and milestone criteria influence timing. Validate how paused cases, reopened cases, holidays, and changes to entitlement status affect the clock. An entitlement does not automatically enforce every contractual term; map the contract to the process deliberately.
Support agents interact through case management tools. Case Feed presents case-related conversations and actions. Agentforce Service Console helps agents work across cases and related records. Chat can support live customer interactions where the org has the relevant feature and channel configured. Experience Cloud sites can provide self-service and external collaboration, subject to user license and sharing design. Omni-Channel routes work to agents based on configured queues, presence, capacity, and routing settings. These features operate as a service workflow; they do not eliminate the need to configure case assignment, knowledge access, record permissions, and escalation behavior.
When a case is not routed, inspect the routing configuration and the agent's presence, capacity, queue membership, and eligible work. When an agent cannot see an article, review article publication state, data category visibility, channel, and permissions. When a milestone is late, check the entitlement association, start criteria, business hours, and pause behavior. Use service console pages to expose the information an agent needs, but avoid adding fields or components that reveal data beyond the user's authorized scope.
For a new support design, map the customer's entry point, case creation, classification, routing, knowledge suggestion, entitlement, escalation, and resolution. Test each path as an internal agent and an external customer if both are supported. Include edge cases like duplicate cases, low staffing, unavailable agents, unsupported channels, expired entitlements, and unpublished articles. Measure service outcomes through reports and dashboards, and keep operational policy aligned with the automation.
Exam focus: distinguish article structure and category visibility, entitlement coverage and milestone timing, and interaction channels such as console, Experience Cloud, and Omni-Channel. For a service-level requirement, choose an entitlement and process rather than a general task reminder. For routing, inspect agent eligibility and capacity. Confirm licensing and sharing for external users. Do not treat a polished interface as proof that the underlying case or knowledge access is correct.
Test service paths with at least one internal agent and one external user where both audiences are part of the design.
Content governance should include review frequency, expiration, translations, and feedback from agents. Search quality depends on article titles, synonyms, and clear categorization; category visibility can also limit discovery. Entitlement calendars must match the contract's time zone, holidays, and business hours. For routed work, monitor queue age and capacity, not only whether routing is enabled. Make an escalation path for overflow or unavailable agents. These operating details determine whether the configured service feature meets the customer promise after launch. Practical scenario
A premium customer has a two-hour first-response commitment, and agents should see a vetted troubleshooting article. Associate the case with the correct entitlement, configure a milestone using the business's service calendar, and make the relevant article published and visible to the agent's category audience. Route the case through Omni-Channel only if eligible agents have the right presence and capacity. Test paused, reopened, after-hours, and expired-coverage cases. Extra concept
Service channels can create a single customer journey but have separate license and access requirements. An Experience Cloud user, internal agent, and knowledge publisher may need different permissions. Design those personas explicitly instead of copying one broad permission set across all service participants.
Key takeaways
- Knowledge publication and category visibility determine article discoverability.
- Entitlements and milestones track service commitments using criteria and business hours.
- Check channel, routing, agent capacity, licenses, and external sharing together.
- Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.knowledge_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.entitlements_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.omnichannel_intro.htm&type=5
