Skip to main content

Best Practices Feedier Surveys

Discover all the best practices when it comes to survey creation

Written by Julien Chil Hagopian

A well-built Feedier survey takes only a few key decisions: the right questions, the right targets, the right channel. This guide walks through what works, what to avoid, and how to handle common edge cases.

Set the right targets first

Before adding a single question, decide what "good" looks like:

  • Keep it under 10 questions → aim for completion rate > 95%

  • Response time < 3 minutes

  • Include at least one KPI question (Rating, NPS, or Emoji) to measure the satisfaction ratio

  • Add Logical flows (conditions) so respondents only see what's relevant to them

  • Pin your KPI questions to the homepage dashboard for at-a-glance monitoring

Choose the right question types

All Feedier question types serve a purpose, but three should be in nearly every survey: Ratings, NPS, and at least one Text question.

Ratings (CSAT)

Ratings measure the satisfaction of specific KPIs. Labels (e.g. 'I like it') can be customized in the content editor.

NPS

The fastest way to see who your promoters and detractors are.

Choice

Best for collecting opinions on a topic. If the question is about satisfaction, prefer a Rating — you'll get more value out of the satisfaction ratio.

Text / Open-ended

Place text questions at the end of the survey, or right after a Choice or Rating question, to dig into the "why" behind the answer. A sentiment score is computed automatically for every response.

If you don't want text responses to count toward the satisfaction ratio, toggle this off in the question's Advanced settings.

Survey design tips

  • Brand your survey — at minimum a logo, cover image, and brand color.

  • Always use attributes. Never ask the end-user for data you already have elsewhere (CRM, database, session metadata).

  • Build for reuse — use a master survey as a template so other teams can clone and adapt it.

Change a displayed label without renaming the attribute

A common confusion: the internal attribute name (used for mapping, segmentation, and reporting) is not the same as the label shown to respondents in the survey.

If you want to change only what the respondent sees — for example, display "Entity" in the form while keeping the attribute tied to the existing Carrier data — do not rename the attribute itself. Instead:

  1. Open your survey → OptionsMulti-language settings

  2. Go to the Questions section

  3. Edit the displayed label for the language(s) you need

This updates only the user-facing label. Your attribute mapping, historical data, and reports remain intact — and you avoid collisions with other attributes (e.g. if an attribute named Entity already exists with different values).

Rule of thumb: use translations / Multi-language settings to change what respondents see; only rename an attribute internally if you also want to change how it's stored and reported across the platform.

Get the best response rate

Email / SMS campaigns

  • Always pass attributes — via CSV upload or by triggering the campaign through the API (e.g. from your database).

  • Use a custom SMTP whenever possible to maximize deliverability (Teams > Settings > SMTP).

  • Keep the message short to reduce inbox scrolling, include a visual call to action, and mention the average response time.

  • Personalize with an attribute — e.g. Hi {name},

  • Use a clear, short subject line.

  • Schedule two follow-ups: at 48 hours and 7 days.

  • Adapt send times to your audience:

    • B2B → working hours

    • B2C → after 6 pm

  • Monitor pushes in Insights > Pushes; contact those with Opened or Clicked status who haven't responded.

Web widget

  • Trigger only at the right moment in the user journey, and consider auto-opening.

  • Pass contextual attributes from the user's session (metadata you already collect).

  • Use a Tag Manager wherever possible — cuts integration time by ~95% (no dev required).

  • In the survey itself, avoid:

    • Heavy branding

    • Ranking questions with more than 2 options, long text items, and overly long questions

    • Long surveys overall

  • Prefer Emoji, Choice, and Ratings (max 5 stars).

  • The trigger button must be highly visible (strong contrast) and must not overlap important UI.

FAQs

How do I share a survey?
Most feedback is collected through the Feedier web widget, while email/SMS campaigns are ideal for targeted cohorts. Share links live in the Share section of your survey. You can also set up a direct integration with your database so sharing is triggered automatically.

How do I get alerted to feedback in real time?
Create a Segment, then under the Actions tab configure alerts via email or a third-party tool (Slack, Teams). Choose between real-time alerts per matching feedback, or a weekly/monthly digest.

What's the fastest way to get an overview of results?
The KPIs on the homepage. The main activity chart lets you compare how different attributes score on total feedback or satisfaction.

What's the best way to share results?
The PDF Report. Generate it via the Create Report button from the Feedback or Insights pages, and customize the charts to fit your audience.

How do I add new team members?
Side menu → Users / TeamsInvite User.

I added a new question to my survey but it doesn't show up on Feedbacks. Why?
You need to push your latest changes after editing the survey. Until you publish, the new question won't appear on incoming feedback.

Can I change a question's displayed label without renaming the attribute?
Yes — use Options → Multi-language settings → Questions. This changes only what respondents see, leaving the underlying attribute (and your historical data) untouched. See Change a displayed label without renaming the attribute above.

Did this answer your question?