The honest rollout sequence is: license, pilot one topic with one team, observe, expand. Skipping the pilot phase produces the same outcome every time, which is a SKU that gets turned off in month two when the executive sponsor moves teams.
- Confirm prerequisite licenses and data hygiene
Agentforce for Sales needs Sales Cloud Enterprise or Unlimited, the Agentforce add-on SKU, and a clean activity data source (Einstein Activity Capture is ideal). Without activity data, the Sales Coach has nothing to evaluate.
- Enable Agentforce in Setup
Setup, Einstein, Agentforce, Enable. Accept the legal terms. Provision the SDR Agent and Sales Coach from the agent gallery. Both agents land in Agent Builder as editable copies of the shipped templates.
- Pilot with one team and one topic
Pick five to ten reps and one topic, usually Account Research or Meeting Scheduling. Limit access via permission sets so the rest of the org does not see the agent until the pilot finishes.
- Customize the Email Drafting prompt template for your voice
The shipped template is generic. Add three to five lines that describe brand voice, common product hooks, and the desired closing CTA. Test against ten real prospects in the pilot team's pipeline.
- Wire the Sales Coach signals to a Chatter feed item, not just the panel
Most reps live in their email and pipeline view, not the Agentforce panel. A Chatter post on the opportunity makes the coaching visible where reps already work.
- Review the Plan Trace and Testing Center weekly for two weeks
Look for topic misfires, irrelevant suggestions, and template regressions. Adjust topic classification descriptions before adding more actions.
- Expand topic by topic, not team by team
Once one topic works well, roll it to the next team before turning on a second topic. The combinatorial debugging of two new topics on two new teams is what kills most rollouts.
Which of the two shipped agents (SDR, Sales Coach) are enabled. Most teams roll out one at a time.
Permission-set-gated access to the agent. Critical during rollout so the rest of the org does not surface unvetted output.
The customized prompt that encodes brand voice and product positioning. Highest-leverage customization in the SKU.
Per-signal sensitivity for the coach. Allows enterprise vs transactional deals to have different thresholds.
Where Sales Coach suggestions surface: Agentforce panel, Chatter feed, or both. Chatter usually wins on adoption.
- Sales Coach without Einstein Activity Capture or a similar activity sync is mostly silent. Reps' manually logged activity is too sparse for the signal model.
- The Email Drafting topic without customization produces generic email. Reps reject it after two days and turn the agent off in their head.
- Conversation pricing surprises orgs that did not estimate volume. A 200-rep team querying the agent five times a day produces 25,000 conversations a month.
- Custom Sales Cloud fields are not visible to the shipped actions. The agent will not see your custom Account.AccountTier field unless you extend the action.
- Field-level security and sharing rules apply. The agent only sees data the calling user can see, so a manager asking about their team sees more than an individual rep on the same query.