Customer Surveys in Genesys Cloud: Designing Feedback Programs That Turn Post-Interaction Data Into CX Decisions

A customer survey is more than a form sent after a conversation. In Genesys Cloud, a useful feedback program depends on how forms, Architect flows, delivery policies and reporting work together. Those design choices affect who receives a survey, when it arrives, whether customers can complete it, and how teams turn responses into operational decisions.

For organizations building cloud communication solutions, the goal is a feedback loop that reflects real interactions and connects findings to practical improvements. The following guide explains the key configuration choices and their consequences.

1. The building blocks: forms, flows and policies

Genesys Cloud customer surveys invite customers to give feedback about a previous interaction. The first component is a survey form. Genesys documentation describes six question types, including Net Promoter Score (NPS). Forms can be tailored to different interaction types, such as a billing inquiry versus a technical support conversation.

Next comes the delivery path. For web surveys, an invite flow in Architect supports the invitation process, while a policy determines which eligible interactions receive surveys automatically. For voice surveys, a voice survey flow handles the questions after an inbound call. Organizations can also share direct, one-time-use web survey links during messaging conversations.

These options serve different needs. A web policy automates invitations based on interaction criteria. A voice flow keeps feedback within the call experience. A direct link can support a more immediate, agent-guided invitation in messaging.

Genesys documents the customer survey form and voice survey flow process separately. Treat the form and delivery method as connected design decisions: a question that works well on a web page may not translate cleanly to spoken prompts.

Actionable takeaway: Choose the feedback channel and interaction purpose first, then build a form and flow suited to that experience.

2. Web survey policies: automation with guardrails

Web survey policies automate invitations, but they require setup and careful targeting. Genesys places them under Policies > Conversation Intelligence > Recording and Policies > Policies. A policy uses a Send web surveys action and requires the appropriate Recording > Retention Policy permissions, a published web survey form and a published survey invite flow in Architect.

Policies match criteria by media type, including voice, email and messaging. Interactions must have recordings retained for surveys to be sent, and recording must be enabled on the SIP trunk. Policies apply only to interactions that occur after they are enabled; they do not generate invitations retroactively.

Delivery details influence the customer experience. Organizations can configure the sender name and sending domain. A recognizable sender, such as “CompanyNameSupport,” helps customers identify the invitation; if no sender name is set, the message shows “no-reply.”

For email and messaging interactions, the initial invitation can be sent As per the Threading Timeline, when the conversation’s threading timeline expires, or After 72 Hours from disconnection. The Send Survey setting controls only the initial invitation. Reminders follow the configured interval: the number defaults to zero, and reminders can be sent up to 90 days after the initial invitation. Customers have 90 days from survey creation to respond.

One interaction can receive only one survey. If it matches multiple policies with survey actions, only one policy sends the invitation, and the organization cannot predetermine which one. Genesys recommends specific criteria to prevent overlap. If multiple customer participants are on an interaction, the invitation goes to the most recent customer participant. See the Genesys web survey policy documentation.

Actionable takeaway: Publish and test forms and invite flows before enabling narrowly scoped policies; verify recording retention, sender identity, timing and overlap rules.

3. Voice surveys: what inbound post-call feedback really requires

Genesys Cloud voice surveys support inbound calls and are designed for post-call feedback. Architect can generate a voice survey flow automatically from a published survey form. Callers can be transferred into the survey after the agent disconnects by using the Set Post-Flow action.

Voice surveys have specific licensing and platform requirements: one of Genesys Cloud CX 1 WEM Add-on II, CX 2 WEM Add-on I, CX 3 or CX 4, plus Edge and Media Tier version 1.0.0.15050 or later. Standard Genesys TTS cannot be used. Organizations need Genesys Enhanced TTS, which is free when used exclusively in voice survey flows and installed from AppFoundry, or a compatible third-party engine.

The generated flow maps form elements into Architect actions. Question groups become reusable tasks; questions use Ask Survey Question actions; and conditional groups include “Not Applicable” and “Default” paths. A Disconnect action ends the flow. Teams can customize action names, prompts, DTMF settings and timeouts, including inter-digit and voice input timeouts.

