Sales Extension Suite for Copilot Bill Whalen | Microsoft

How to prompt and review results

Ask like a seller, not a database administrator

Include the outcome, account or opportunity context, allowed evidence, and action boundary. You do not need a GUID. If several records fit, ask to see the likely matches and choose before deep retrieval. For a notes-only rehearsal, no record lookup should happen.

Example prompts

Browse all four example prompts below, or open just the one you need. These are starter examples, not the full workflow catalog. For an immediate fictional result, try the home-page examples.

Sales rep: prepare for a call
Use Sales Suite | Account & Deals. Help me prepare for a call about [customer and opportunity context]. Use only the CRM evidence I am authorized to read. If the opportunity is ambiguous, show likely matches and wait for my choice. Give me the bottom line, evidence dates, gaps, and one next best action. Read-only; no messages, assignments, or CRM changes.
Sales leader: review the pipeline
Use Sales Suite | Seller Workflows. Review [authorized team and time window] with pipeline-change-digest. Separate deal risk from missing data. Propose the three most useful coaching questions and one next action per deal, with sources. Do not change forecasts, infer performance from missing evidence, or search employee communications.
Account team: make a useful handoff
Use Sales Suite | Account & Deals. For [confirmed opportunity], propose a V-team handoff: minimum evidence, recipient role, precise question, and the decision needed to close the loop. Mark unconfirmed owners as proposed. Do not notify or assign anyone.
Notes-only rehearsal
Use Sales Suite | Seller Workflows, call-follow-up. Synthetic rehearsal only. Use only the notes below; do not query CRM, email, Teams, or other sources. Do not send, save, schedule, assign, or update anything. Return a concise recap, confirmed actions with owners and agreed dates, open decisions, one next best action, and proposed V-team handoffs. Keep reviewer identification, completion of the IT review, and the data-use decision separate. Report what actually ran.

Synthetic rehearsal only. Northstar Equipment is fictional.
Opportunity: Field Service Agent Pilot. Meeting date: October 15, 2026.
Jordan wants technicians to spend less time searching manuals and repair notes.
One equipment family was suggested, but none was selected.
Casey requires an IT data-access and security review before customer data is used.
Jordan will send three anonymized scenarios by October 20.
Bill will draft an outline after receiving them; no delivery date was agreed.
Casey will identify the security reviewer; no deadline was agreed.
Two weeks was suggested, not agreed. No budget, start date, success target,
purchase decision, data-use approval, or production deployment was agreed.
A follow-up meeting was discussed but not scheduled.

Review the answer before acting

  1. Right account? A likely opportunity is not a confirmed match. Synthetic notes must never become real customer evidence.
  2. Supported facts? Every important claim should have a source or be clearly labeled as a proposal or gap.
  3. Honest dates and owners? No agreed date means “not agreed.” Suggested owners are proposed, not assigned.
  4. One useful next action? It must respect your no-send/no-save boundary and show dependencies.
  5. Correct gates? Naming a security reviewer is not completing the review or approving data use. Do not assume anonymized scenarios are exempt.
  6. What really ran? Check tool activity and sources. Instructions loading is not proof of a successful provider call or external action.

If a tool is missing or denies access, report the gap; do not broaden the query, switch identities, or fabricate evidence.