Customer Surveys and Voice of Customer Reporting by Quarter-End With No New Tools

Check entitlement before you build anything. Dynamics 365 Customer Voice is a separate product with its own response limits, and Microsoft has announced its retirement, so confirm in current Microsoft documentation what your licences include and for how long. If Customer Voice is available, send surveys from it and map its responses to a shared question list. If it is not, Microsoft Forms plus a Power Automate flow writing to a response table you control produces a defensible quarterly report with tools most Microsoft 365 tenants already have. For five teams running different surveys, define one response schema, keep a question mapping table per team, and give leadership a single Power BI or Excel view.

The situation this guide is written for is common: leadership wants a voice of customer number by quarter-end, five teams already ask customers for feedback in five different ways, there is no budget for a survey platform and no IT project slot. None of that needs a new product. It needs one decision about the collection route, one agreed data shape and a report that shows its working.

Which survey tools are you actually entitled to use?

Start with what you already own, and write the answer down, because it decides the route.

• Dynamics 365 Customer Voice is licensed separately. Some Dynamics 365 licences have historically included a limited allowance of Customer Voice survey responses, and additional capacity was sold as an add-on. Microsoft has announced the retirement of Customer Voice, with survey capability moving to Dynamics 365 Customer Insights - Journeys and to Copilot Studio for conversational surveys. Check current Microsoft documentation for the allowance attached to your licences, the retirement dates and the recommended migration path before you rely on it for more than one quarter.
• Microsoft Forms is included in most Microsoft 365 business and enterprise plans. Confirm it is enabled in your tenant and whether external respondents are allowed to answer.
• Power Automate for Microsoft 365 is included in the same plans for standard connectors. The Microsoft Forms connector is standard. The Dataverse connector is premium when used outside the context of a licensed Dynamics 365 or Power Apps application, so check how the flow owner is licensed before you design around Dataverse. Premium connector rules and the designs that look compliant but are not are covered on our Power Automate consulting page, and we will not repeat them here.
• Power BI sharing normally needs a Power BI licence for the author and the readers, or content hosted in a capacity that allows free viewers. If that is not in place, Excel is a perfectly good leadership view for a quarterly report.

If the honest answer is that Customer Voice is not available or not worth adopting for a product being retired, use the Forms route. If your organisation has no Dataverse at all, the same schema works in SharePoint lists or a single Excel workbook for one quarter, with the understanding that it will need a proper home before the volume or the audience grows.

How does the Customer Voice route get responses into Dataverse?

Customer Voice already stores its data in Dataverse, so the work is mapping, not moving. Surveys, invitations, survey responses and individual question responses are held in Customer Voice tables in the environment where the project was created. Check current Microsoft documentation for the table names and relationships in your version.

1. Confirm which environment each team created its Customer Voice projects in. Teams working in different environments produce responses that cannot be joined without an export.
2. Use survey variables or invitations to carry the context you need, such as the case, account or team, so each response can be linked to a record rather than only to an email address.
3. Add a canonical question lookup for each Customer Voice question through the mapping table described below, rather than renaming or rewriting surveys mid-quarter.
4. Populate your shared response table from the Customer Voice response tables with a scheduled flow or a Dataverse view feeding the report, keeping the Customer Voice response identifier on every row.
5. Because the product is being retired, export the historical surveys and responses you need into tables you own now, so the next quarter does not depend on a product timeline you do not control.

Where surveys are triggered by case closure in Dynamics 365 Customer Service, the case process itself is covered by our Dynamics 365 Customer Service implementation work. If the numbers will be used to judge teams or individuals, read building a CSAT programme that cannot be gamed before you choose who sends surveys and who can edit responses.

How does the Microsoft Forms and Power Automate route work?

One flow per form writes every submission into a response table you own. The survey tool becomes replaceable, and the data stays put.

1. Keep each team's existing form if it works, or create one per team. Store forms in a group or shared ownership rather than in one person's account, so a leaver does not take the survey with them.
2. Create a flow for each form with the Microsoft Forms trigger for a new response and the action that gets the response details.
3. Write one header row per submission: source form identifier, Forms response identifier, submitted date and time in UTC, team, respondent email where the form collects it, and any case or order reference the form asked for.
4. Write one answer row per question: the header, the source question identifier, the raw answer text and, for rating questions, the raw number.
5. Use the combination of form identifier and response identifier as an alternate key or duplicate check, so a flow that retries cannot count the same response twice.
6. Add error handling that records failed runs somewhere a named person reviews, and run the flow on shared service account connections rather than personal ones (check current Microsoft documentation for which connectors support service principal authentication).
7. Backfill responses submitted before the flow existed from each form's Excel export, loaded into the same tables with the same identifiers.

Anonymous forms cannot be linked to a customer record, and that is acceptable for a sentiment measure. Decide it deliberately per team and record it in the survey table, because it changes what the report can say. Recovering flows that break when their owner leaves, connection references and moving flows between environments are all covered on the Power Automate consulting page.

What response schema lets five teams report as one?

