Customer Satisfaction Surveys: When to Send Them and What to Ask

A customer satisfaction survey asks a defined group of customers to evaluate a specific experience or their broader relationship with a company. Send it when the customer has had enough exposure to answer the question, while the experience is still identifiable, and only when someone owns the decision that the response can change.

The best send time is therefore not “immediately” or “quarterly” in the abstract. It follows from the object of evaluation. A support-resolution survey may be triggered after a case closes. An onboarding survey may wait until the customer has had a fair chance to complete the relevant steps. A relationship survey may use a periodic sample rather than follow every transaction. The survey request, question, response scale, and analysis window must all refer to the same object.

Start with the experience and the decision#

Write a one-sentence measurement contract before writing the question:

Among [eligible customers], after [defined experience], ask about [one construct] within [time window] so [named owner] can make [specific decision].

For example, a support team might evaluate satisfaction with a resolved case so its operations lead can examine resolution quality by issue type. A product team might evaluate a completed setup flow so the onboarding owner can decide where qualitative follow-up is needed. These are illustrative applications, not real company cases or benchmark recommendations.

If the team cannot name the decision, the survey is likely to create commentary without accountability. A rating may move, but nobody will know whether to change the product, the process, the message, or the measurement itself.

Transactional and relationship surveys answer different questions#

A transactional survey is linked to a defined interaction: a support case, delivery, onboarding step, purchase, renewal conversation, or feature workflow. It should be close enough to the event that the customer can identify it, but not so early that the promised outcome has not occurred. The trigger should come from a reliable system state, not an assumed elapsed time.

A relationship survey asks about the broader customer-company relationship. It can be useful when no single event captures the experience or when leadership needs a periodic view across accounts. Its reference period and eligible population must be explicit because respondents can otherwise average very different recent experiences.

Qualtrics distinguishes transactional surveys from relationship surveys; that distinction is useful because it prevents a case-level score from being presented as a complete account-health measure. It also prevents a broad relationship rating from being assigned to one touchpoint without supporting evidence.

When to send a customer satisfaction survey#

Use the underlying process to choose a trigger and delay.

After a completed interaction#

Send after the system has recorded the state that the question names. A “satisfaction with resolution” question requires a case resolution, not merely a reply. A delivery survey requires delivery or a verified exception. If the state can be reopened, define whether the survey fires on first closure, final closure, or after a stability period.

After enough time to experience an outcome#

Some value appears later than the operational event. A setup form can be submitted before the setup works. A report can be generated before anyone uses it. Establish a minimum exposure condition and a maximum recall window. There is no sourced universal number for either in this research; the correct interval must be tested against the actual experience and decision cycle.

At a relationship checkpoint#

Use a documented sampling calendar and suppression policy. Periodic surveying can support trend analysis, but repeatedly asking the easiest-to-reach customers can distort it. Define whether the unit is a user, account, contract, or location and how multiple contacts within one account are handled.

After a change, with a baseline#

If the survey will evaluate a product or process change, preserve the old question wording, eligibility, channel, and analysis method long enough to interpret the comparison. A score before and after a release is not a causal estimate by itself; customer mix, seasonality, invitation volume, and response behavior can also change.

What to ask#

The smallest useful satisfaction survey often has one scoped rating, one reason question, and only the context required for action.

1. Scoped rating: “How satisfied are you with the resolution of your support request?”
2. Reason: “What is the main reason for your answer?”
3. Optional diagnostic: a question about one mechanism the owner can change, such as clarity or effort, if it is not already captured reliably elsewhere.

These are illustrative patterns, not mandated wording. The exact scale must have labelled endpoints and a stored direction. If higher values mean greater satisfaction, encode that once and use the same rule in dashboards and exports. A team may report the share of responses meeting a stated satisfaction threshold, a mean, or the full distribution, but it must preserve the denominator and scale definition.

Qualtrics and SurveyMonkey both recommend questions that stay connected to the customer experience being evaluated. That means avoiding prompts such as “How satisfied were you with the speed and quality of support?” A respondent may approve of one and reject the other, so the combined answer cannot diagnose either dimension.

Questions to avoid#

Avoid questions that make the desired answer visible, require knowledge the respondent is unlikely to have, or combine unrelated judgments.

• Leading: “How satisfied were you with our improved onboarding?” presumes improvement.
• Double-barrelled: “How satisfied are you with product speed and support quality?” combines two objects.
• Undefined: “Are you satisfied with us?” leaves the experience and period unclear.
• False precision: requesting a highly granular score when respondents cannot reliably distinguish adjacent values.
• Unowned open text: asking “What should we improve?” without a coding, routing, or response process.
• Sensitive diagnostic: collecting personal or account information that is not necessary for the stated decision.

An open-ended follow-up is valuable because it can reveal why a respondent chose a rating. It is not automatically a representative list of customer priorities. People who write comments are a selected subset, and analysts still need a coding rule, quality check, and a way to retain minority themes.

Build trigger and suppression rules before launch#

Survey burden is part of the design. A technically valid trigger can still invite the same active customer after every case, event, or login. Create one eligibility table that all sending systems use.

Do not silently replace a documented invitation rule with “everyone the tool can reach.” Who is eligible, who can receive the invitation, and who answers determine the population described by the result. A survey result describes respondents under the implemented invitation process; generalization beyond them needs separate evidence.

Interpret the result with its denominator#

Every published result should retain at least:

• the eligible population;
• the number invited and successfully delivered;
• the number responding to the rating item;
• the scale, labels, direction, and satisfaction threshold if one is used;
• the trigger and response window;
• the analysis unit and deduplication rule;
• relevant segments defined before inspecting the result;
• material changes to wording, channel, placement, or eligibility.

Do not treat “no response” as dissatisfaction. Do not assume a high score proves retention or expansion. Join the survey to behavioral outcomes only under an approved identity and analysis plan, and keep correlation separate from causal claims.

Put the survey into operation#