Customer survey limits: 8 figures for campaign planning

• Distinguish daily volume from invitation size. A default domain permits 10,000 emails daily, while a custom domain permits 50,000, but a single survey invitation is capped at 10,000 recipients according to Microsoft.
• Match import files to contact limits. You can import a maximum of 10,000 contacts using a CSV file, which aligns with the recipient cap for a single invitation according to Microsoft.
• Limit saved emails to ten. The system allows saving a maximum of 10 email messages for reuse across different campaign segments according to Microsoft.
• Treat high counts as cached data. If a rating count exceeds 100,000, the result is cached and updates every 24 hours, applying specifically to legacy CSAT endpoints according to Zendesk.
• Note the image display count. The interface displays only the most recently 9 images, which is a display constraint, according to Vitally.

Sending capacity differs from reporting counts. For Microsoft Customer Voice, the default domain permits a maximum of 10,000 emails per day, according to Microsoft. A custom domain permits a maximum of 50,000 emails per day, according to Microsoft. These daily figures define sending throughput, not total respondent capacity.

Invitation size and import limits operate separately from daily sending rates. You can send a survey invitation to a maximum of 10,000 recipients, according to Microsoft. You can import a maximum of 10,000 contacts by using a CSV file, according to Microsoft. These boundaries constrain the size of a single invitation batch and the initial contact list, not the total number of emails sent over time.

Saved email storage is a distinct operational limit. You can save a maximum of 10 invitation emails, according to Microsoft. This cap applies to saved invitation emails, not to the number of surveys you can create or send.

Read status tracking uses a specific mechanism. Customer Voice uses a pixel-tracking mechanism in survey invitation emails to determine whether the invitations are read or unread, according to Microsoft. This tracking indicates whether the email was opened, not whether a response was submitted.

These figures apply to the specific products and domains named in the sources. Do not treat one publisher's rule as every firm's rule.

The following table lists the eight documented figures by publisher. Publication dates are unknown for all sources.

Verify your specific tool version against these values before launch.

Picture a send day with a cap of 10,000 emails and one invitation of 10,000 people. The invitation fills that day, so another batch of 10,000 waits until the next day. You keep 8 saved emails, show 9 images on the survey, and use 1 page. These round figures are illustrative. They show how to line up one invitation, a daily cap, saved emails, and a page count before launch.

When planning a feedback campaign, you must account for five specific operational boundaries within the "Send a survey by using email" documentation. These figures define the maximum throughput and storage capacity for your outbound communications.

First, consider your daily sending volume. If you are sending email using the default domain, you can send a maximum of 10,000 emails per day, according to Microsoft. This cap applies specifically to the default sending infrastructure. If you are using a custom domain, you can send a maximum of 50,000 emails per day, according to Microsoft. This distinction is critical for large-scale campaigns where daily volume might exceed the standard threshold.

Second, evaluate the size of your invitation list. This limit governs the total number of individuals who can be targeted in a single survey invitation action.

Third, verify your contact import method. If your customer database exceeds this number, you must split the import into multiple batches to stay within the documented boundary.

Finally, manage your email storage. This constraint limits the number of pre-configured invitation messages you can store and reuse for different segments of your customer base.

These five figures—default daily emails, custom daily emails, invitation recipients, CSV import contacts, and saved emails—form the core operational limits for Microsoft Customer Voice. They are distinct from reporting counts or editor display constraints covered in other sections. When structuring your campaign, ensure your daily send volume does not exceed the domain-specific cap, one survey invitation stays within 10,000 recipients, and your data import strategy respects the CSV boundary. If you are preparing to launch a survey, verify that your chosen sending domain aligns with your required daily throughput.

When planning a feedback campaign, distinguish between sending capacity and reporting counts. In the Satisfaction Ratings | Zendesk Developer Docs, if the count exceeds 100,000, the count will return a cached result according to Zendesk. This cached result will update every 24 hours according to Zendesk. Do not treat this 100,000 figure as a hard limit on the total number of survey respondents you can invite; it is a threshold for how the API reports the count.