A small set of tables that separates what was asked from what it means. Five tables are enough:

• Survey: team, source tool (Customer Voice, Forms or other), source identifier, audience, whether it is anonymous, scale used, and effective from and to dates.
• Response: survey, source response identifier, submitted date and time, respondent or linked record where known, and channel.
• Answer: response, source question identifier, raw value as text, raw number where there is one, and the canonical question it maps to.
• Canonical question: the shared questions leadership reports on, for example overall satisfaction, likelihood to recommend, effort to resolve and one free-text theme, each with its reporting scale.
• Question mapping: team survey, source question identifier and wording, canonical question, conversion rule, who approved it and the effective date.

Keep the raw answers forever and derive everything else. When a conversion rule changes, you recalculate; you never overwrite what the customer said.

How do you map each team's different questions without rewriting their surveys?

Map only what genuinely means the same thing, and leave the rest team-specific.

• One row in the mapping table per team question that feeds a canonical question. A question such as "How satisfied were you with our support?" and "How happy are you with the service you received?" can reasonably map to overall satisfaction. "Would you buy from us again?" should not.
• Record the conversion rule for scales explicitly. A 1 to 5 rating and a 0 to 10 rating do not become the same measure because you rescaled them. Report each scale in its own terms, or agree a documented banding such as satisfied, neutral and dissatisfied that each team lead signs off, and show which teams sit on which scale.
• Leave unmapped questions in the data. They still appear in team-level views, just not in the shared score.
• Version the mapping with effective dates. If a team changes its question in the middle of a quarter, that is a new mapping row, not an edit to the old one.
• Ask each team lead to approve their own mapping before quarter-end, not after the numbers are visible.

This turns five inconsistent processes into one report without asking any team to change how it surveys this quarter. Harmonising the surveys themselves can wait for the next one.

What makes a quarterly voice of customer report defensible?

A reader who doubts a number can follow it back to responses, and the calculation did not change after the results were known.

• Define the quarter by submission date in one stated time zone.
• Take a quarter-end snapshot of responses and mappings, and report from the snapshot so late edits or backfills do not move a published figure.
• Show the response count beside every score, per team and in total, and state a minimum count below which a figure is shown as insufficient responses.
• Reconcile counts: responses in each source tool against rows in the response table for the same period, with any difference explained.
• Write the calculation down once, including the mapping version, the banding rules and exclusions such as internal or test responses.
• Keep free-text themes separate from scores, and say how they were grouped.
• Do not hand-edit the leadership spreadsheet. If a number is wrong, fix the data or the rule and refresh.

The same discipline of reconciliation and a documented calculation appears in our guide to trusted reporting that is audit-ready fast, and where survey data needs to be joined with figures from other systems, consolidating reporting across several systems covers that wider problem.

Should the leadership view be Power BI or Excel?

Whichever your leadership already opens, built on the same tables either way.

• Power BI suits a recurring view with filters by team, channel and period, drill-through to comments and a published refresh. It connects to Dataverse directly. Check licensing for the people who will read it before promising it.
• Excel suits a single quarterly pack. Use Power Query against the Dataverse or SharePoint tables, or an export of the snapshot, so the workbook refreshes rather than being retyped.
• Either way, lead with one page: the canonical questions, score and response count per team, the change from the previous quarter where one exists, and a short list of the free-text themes with counts.

What can realistically be done before quarter-end?

The route decision, the schema, the flows and a first report are a short piece of work when the scope stays this narrow. A sensible order:

1. Confirm entitlement and choose the collection route for each team.
2. Create the five tables and agree the canonical question list with leadership.
3. Build and test the flows or the Customer Voice mapping, then backfill the quarter.
4. Complete the mapping table with each team lead and get sign-off.
5. Build the report, reconcile counts, take the snapshot and publish.
6. Hand over a one-page runbook: who owns each flow, how to add a team or a question, and how to take next quarter's snapshot.

What does not fit before quarter-end is harmonising every team's survey, migrating off Customer Voice for good or building a full customer feedback programme. Put those in the plan for the following quarter.

When is a custom build the better answer?

When surveys are only one part of a wider customer platform decision, for example when per-user Microsoft licensing does not fit the number of people who need to see or act on feedback. The same schema and mapping approach works in a custom CRM built on React, Node.js, PostgreSQL or .NET, with survey collection handled by your own forms. We recommend the right solution for each organisation, and for a quarter-end deadline that is almost always the tools already in the tenant.

How does Solzet help with survey reporting on a deadline?

As a short delivery-and-handover engagement. Our senior consultants confirm the entitlement position with you against current Microsoft documentation, choose the route per team, build the response schema, flows or Customer Voice mapping and the Power BI or Excel view, reconcile the first quarter and hand over the runbook so your team runs the next one without us. Where the underlying case or service process needs work, that sits within our Dynamics 365 Customer Service delivery. Our senior consultants and full-stack developers bring 8+ years of Dynamics 365 Customer Engagement, Power Platform and custom CRM delivery, working remotely from Yerevan, Armenia, directly or white-label for Microsoft partners.