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.
- 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.
- 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.
- 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.
- 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.
- 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.
Permission-set-based. Grant Einstein Copilot user permission to profiles that need it. Start with a pilot group; expand gradually.
Pre-configured for Sales Cloud and Service Cloud. Summarize Account, Draft Email, Create Task, Suggest Next Steps. Customize but do not break.
Org-specific business areas. Add to the standard Copilot agent in Studio with flow or Apex actions.
Atlas Reasoning Engine by default. Configurable to GPT or other supported models via Model Builder.
- 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.