Creating a Quarterly Business Review deck for a customer success team often requires pulling data from multiple sources, summarizing account health, and presenting renewal risks. Manually assembling this slide deck can take hours of copying data from CRM, support tickets, and usage analytics. Copilot in Microsoft 365 can automate most of this work if you write structured prompts that tell it exactly what data to retrieve and how to format each slide. This article explains how to build effective prompts that produce consistent, data-backed QBR decks without the manual overhead.
Key Takeaways: Writing Copilot Prompts for QBR Decks
- Copilot pane in PowerPoint > Prompt box: Use structured commands with bullet-style instructions to generate slide content from Microsoft Graph data.
- Data source references like “from Dynamics 365” or “from Salesforce”: Specify the exact CRM or analytics source Copilot should query for account metrics.
- Slide-by-slide prompt pattern: Break the deck into sections and write one prompt per slide to avoid data mixing or formatting errors.
Understanding How Copilot Generates QBR Content
Copilot in PowerPoint can read from Microsoft Graph, which includes data stored in Dynamics 365, Salesforce via connectors, Microsoft 365 usage logs, and SharePoint documents. When you prompt Copilot to build a QBR deck, it interprets your request and pulls structured fields like account name, renewal date, support ticket count, and product usage metrics. The quality of the output depends directly on how clearly you specify the data source, the time frame, and the slide layout.
Copilot does not have a pre-built QBR template. You must guide it by describing each slide’s purpose and the metrics it should display. If you write a vague prompt such as “Create a QBR deck for Contoso,” Copilot may generate generic slides with placeholder data. A precise prompt that names the CRM system, the quarter, and the specific KPIs yields usable slides that require only minor formatting adjustments.
Prerequisites for Using Copilot in PowerPoint
Before writing prompts, confirm the following requirements are in place:
- You have a Copilot for Microsoft 365 license assigned to your account.
- Your organization has enabled the Microsoft Graph data connectors for your CRM system, such as Dynamics 365 or Salesforce.
- You are using the latest version of PowerPoint for Windows or Mac, or PowerPoint for the web.
- The customer account data you want to reference is stored in a supported Microsoft Graph source.
Steps to Write Effective Prompts for a QBR Deck
- Open PowerPoint and launch the Copilot pane
Click the Copilot icon on the ribbon or press Alt+I to open the Copilot pane. This is where you enter all prompts. Start with a blank presentation or a company-branded template. - Write a deck-level prompt to set the context
In the Copilot pane, type: “Create a new presentation for the QBR of customer Contoso. Use data from Dynamics 365 for the last quarter. Include slides for executive summary, account health, product usage, support performance, and renewal risk.” This prompt tells Copilot the customer name, the data source, the time frame, and the slide structure. - Review the generated slide structure
Copilot will produce a set of slides with headings and some placeholder text. Do not expect perfect data on the first attempt. Check each slide to confirm the metrics are from the correct quarter and account. - Refine the executive summary slide with a specific prompt
Select the executive summary slide and type in the Copilot pane: “Update this slide to show the overall account health score, the number of active users, total support tickets opened this quarter, and the renewal probability percentage. Use data from Dynamics 365.” Copilot will replace the placeholder text with real numbers from your CRM. - Add a product usage slide with a targeted prompt
Insert a new slide and type: “Add a slide titled Product Usage. Show the top three products used by Contoso this quarter, the monthly active user count per product, and the month-over-month change. Source data from Microsoft 365 usage reports.” This pulls usage analytics from your tenant. - Generate a support performance slide using ticket data
Add another slide and prompt: “Create a slide called Support Performance. Include total tickets opened, average first response time, average resolution time, and ticket breakdown by severity. Get this data from Dynamics 365.” Copilot will fill in the metrics for the specified customer. - Create a renewal risk slide with a conditional prompt
Type: “Add a slide titled Renewal Risk. Show the renewal date, current contract value, any open escalations, and a risk rating of high, medium, or low based on support ticket volume and usage decline. Use Dynamics 365 data.” Copilot evaluates the data and assigns a risk rating. - Adjust formatting using slide-level prompts
If a table or chart looks misaligned, select the slide and type: “Reformat this slide to use a two-column layout with the table on the left and a callout box on the right. Keep the font consistent with the company template.” Copilot will restructure the layout. - Add a notes section for the presenter
Select each slide and type: “Add speaker notes to this slide that explain the key takeaway for each metric. Mention the quarter-over-quarter trend.” This prepares the presenter for the review meeting. - Run a final consistency check across all slides
Type in the Copilot pane: “Review the entire deck and flag any slide that has missing data, mismatched quarter references, or metrics that are not from the Contoso account.” Copilot will list slides that need attention.
Common Prompt Mistakes and How to Avoid Them
Copilot returns data from the wrong customer
If you do not specify the customer name in every prompt, Copilot may pull aggregated data from your entire tenant. Always include the customer account name in each prompt, especially when you add new slides. For example, write “for Contoso” at the end of every slide-specific command.
Copilot generates placeholder text instead of real data
This happens when Copilot cannot find the data source you referenced. Verify that your CRM connector is enabled in the Microsoft 365 admin center and that the customer account exists in that system. If the data is stored in a SharePoint list, reference that list by name in the prompt.
Metrics are from the wrong time period
Copilot defaults to the current month if you do not specify a quarter or date range. Always include the exact time frame in your prompt, such as “Q3 2025” or “the period from July 1, 2025 to September 30, 2025.”
Copilot mixes data from multiple customers on one slide
If you work on a deck that covers multiple customers, use separate prompts for each customer slide. Do not ask Copilot to “add data for all customers” on a single slide — it will merge fields incorrectly. Instead, create one slide per customer and prompt each slide individually.
Copilot Prompt Patterns for QBR Slides: Slide vs Deck Level
| Prompt Level | When to Use | Example Prompt |
|---|---|---|
| Deck-level prompt | First prompt when creating a new presentation | “Create a QBR deck for Contoso using Dynamics 365 data from Q3 2025. Include executive summary, usage, support, and renewal slides” |
| Slide-level prompt | When you need to update or add one specific slide | “Update this slide to show the account health score, active users, and renewal probability for Contoso from Dynamics 365” |
| Formatting prompt | After content is generated, to adjust layout or style | “Reformat this slide to a single-column layout with a bold header and a bullet list below it” |
Using the correct prompt level for each task reduces errors and speeds up the deck creation process. Deck-level prompts set the overall structure. Slide-level prompts fill in the correct data for each section. Formatting prompts polish the visual output without affecting the data.
Conclusion
You can now write Copilot prompts that generate a complete, data-driven QBR deck for customer success reviews. Start each prompt with the customer name, the data source, and the time period to ensure accurate results. Use slide-level prompts to refine individual sections and formatting prompts to align the deck with your company template. For advanced control, try using the “Copilot > Create from file” option to base the deck on a previous QBR document stored in SharePoint. This approach reduces manual data entry and lets you focus on the strategic narrative during the review meeting.