[object Object]

The Integration

Summer ‘26 embeds Agentforce into Sales Cloud views, not as a sidebar but as native workflow. Opportunity record pages, Account 360, Forecast views, and the Sales Console all surface agent capabilities in-context. The embed point is a new Lightning component, lightning-agentforce-inline, that admins can drop on any record page or app page through Lightning App Builder. Permission Set controls visibility per profile, so the rollout can stage by team.

What Reps See

Summarize recent activity on an opportunity without copy-pasting into a separate AI tab. Draft follow-up emails grounded in the actual deal context, with the option to send directly via the Activity composer. See next-best-action suggestions inline with deal details, ranked by an Atlas-driven priority score. Ask pipeline-review questions in the Forecast view (“which deals over $100k slipped two quarters in a row?”) and get a typed answer with clickable record drill-downs.

Inline surfaces (Summer '26):
  Opportunity record  - Activity summary, draft email, next-best-action
  Account 360         - Stakeholder map, recent news, whitespace analysis
  Forecast            - Slip risk, pipeline gap analysis, narrative summary
  Sales Console       - Per-tab agent context, multi-record summarization
  Mobile (SF1)        - Voice-driven activity capture and meeting prep

Why Integration Matters

Previous Agentforce required tab-switching. Users who liked AI adopted; users who didn’t skipped. Embedding makes AI part of the rep’s natural flow — adoption rises because the friction drops. Salesforce-disclosed beta data shows daily-active-user lift of 35–50% versus the prior sidebar-only model, with a corresponding lift in opportunity-update completeness scores.

Rollout Guidance

Don’t disable Agentforce in-context — the embed assumes it’s on, and disabling it leaves visible-but-broken UI affordances. Re-train reps briefly: what’s new, where it surfaces, how to invoke (most surfaces support both click and slash-command). Measure adoption via activity metrics post-rollout (drafts generated per rep per week, summary opens, suggestion accept rate); investigate low-adoption teams individually rather than averaging away the signal.

What to Configure Before Enabling

Set the Topic-to-page mapping so the right Topic loads in the right context (Account Topic on Account pages, Opportunity Topic on Opportunity pages). Configure refusal text in your brand voice — the default is functional but generic. Lock down which Actions are permitted from which page (a rep on a Forecast page should not be able to fire a Convert Lead action by accident).

Common Failure Modes

  • Enabling all surfaces at once for all reps. Stage by team and surface so support load is manageable.
  • Skipping the Topic mapping and letting the agent guess context — answer quality drops noticeably.
  • Forgetting that the inline surfaces consume Agentforce platform capacity and budget. Set per-rep daily call quotas in Command Center to prevent runaway spend.
  • Not piping the inline interactions into Command Center traces. The bottom 10% of inline interactions are the ones you need to see.

What to Do This Week

In a sandbox, drop lightning-agentforce-inline on the Opportunity record page, configure the Opportunity Topic, and have three reps run through their normal day with it. Capture friction points before promoting to production.

[object Object]
Share