Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryEEinstein Copilot
AIIntermediate

Einstein Copilot

Einstein Copilot is Salesforce's generative AI assistant embedded directly inside Sales Cloud, Service Cloud, and other Salesforce apps.

§ 01

Definition

Einstein Copilot is Salesforce's generative AI assistant embedded directly inside Sales Cloud, Service Cloud, and other Salesforce apps. Users open the Copilot panel from the global header, ask questions in natural language ("summarize my open opportunities," "draft a follow-up email to this contact," "what are the open cases for this account"), and Einstein Copilot answers grounded on the user's Salesforce data, calls Salesforce actions when needed, and respects the user's record-level access throughout. Copilot is the in-app AI assistant; Agentforce Agents are the autonomous customer-facing or process-driving agents that run independently.

Einstein Copilot was launched in 2024 as the initial generative AI assistant brand. As Salesforce evolved the product, the messaging and architecture converged with Agentforce; Einstein Copilot is increasingly described as an internal-user agent built on the Agentforce platform with Sales Cloud and Service Cloud standard topics pre-configured. The distinction between Copilot and a generic Agentforce Agent is shrinking; expect the brand to continue evolving as Salesforce consolidates the AI assistant story.

§ 02

What Einstein Copilot does, how it grounds answers, and how it relates to Agentforce

The Copilot panel and where it appears

Einstein Copilot is accessed via a panel that opens from the global header in Lightning Experience. The panel slides over the page; users type natural-language questions and the Copilot responds. Copilot is also available in mobile Salesforce apps and in some Slack contexts. The panel respects the current page context: opening Copilot on an Account page lets the user ask "what is recent activity on this account" without explicitly naming the record.

Grounding on Salesforce data

Copilot grounds every response on the user''s actual Salesforce data, not on the LLM''s training knowledge. When a user asks about a specific Account, Copilot queries the Account, related Opportunities, Cases, Contacts, and recent activity via Salesforce APIs, builds a context, and instructs the LLM to answer based on that context. The grounding is automatic; users do not configure data sources. Salesforce''s sharing model still applies; Copilot can only see records the asking user has access to.

Standard topics and actions

Einstein Copilot ships with pre-configured topics covering common Sales Cloud and Service Cloud tasks: Summarize Account, Draft Email, Create Task, Generate Knowledge Article from Case, Suggest Next Steps. Each topic carries instructions and standard actions. Admins can customize the standard topics, add custom topics, and attach custom actions backed by flows or Apex. The customization model is identical to Agentforce Agent configuration; Copilot is technically an Agentforce Agent with Sales/Service preset content.

The Einstein Trust Layer

Every Copilot interaction routes through the Einstein Trust Layer, which masks sensitive data before sending prompts to the LLM, applies toxicity detection on responses, audits every interaction, and enforces zero data retention with external model providers. Sales Cloud customers who would never paste customer data into ChatGPT can use Einstein Copilot precisely because the Trust Layer mediates the LLM interaction. The Trust Layer is what makes generative AI in Salesforce viable for enterprise customers.

Copilot versus Agentforce Agents

Originally distinct products; converging now. Einstein Copilot was the in-app AI assistant for Salesforce internal users (sales rep summarizing an account, service agent drafting a response). Agentforce Agents were the autonomous customer-facing AI workers. As of 2025, Salesforce consolidates: Copilot is essentially an Agentforce Agent with Sales/Service standard topics, deployed to the in-app Copilot panel as a channel. New Copilot-style features increasingly ship through the Agentforce platform.

Customizing Copilot for your org

Through Setup, Agentforce Studio (or the original Copilot Builder for older deployments), admins customize the standard Copilot agent: add custom topics for org-specific business areas, attach custom Actions backed by flows or Apex, override standard prompt templates with org-specific tone and language, configure which user profiles have Copilot access. Customization makes Copilot useful for industry-specific workflows the standard topics do not cover.

Licensing and rollout

Einstein Copilot is sold via the Agentforce license tiers. Sales Cloud and Service Cloud editions can bundle Copilot at certain tiers; others require an add-on. Per-user licensing is the typical model. Customer pricing has shifted multiple times as Salesforce iterates the bundle; check the current Salesforce pricing page rather than assuming legacy bundle details. Rollout typically starts with a pilot group of high-engagement users before expanding org-wide.

§ 03

Enabling and customizing Einstein Copilot for an org

Copilot setup runs in three phases: enable the feature, configure profile access, customize the standard agent if needed. Most orgs start with standard topics and add customization after measuring adoption.

  1. Verify the license and enable Copilot

    Setup, Quick Find, Einstein Copilot (or Agentforce Studio in newer orgs). Confirm the org''s license includes Copilot. Toggle Enable Einstein Copilot. The Copilot panel becomes available in the global header for users with permission.

  2. Grant Copilot access via permission set

    Assign the Einstein Copilot user permission set to the user profiles that should have access. Without this, users cannot open the panel even if the feature is enabled. Start with a pilot group; expand gradually.

  3. Review standard topics and actions

    Inside Agentforce Studio, open the Einstein Copilot agent. Review the pre-configured topics: Summarize Account, Draft Email, Create Task. Understand what each topic does before customizing; some customers customize too aggressively and break standard behaviour.

  4. Add custom topics or actions

    For org-specific use cases (insurance policy lookup, manufacturing asset status), add custom topics with custom actions backed by flows or Apex. Match the topic naming and action design conventions used in the standard topics for consistency.

  5. Monitor adoption and iterate

    Use the Agentforce Studio monitoring dashboard to track Copilot usage: conversations per user, top topics, escalation rates. Iterate on standard topic customization, custom topic additions, and rollout to additional user profiles based on observed value.

Key options
Access controlremember

Permission-set-based. Grant Einstein Copilot user permission to profiles that need it. Start with a pilot group; expand gradually.

Standard topicsremember

Pre-configured for Sales Cloud and Service Cloud. Summarize Account, Draft Email, Create Task, Suggest Next Steps. Customize but do not break.

Custom topicsremember

Org-specific business areas. Add to the standard Copilot agent in Studio with flow or Apex actions.

Underlying LLMremember

Atlas Reasoning Engine by default. Configurable to GPT or other supported models via Model Builder.

Gotchas
  • Copilot grounds on user record access. Two users asking the same question can get different answers because their record visibility differs.
  • The Einstein Trust Layer is mandatory; you cannot disable masking or audit. Compliance teams should still review the data classification for sensitive fields.
  • Standard topics are good defaults; over-customizing them can degrade behaviour. Add custom topics for new use cases rather than rewriting standard ones.
  • Copilot and Agentforce Agents share infrastructure but have different brand positioning. The technical line between them keeps shifting; track current Salesforce documentation.
  • Licensing has shifted multiple times. Confirm the current bundle and add-on requirements before promising rollout timelines.
§

Trust & references

This term has been renamed to Agentforce.

View current page
Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Einstein Copilot.

Keep learning

Hands-on resources to go deeper on Einstein Copilot.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

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 is Einstein Copilot?

Q2. What's the Einstein Trust Layer?

Q3. What does Copilot enable users to do?

§

Discussion

Loading…

Loading discussion…