During background updates, the system behaves specifically. When the count exceeds 100,000, count[refreshed_at] may occasionally be null according to Zendesk. This indicates that the count is being updated in the background, and count[value] is limited to 100,000 until the update is complete according to Zendesk. If you see a null timestamp or a value capped at 100,000, the system is still processing the data. You should not interpret this cap as a restriction on your ability to collect more responses, but rather as a temporary state in the reporting mechanism.

Scope these figures carefully to the specific endpoints. The endpoints listed on this page are for the legacy CSAT feature according to Zendesk. Therefore, these cached count behaviors and the 100,000 threshold apply specifically to the legacy CSAT feature endpoints, not necessarily to all current survey or feedback mechanisms within the platform. If your campaign relies on newer feedback features, verify whether these specific legacy endpoint rules apply to your data retrieval method.

Check your reporting tools to see if they are pulling from these legacy endpoints. If they are, expect the 24-hour refresh cycle and the potential for null timestamps during background updates. Plan your data review windows to account for the 24-hour update interval, ensuring you do not make decisions based on stale cached data. Confirm that your integration is correctly handling the null refreshed_at values and the temporary 100,000 value limit during background updates to avoid misreporting your campaign metrics.

When configuring visual assets for your feedback campaign, note the display constraint. The Custom Surveys documentation states, "We only display the most recently 9 images, nothing more" according to Vitally. This limit governs what appears in the interface. Plan your visual sequence accordingly if you intend to rotate graphics across multiple survey waves.

For multi-page survey structures, the Survey Design guide specifies that "A survey should always have at least one page" according to Gainsight. This minimum requirement ensures that every survey has a valid landing point for respondents. This baseline applies regardless of how many questions you include on that single page.

Participant experience is further constrained by the rule that "Survey participants can only view one page at a time" according to Gainsight. This means that even if your survey contains ten pages, a respondent sees only the current page before advancing. Design your page transitions to guide users smoothly from one step to the next, knowing that each page is a discrete unit of interaction.

Editorial recommendation: Audit your current survey layouts to ensure that no page exceeds the attention span of your typical respondent. If you use more than nine images in a single campaign, verify that your rotation logic aligns with the display limit to avoid unexpected gaps in visual branding.

Do not assume that a limit in one vendor's documentation applies to another platform. The figures you have for Microsoft Customer Voice, Zendesk, Vitally, and Gainsight are distinct operational boundaries. Each applies only to the product named in its source.

When you review your dashboard, distinguish between sending capacity and reporting counts. A daily email cap is a hard limit on how many messages you can dispatch per day. A cached rating count is a reporting figure that updates on a background schedule. These are different mechanisms. Do not use a reporting threshold to plan your daily send volume.

Invitation read status is a tracking metric, not a response. This mechanism records when an email is opened, according to Microsoft. It does not record whether a customer completed the survey. If you use read status to measure campaign success, you will overstate your response rate. A read invitation is not a submitted response.

Before you launch, compare your planned invitation count, daily sending volume, and contact import size against the documented limits for the specific tool and sending domain you already use. Today, write these totals beside the cap for the tool you use, and read outbound email limits, survey rating bands, and help center limits.

What customer survey limits are documented for campaign planning?

The documented figures include 10,000 daily emails for default domains and 50,000 for custom domains, according to Microsoft. You can send a survey invitation to a maximum of 10,000 recipients and import a maximum of 10,000 contacts by using a CSV file, according to Microsoft. If the count exceeds 100,000, the count will return a cached result, according to Zendesk. The system displays the most recently 9 images, according to Vitally. A survey should always have at least one page, according to Gainsight.

How many survey emails can Microsoft Customer Voice send daily with a custom domain?

A custom domain can send a maximum of 50,000 emails per day, according to Microsoft.

How often does Zendesk update its cached rating count?

The cached result will update every 24 hours, according to Zendesk. This refresh interval applies when the count exceeds the threshold that triggers the cached result behavior.

Does the Zendesk count guidance apply to legacy CSAT endpoints?

Yes, the endpoints listed on this page are for the legacy CSAT feature, according to Zendesk.

Can Gainsight survey participants view multiple pages at once?

Survey participants can only view one page at a time, according to Gainsight. This constraint defines the participant experience for multi-page survey structures.

This post is general operational information, not legal advice about notice periods or renewal clauses. It does not promise that any method keeps a customer. A review model checked the facts once, and that check can miss errors, so open the sources before you act.