Voice forms also have constraints: a cumulative maximum of 50 Multiple Choice, Yes-No and Range questions; up to 20 answer options per question, though fewer are recommended; answers up to 50 characters; and one NPS question per form. Voice transcripts are capped at 4,000 characters, which matters for free-text answers and NPS follow-ups. Genesys recommends duplicating a shared web form without markup or encoded characters for voice use.

Actionable takeaway: Keep voice surveys focused, review generated Architect actions, and validate TTS, DTMF and timeout behavior before routing callers into the flow.

4. Consent, opt-out and email deliverability

A survey program should respect customer preferences and protect the organization’s ability to send invitations. Genesys Cloud lets teams record a survey opt-out preference for an External Contact in Directory > External Contacts. Advanced invite flows can check that flag and stop the invitation with an OptOut disposition.

Email hygiene matters, too. Genesys recommends validating customer email addresses, using confirmed opt-in, and removing non-engagers within a configured timeframe to reduce the risk of sending to spamtraps. Include an easy-to-spot unsubscribe link. For testing, do not use fake email addresses; Genesys recommends the Amazon SES mailbox simulator.

A high survey email bounce rate can lead to a temporary suspension of survey email sending. Genesys notifies the organization and works with it to resolve the issue. In practice, deliverability is not just a technical detail: it affects whether future feedback requests reach customers.

Actionable takeaway: Check opt-out preferences in the flow, test with the recommended mailbox simulator, and maintain clear unsubscribe and list-hygiene practices.

5. Turning responses into decisions: Surveys Performance views

Genesys Cloud provides a Surveys Performance Summary view in the Analytics workspace and a Surveys Performance Detail view for individual form versions. The Summary view shows survey status and responses; Detail exposes the questions and responses for a selected form version. Genesys lists CX 3, CX 4 or EX licensing, along with Analytics > Survey Aggregate View and Quality > Survey Form View permissions, as prerequisites.

A key reporting detail: survey data is assigned to the interval when the invitation was sent, not when the customer completed it. A survey sent on January 10 and completed on February 15 counts in the January 10 interval. Teams reviewing recent feedback should account for this timing.

Filters include date ranges up to six months, media type, user, queue, wrap-up code, skills, language, score ranges, NPS ranges, survey type (web or voice) and response status (full or partial). Views require a manual refresh to display current data; teams can save views and export results. Survey results also appear in an interaction’s Quality tab, and survey events can feed journey management for sentiment and trend analysis. Dashboards can visualize the data.

Review the Surveys Performance Summary and Detail view documentation when setting up recurring reviews.

Actionable takeaway: Align reporting windows with invitation dates, refresh views before analysis, and connect survey patterns to interaction and journey context.

6. Design choices that decide your response quality

Good feedback design is a series of practical trade-offs. Segment forms by interaction type so questions remain relevant. Make the sender recognizable and choose invitation timing deliberately: waiting until a threading timeline expires may fit an ongoing email or messaging exchange, while a set delay creates a consistent interval after disconnection.

Keep voice forms concise, with clear answer choices and fewer options where possible. If the same research questions need to work across web and voice, maintain separate versions when markup or channel constraints demand it. Comparing channels also requires care: people who respond to a web invitation may differ from callers who complete a voice survey. The channel, timing and form design all shape the feedback that becomes visible.

Use results to investigate patterns, not simply rank teams. A score range or NPS movement can indicate where to look; interaction details and recurring themes help establish what may need to change. A well-designed feedback program is not just a survey. It is a repeatable process for collecting, reviewing and acting on customer input.

Planning broader Genesys Cloud changes alongside surveys? Dunamis Consulting’s 5-step migration framework offers a structured view of cloud telephony planning.

Actionable takeaway: Start with a focused pilot, compare feedback by channel and interaction type, and work with Dunamis Consulting for a consultation to identify gaps and opportunities, cost analysis, project scheduling, flexible staffing solutions, bulk hour purchases, and managed and support services, backed by 15 years of cloud telephony experience.