Einstein Article Recommendations
Einstein Article Recommendations is the Service Cloud feature that suggests Salesforce Knowledge articles to a support agent based on the open case.
Definition
Einstein Article Recommendations is the Service Cloud feature that suggests Salesforce Knowledge articles to a support agent based on the open case. When an agent loads a case, Einstein analyzes the case description, subject, and any prior comments, scores every accessible Knowledge article for relevance, and surfaces the top matches in a sidebar component. The agent can attach the article to the case or insert its content into a reply with one click, cutting the search time that traditionally ate the first minute of every case.
The feature ships with Service Cloud editions that include Einstein, runs on a Salesforce-managed model that needs no per-org training, and uses the org's actual Knowledge base as the candidate pool. Its impact is bounded by Knowledge hygiene; a well-curated Knowledge base with good titles and current content makes the recommendations sharp, while a stale base with vague titles makes them noisy. The most common rollout failure is not the feature but the unwillingness to invest in Knowledge cleanup before turning it on.
Why article recommendations live and die on Knowledge hygiene
Where the feature lives in Setup and on the case
Enable Einstein Article Recommendations in Setup, Einstein Service, Article Recommendations. Toggle it on, pick the case record types it applies to, and the model becomes active. Add the Article Recommendations component to the Case record page in Lightning App Builder. The component renders as a list of suggested articles in the sidebar or in a tab, each with an attach action, an email action, and a copy-link action. Agents see the list the moment the case loads; new recommendations appear as the agent edits the case description or as new comments arrive. The component supports both Lightning Service Console and the standard Lightning record page.
How the recommendation model works
The model runs on a Salesforce-managed transformer that takes case text (subject, description, comments) and Knowledge article text (title, body, summary) and computes a similarity score for every accessible article. The top N highest-scoring articles are returned. Personalization is light; the same case gets similar recommendations across different agents, with minor variation for agent-specific access. The model retrains on Salesforce's schedule rather than per-org, so a new article appears in recommendations within hours of publishing. Older articles that no longer match modern phrasing slowly lose relevance until they fall out of the top results entirely.
The Knowledge hygiene that determines recommendation quality
Three Knowledge attributes drive recommendation accuracy. Title clarity: an article titled "Password Reset Procedure" beats one titled "ACT-2024-PR-final" in every model. Body density: articles with the actual answer in the first paragraph rank better than articles that bury the answer at the end. Data category alignment: articles tagged with the right categories surface in the right contexts. The biggest single improvement most teams can make is auditing the bottom 25 percent of Knowledge articles by view count, retiring ones that should not exist anymore, and rewriting titles on ones that should. The recommendation model is bounded by what Knowledge contains.
Attach, email, and insert actions
Each recommended article comes with three actions. Attach links the article to the case for case history and reporting. Email drops the article body into a draft email to the contact. Insert pastes the article text directly into the agent reply (Chatter or email). The action choice depends on workflow. Service teams that resolve via email favor Email. Teams that close cases with internal notes favor Attach. Teams that use the Service Console reply pane favor Insert. The actions all write events to the AgentWork object so reporting can split recommendation acceptance by action type. Different action mixes correlate with different agent productivity patterns.
Acceptance rate and the Knowledge feedback loop
Every recommendation surfaces with an Accept (used) or Ignore (skipped) signal. Acceptance rate is the headline metric. Production deployments typically hit 30 to 50 percent acceptance on well-curated Knowledge bases and 10 to 20 percent on stale ones. The acceptance signal feeds back into the model on Salesforce's retraining cycle, so articles that agents consistently accept rise in relevance for similar cases. Articles that agents consistently ignore fall in relevance. Without acceptance signal, the model has no feedback loop to improve. Encouraging agents to accept (even if they only reference the article without sending it) produces a meaningfully better recommendation engine over weeks.
Permissions, access, and the empty-list problem
The agent only sees article recommendations from articles their permissions allow. A case agent without access to a specific data category cannot see articles in that category, even when Einstein scores them highly. The most common ticket admins get is "my recommendations are empty" which is almost always one of three things: the case record type is not enabled for Article Recommendations, the agent lacks Read on Knowledge, or the Knowledge base has no articles in the data categories the case maps to. Walk through those three checks before investigating model behavior.
Reporting and proving the ROI
The Einstein for Service Insights dashboard surfaces three reports: recommendations served per agent per day, acceptance rate per article, and average handle time reduction. The handle time number is the headline ROI metric. Most production deployments cut average handle time by 5 to 15 percent on case types where Knowledge is well-curated. The acceptance rate per article number is the diagnostic metric; articles with high serve rate and low acceptance are usually titled or written wrong. Pulling that report monthly and fixing the bottom 10 articles is the discipline that compounds value.
How to roll out Article Recommendations and earn the conversion lift
The feature ships in minutes. The Knowledge audit that makes the recommendations useful takes one or two days. Skipping the audit is the rollout failure pattern. The teams that ship the audit first hit 30 to 50 percent acceptance in week one and never look back; the teams that skip it hit 15 percent and quietly stop using the feature.
- Audit Knowledge before turning the feature on
Pull all Knowledge articles by view count. Archive articles older than 18 months unless they are timeless. Rewrite titles on the top 50 most-viewed articles to be plain-language descriptions of the question they answer, not internal codes.
- Enable Einstein Article Recommendations
Setup, Einstein Service, Article Recommendations. Toggle on. Pick the case record types it applies to. Service Cloud edition with Einstein is required.
- Add the component to the case record page
Open Lightning App Builder, edit the Case Record Page. Drag the Article Recommendations component into the sidebar. Save and activate.
- Verify agent access to Knowledge
Agents need Read on Knowledge and access to the data categories the case maps to. Without both, the recommendations list renders empty even when articles match.
- Pilot with one team for two weeks
Pick five to ten agents. Watch acceptance rate daily. Pull samples of accepted and ignored recommendations to spot Knowledge issues that affect quality.
- Train agents to accept even when they only reference the article
The acceptance signal feeds back into the model. An agent who reads an article but does not formally accept it gives the model no signal. Brief them on this loop in the rollout meeting.
- Schedule the monthly Einstein for Service Insights review
Pull the acceptance rate per article report monthly. Rewrite or retire the bottom 10 articles by acceptance rate. The cadence is what compounds value.
Which case record types Article Recommendations applies to. Default is all; can be restricted to specific record types during pilot.
How many recommended articles to show. Default 5; tune to placement space available on the case page.
Which actions (Attach, Email, Insert) are exposed per recommendation. Default all three.
Which Knowledge categories are eligible for recommendations. Defaults to all accessible to the agent.
Sidebar, tab, or main column on the case record page. Sidebar is most common but the choice affects agent visibility.
- Stale Knowledge produces stale recommendations. The model cannot make a bad Knowledge base sharp; it can only return what is there.
- Empty recommendation lists almost always trace to permissions, record type, or empty categories rather than the model. Walk through those three before investigating model behavior.
- Acceptance rate is the feedback loop. Agents who reference articles without accepting starve the model of signal and the recommendations degrade over time.
- Article titles drive ranking more than agents expect. Renaming the top 50 most-viewed articles to clear plain-language titles often produces visible accuracy improvements within a week.
- The retraining cadence is on Salesforce's schedule. A new article appears in recommendations within hours; a rewritten title takes effect on the next retrain, which can be days.
Trust & references
Straight from the source - Salesforce's reference material on Einstein Article Recommendations.
- Einstein Article RecommendationsSalesforce Help
- Set Up Einstein for ServiceSalesforce Help
- Knowledge SetupSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Einstein Article Recommendations do?
Q2. Who benefits most from Article Recommendations?
Q3. What's a prerequisite for good recommendations?
Discussion
Loading discussion…