BLOG
Automating a post-delivery satisfaction survey means connecting a confirmed completion event to a short question, a contextual record, and responsible follow-up. Sending a form to the entire customer list is not the same process. The useful result is an answer the team can associate with the relevant delivery and act on.
Start with one experience, a simple rating, an optional explanation, and a clear owner for low scores. Choose the channel and timing for the actual relationship rather than assuming one app or schedule fits every business.
Use confirmed delivery or service completion as the trigger
For an order, use the confirmed delivered state from the appropriate carrier or operating system. Dispatch time and estimated arrival are different events. A survey sent before the customer receives anything asks about an experience that has not occurred.
For a service business, define the equivalent completion state with the team. An approved website handover, completed appointment, or finished support intervention can be different triggers and should not be mixed without a reason.
Give each stage a purpose
| Stage | Purpose | Common mistake |
|---|---|---|
| Confirmed completion | Start from an actual event | Using a shipping estimate |
| Timing | Allow experience of the result | Asking before use or long afterward |
| Question | Collect a focused answer | Combining many subjects |
| Record | Keep delivery context | A score isolated in a message |
| Follow-up | Assign a concerning response | No person owns it |
| Reminder | Offer a limited second opportunity | Repeated unwanted requests |
| Review | Connect feedback to a decision | Reporting without action |
Choose timing according to the experience
Send the question after the customer has had a reasonable opportunity to use or assess the delivery. An immediately usable service and something requiring setup can need different intervals.
A few hours or one to three days can be starting scenarios to evaluate, not a universal optimum established by this guide. Comments such as “I have not used it yet” indicate that the chosen timing needs review. Very delayed requests can create another problem: the experience is no longer clear.
Ask one understandable question
For a five-point satisfaction survey, an illustrative question is: “From 1 to 5, how would you rate this delivery?” Explain the scale consistently and make an additional reason optional.
Avoid asking about packaging, timing, support, and the whole company as if they were one precise measurement. Define the experience being rated. The comment can provide context, but a number alone does not diagnose the cause or seriousness of every issue.
Record the answer with the right context
Associate the response with an internal order or service reference, customer context where appropriate, and date. Use an authorized CRM, maintained record, or survey platform instead of leaving the score in an isolated chat.
Keep the link between invitation and response reliable without exposing unnecessary personal information in a public URL. A repeated delivery event or another click should not create an unrelated second survey record.
This context lets the team examine patterns by delivery type, period, or other relevant operational category. It does not establish causation from one low rating.
Assign low scores to a person
Define a business rule for review, such as flagging ratings of 1 or 2 on a five-point scale. Include the relevant delivery reference and authorized comment so the receiving person can investigate.
The response should aim to understand and resolve the case. Record the outcome through the appropriate process rather than merely collecting complaints in another dashboard.
Automated task creation organizes the handover; it does not prove that the issue was resolved. Define who owns the task, how overdue cases are noticed, and what counts as closure.
Limit reminders and stop when appropriate
A single optional reminder can be a practical starting policy for customers who have not responded. Review whether it fits the channel and relationship, then end the sequence rather than repeatedly requesting an answer.
Check whether a response arrived, communication was declined, or the case became unsuitable before sending again. A satisfaction survey should not create the next reason for dissatisfaction.
Distinguish CSAT from NPS
Qualtrics compares CSAT and NPS as measures with different focuses. For a transactional question, CSAT can describe satisfaction with a specific experience. In a common five-point implementation, the calculation uses responses 4 and 5 divided by all valid responses, multiplied by 100.
NPS concerns willingness to recommend. Bain’s NPS reference describes the system. Its calculation subtracts the percentage of detractors from the percentage of promoters; promoters are ratings 9–10 and detractors 0–6.
Do not treat the two scales as interchangeable. For the relationship question, choose a cadence or milestone appropriate to the business rather than automatically adding an NPS request after every transaction.
Review response coverage, not just the score
Alongside the satisfaction measure, track how many eligible invitations were sent, how many valid responses arrived, and how many flagged cases received follow-up. Keep the definition and observation period stable.
For example, eight satisfied responses out of ten valid five-point responses produce an 80% result under the stated CSAT rule. That does not mean 80% of all customers were surveyed or satisfied. State the sample and response coverage.
Check channel cost and data handling
If using WhatsApp Business Platform, consult the current official pricing and relevant messaging requirements. Category, destination market, and the service window can affect the arrangement. Do not assume every survey message is free.
Use an authorized contact route, explain the purpose, and provide an appropriate way to decline further communication. Check applicable US requirements, contracts, and organizational rules with the responsible person instead of importing a Brazilian legal reference as the governing rule.
Collect only necessary feedback and restrict access to customer comments. A survey response does not automatically authorize public use as a testimonial.
Pilot the circuit before increasing volume
Use controlled records to verify the completion trigger, invitation, response mapping, reminder suppression, and low-score task. Include a repeated event and an already-answered invitation.
Confirm that the human owner can find the context and record a resolution. This is a proposed test procedure, not a claim that a provider account or customer campaign has already been configured here.
Frequently asked questions
How many questions should I start with?
One focused rating and an optional explanation provide a manageable first workflow. Expand only when another question serves a clear purpose.
Can I reward a positive rating?
Conditioning an incentive on positivity undermines the measurement. If an incentive is appropriate, separate participation from the requested score and review the relevant rules.
What completes the automation?
The answer is recorded correctly, exceptions reach an owner, reminders stop appropriately, and someone reviews the resulting evidence.
