Goal: by the end of this guide, your survey is sent to the right people, at the right time, and each response arrives in Feedier with its context, ready to be analyzed.
Who it's for, and before you start
Who it's for | The person who designs and runs the survey (Admin, or Editor with the Surveys module) |
To prepare | The survey's goal, the list or system that will provide the recipients, and the information you already know about each customer |
Time | One to two hours of setup, plus testing time |
The steps
1. Set the goal and the indicator
A survey answers one question: "Would our customers recommend our after-sales service?". Choose one main indicator: NPS, satisfaction or CES.
2. List what you already know
Store, product, channel, order number, language: everything you know will become an attribute passed along automatically. You'll never ask the customer for it. See Attributes and referentials.
3. Write short questions
Benchmark | Target |
Number of questions | Fewer than 10 |
Response time | Under 3 minutes |
Typical structure | 1 KPI question, 1 "why" verbatim question, 2 to 5 targeted questions |
Add conditions: a text question that only appears to dissatisfied customers, product questions based on the product purchased. See Create and configure a survey.
4. Brand the survey
In Logo & color: logo, colors, cover image. If possible, add your own sending and URL domain. See Custom domains.
5. Translate if needed
A single survey for all languages, with the locale attribute. See Multilingual surveys.
6. Choose the channel and timing
Situation | Channel | Timing |
After a purchase or a service call | Email or SMS campaign triggered by the API | Within 24 hours |
Annual barometer | Email campaign with a file | B2B: business hours; B2C: after 6 p.m. |
Journey on your website | Dynamic web widget | Right after the key step |
Point of sale | QR code | At checkout or at the exit |
Schedule two reminders, at 48 hours and at 7 days. See Distribute a survey.
7. Test, then publish
Answer using the Test link in the Share tab, on desktop and on mobile.
Send yourself the campaign, check the email and the attributes received.
Publish the survey: this is what creates its source in Feedier.
8. Track the first responses
After a few days, check the sending statuses in the Pushes menu, the first verbatims in the feedback feed, and create an alert on detractors. See Organize callbacks to dissatisfied customers.
Example
A chain of 40 stores sends a survey by SMS the day after each purchase:
Element | Choice |
Questions | NPS, "What explains your score?", rating of the welcome, rating of product availability |
Attributes passed |
|
Trigger | API, from the point-of-sale system |
Reminder | Just one, at 48 hours |
Common mistakes
Mistake | Consequence | What to do |
Asking the customer for their store or product | Incomplete data and a longer survey | Pass this information as attributes |
Forgetting to publish after a change | New questions don't appear | Publish after every change |
Several NPS questions | An averaged NPS that's hard to read | A single NPS question |
No text question | No explanation of the scores | At least one "why" question |
Going further
Last reviewed: November 11, 2026, version 4.23.5.
