[object Object]

A sales rep starts Monday with 47 open deals, 80 emails from the weekend, and a 9am pipeline call. The old workflow is half an hour of clicking, scrolling, and tab-switching to figure out what to talk about. The Wave 1 sales agent collapses that to a five-minute conversation that surfaces the deals at risk, the prospects who replied over the weekend, and the meetings that need prep. That is real time back if the rollout is configured right.

The Positioning

Wave 1 frames Sales Agent as where sellers start their day. Ask in natural language: “Which deals are at risk this week?” or “Draft a follow-up for the Acme meeting.” The agent pulls from CRM, Outlook, and Teams to answer. The conversational interface replaces the dashboard hunt; the rep asks for what they need rather than scrolling for it.

Common morning prompts:
- "What did I miss this weekend?"
- "Which deals slipped from forecast?"
- "Who needs a follow-up today?"
- "Prep me for my 10am with Contoso"
- "Draft a check-in for the deals stuck in negotiation"

The prompts become muscle memory after a week. Document the patterns that work for your team and share them.

Data Sources

The agent reads across Dynamics 365 Sales, Microsoft 365 email and calendar, Teams meeting recaps. Signals correlate — a deal that has not had rep outreach in 10 days plus declining engagement flags for attention. The cross-source correlation is the unique value; a CRM-only summary cannot detect a stalled deal that the rep is still calling weekly.

Signal sources:
- CRM: stage, close date, last activity
- Outlook: thread depth, response time, sentiment
- Teams: meeting frequency, attendees, recap topics
- Sales Insights (if licensed): predictive scores, engagement

Configure the data scope per role. The agent honors the rep’s existing security; it cannot see deals the rep cannot see.

Mobile and In-Context

Mobile-first experiences — agent guidance in the field, not just at the desk. In-context experiences embed Sales Agent into Outlook, Teams, Dynamics forms. Rep does not switch apps to ask. The voice mode on mobile lets the rep get a briefing on the walk from the car to the customer office.

Surface coverage:
- Sales hub web app: full agent panel
- Outlook desktop and web: in compose pane
- Teams desktop and meetings: in side panel
- Dynamics mobile app: chat and voice
- Outlook mobile: reduced surface, save-to-CRM and brief

Test each surface with the actual users who will use it. Adoption breaks at the lowest-quality surface.

Rollout Strategy

Enable for a pilot sales team first. Measure: time-to-first-touch on new leads, response velocity, forecast accuracy. Expand based on measured lift; not every rep needs the full agent from day one. The metrics that move first are activity logging volume and email response time; forecast accuracy moves later because the rep has to act on the agent’s signal.

Pilot plan:
Week 1: enable, baseline metrics in place
Week 2: training and prompt patterns shared
Week 3-4: rep self-service usage
Week 5-6: measure lift, decide on expansion

Pick reps who already use CRM consistently. Reps who avoid CRM as a pattern are the wrong pilot population; they will not provide a clean adoption signal.

Capability Matrix

The Wave 1 admin controls let you scope agent capabilities per role. An SDR might get read on leads and write on lead qualification; an account executive gets read on the full account graph and write on opportunity notes and stage updates. Map the matrix during rollout.

agent_capabilities:
  AE:
    read: account, opportunity, contact, activity, case
    write: opportunity_notes, activity_complete, stage_change
    voice: enabled
  SDR:
    read: lead, contact
    write: lead_qualify, activity_complete
    voice: enabled

Without the explicit map, every rep gets every capability and the data scope question becomes hard to answer.

Coaching the Prompt Patterns

The agent works best when reps ask focused questions. Train the team on three or four prompt patterns: morning briefing, pre-meeting prep, end-of-day cleanup, weekly pipeline review. Reps who use these patterns consistently see the largest time savings; reps who use ad-hoc prompts see variable results.

Telemetry

Pipe agent usage to App Insights through the M365 admin telemetry feed. Track prompts per rep per day, time of day, and downstream actions. Use this to identify reps who are not using the agent (training opportunity) and reps who use it heavily but do not act (workflow problem).

What to do this week

Pick a pilot team of five to ten reps, define the capability matrix, and stand up the baseline metrics. Train on the four prompt patterns and meet weekly for the first month to share what works.

[object Object]
Share