Customer Voice surveys in Dynamics 365

Dynamics 365 Customer Voice is Microsoft's customer-feedback platform. It collects survey responses, runs sentiment analysis, and feeds the data back into Dynamics 365 records — opportunities, cases, work orders, accounts — so the rest of the business can act on what customers actually say. For organisations that run NPS, CSAT, or post-interaction surveys, Customer Voice is the natural choice when the data should land in CRM.

Building a survey

Customer Voice surveys are built in a drag-and-drop designer with question types: short text, long text, choice (single or multi), Likert / rating, NPS, ranking, date, file upload. Conditional branching lets a survey adapt to earlier answers — a low rating triggers a follow-up reason question, while a high rating skips straight to a thank-you screen.

Survey themes and branding

Custom themes, logos, fonts, and colours match the survey to the company's brand. Multi-language surveys present the same survey in multiple languages, with translations stored alongside the original.

Distribution channels.

• Email — sent via Customer Voice's own mail or via Power Automate to Microsoft 365 mailboxes.
• Embedded link — generated for inclusion in any external email, web page, SMS, or QR code.
• In-product / portal embedding — embed the survey inside a Dynamics 365 form, a Power Pages portal, or any iframe-friendly host.
• SMS — through Azure Communication Services or partner SMS gateways triggered by Power Automate.
• Teams — bot-driven surveys delivered as adaptive cards in Teams chats.
• Power Automate flow — flows triggered by Dataverse events fire the survey at the right moment (case resolved, opportunity won, work order completed).

Triggering

Best-practice surveys are event-triggered rather than periodic. Case resolved → send CSAT survey one hour later. Opportunity closed-won → send relationship survey two weeks later. Work order completed → send satisfaction survey same day. Power Automate flows orchestrate the timing and conditions.

Response handling

Each survey response creates a survey response record in Dataverse, linked to the originating record (case, opportunity, etc.) and to the contact. Responses include:

• The structured answers.
• Computed scores (overall, by category).
• Sentiment analysis on free-text answers.
• Time-to-respond and completion percentage.

Actions from responses

Power Automate flows trigger on survey responses to:

• Create a follow-up case if a customer gave a low rating.
• Notify an account manager if a key customer scored below threshold.
• Update the contact's NPS score on their record.
• Aggregate scores into dashboards for executive review.

Analytics

Built-in dashboards show response rate, score distribution, sentiment trend, and breakdown by survey, segment, or time period. Power BI templates extend the analytics with cross-system slicing (e.g. CSAT by product line, by region, by support agent).

Anonymous vs identified

Surveys can be anonymous (no contact linkage, no follow-up) or identified (linked to contact, follow-up enabled). The right choice depends on regulatory and trust considerations.

Practical use cases.

• Post-case CSAT.
• Quarterly NPS.
• Post-purchase customer experience.
• Internal employee surveys (Customer Voice does this too).
• Event feedback.
• Win-loss analysis after closed opportunities.

Licensing

Customer Voice is sold per response volume — survey responses per month, with capacity tiers. Bundled with some Dynamics 365 SKUs.

When Customer Voice is the right tool — and when it isn't

Customer Voice's strongest fit is transactional feedback that must land in Dataverse. If a low CSAT should reopen a Case, or a promoter score should update a Contact so Sales can spot expansion opportunities, the native write-back is what you're paying for. Nothing else in Microsoft's estate does this without a middle-ware layer.

Where it is a weak fit:

• Long research questionnaires — 30-question studies with logic branching Customer Voice supports on paper but that authors find easier in Qualtrics or SurveyMonkey. The dedicated tools have deeper analytics and a much older reporting UI muscle memory.
• Anonymous public forms — a Microsoft Forms survey is simpler, faster, and does not consume Customer Voice response capacity.
• Continuous relationship NPS at scale — the response-based pricing works against you once you're firing tens of thousands of surveys a month. Compare the run-rate against Medallia or Delighted before signing up.

Response caps and what they actually mean

The pricing unit is survey responses per month, pooled across the tenant. A response is a completed submission — half-completed ones do not count against the cap in the current metering. Every Dynamics 365 SKU includes a modest allowance; larger allowances are bought as add-ons.

Two failure modes:

1. Silent throttling. Hit the cap and new survey invitations continue to send but responses are dropped or queued depending on tenant configuration. The Customer Voice admin centre shows current-period usage; wire an alert to it if you are near the ceiling.
2. Ghost invitations. A retention flow that resends surveys to non-responders can double or triple counted volume with no obvious business benefit. Cap the resend loop.

Integration patterns worth stealing

• Case closure trigger — Power Automate on Dataverse (msdyn_incident Status change to Resolved) waits one hour, then sends a two-question CSAT (rating + free text). Response comes back, sentiment on the free text is negative → new Task assigned to the case owner's manager. This is the canonical worked example and the one Microsoft's own docs anchor around.
• Won-opportunity relationship survey — trigger on Opportunity StatusCode = Won, delay two weeks, send five-question relationship survey to primary contact + additional contacts on the account. Aggregate rolls up to Account.
• Field-service satisfaction — Field Service work order completion posts a survey to the customer's mobile via SMS (Azure Communication Services). Response links back to the work order and the technician.
• Employee pulse — a monthly one-question pulse to the sales team, delivered as a Teams adaptive card. Response aggregates into a Power BI dashboard for the CRO.

Rollout checklist

• Confirm Customer Voice is available on the Dynamics 365 SKU already owned; if not, buy the response add-on before designing surveys.
• Design each survey as one question you actually want answered plus a free-text follow-up. Longer surveys destroy response rates.
• Wire the response-back-to-record path before go-live — a CSAT that lands in Dataverse but nothing acts on is worse than no survey at all.
• Set anonymous vs identified per-survey; do not default to anonymous "to be safe".
• Localise for every language the customer base uses; a mixed-language response is worse than a single-language one.
• Turn on the Customer Voice usage alert at 80% of the monthly response cap.
• Publish an internal SLA for how the team acts on low ratings — the tool measures nothing if the answer is filed and forgotten.

FAQ

Is Customer Voice the same as Microsoft Forms? No. Forms is a general-purpose survey tool tied to Microsoft 365. Customer Voice is Dynamics 365-native — responses become Dataverse records, and integration with Cases, Opportunities, and Work Orders is built in. Forms cannot do that natively.

Can Customer Voice send surveys via SMS? Yes, via Azure Communication Services or a third-party SMS gateway invoked from Power Automate. The out-of-the-box channels are email and Teams; SMS is orchestrated, not native.

Are survey responses counted toward Dataverse storage? Yes. Every survey response is a row in Dataverse and counts against database capacity. Very high-volume tenants should archive old responses on a retention schedule.

Can we brand the survey landing page with our own domain? Yes, custom themes and a vanity URL (via a redirect at your DNS) are supported. Fully white-labelled hosting is not — the survey renders on a Microsoft-controlled domain by default.

What happens if we exceed the response cap? Behaviour depends on tenant policy but the safe assumption is that responses beyond the cap are dropped. Monitor the usage graph and buy additional capacity before you cross the line.