Support / Using Pilea
Creating surveys
Connected feedback sources tell you what customers say when they choose to speak up. Surveys let you ask the questions yourself - and in Pilea, every response lands in the same analysis pipeline as the rest of your feedback.
The three-step builder
Building a survey is a three-step flow:
- Basic Info - give the survey a name, a title, and a description.
- Questions - add your questions in the visual builder. You need at least one, and you can mix question types: NPS (0-10), CSAT (Stars), CES (Effort Score), Thumbs Up/Down, Rating Scale, Open-ended, Multiple Choice, Text Input, Long Text, Dropdown, Checkbox, and Radio Buttons.
- Settings - configure how the survey is displayed.
Then Publish Survey.
A few things you can add to a question:
- An image. Each question can carry one image (JPG, PNG, GIF or WebP, up to 10MB) with a description for screen readers, so you can ask about a specific screen or design.
- An “Other” option. Choice questions can include an optional Other answer with a free-text field, so respondents aren’t forced into your list.
💡 Tip: Short surveys finish. A single well-aimed NPS or rating question with a follow-up beats a ten-question form most respondents abandon.
Surveys in more than one language
Write a survey once and run it in several languages. A survey has one default language, which you set when you create it, and can add translations into any of these 12 languages: English, Norwegian (Bokmål), Swedish, Danish, Finnish, German, French, Spanish, Italian, Dutch, Portuguese (European) and Polish.
Only the wording is translated. Question types, order, required flags and the list of choices are shared across every language, so a “Very likely” answered in Swedish counts the same as one in English, and every response is analysed together.
Adding a language
- Open the survey and use the language bar above the questions. Click Add language and pick one.
- Pilea suggests a translation of the whole survey: the title, description, questions, answer options, image descriptions and thank-you message. Nothing is saved until you save the survey.
- Review the suggestion in the side-by-side translation editor, with the default language on one side and the translation on the other. Edit anything that doesn’t sound right.
The live preview follows the language you’re editing, so you can see exactly what respondents will get. The survey’s buttons, progress text and error messages are already translated for every language. The “Other” choice is translated automatically.
Keeping translations up to date
When you add or change a question after translating, the language bar shows how many fields are untranslated in each language. Until you translate them, those fields show in the default language.
- Translate {n} missing fills in only the untranslated fields and leaves wording you’ve already reviewed alone.
- You can also translate a newly added question straight from its card.
- Re-translate everything replaces all of a language’s wording with a fresh suggestion. Pilea asks you to confirm first.
- Remove {language} removes that translation from the survey.
If the copy you’ve written doesn’t match the survey’s language, for example Swedish text in a survey set to English, Pilea notices and offers to switch the survey language.
Choosing the language respondents see
The language is chosen per embed and per link, not detected from the visitor’s browser:
- Embed - pick a language in the embed options and the code includes it, as
data-pilea-language="sv"for example. Use one embed per language, for example one per locale of your site. - Shareable link - pick a language when you share, and the link opens the survey in that language.
If a language isn’t available, respondents see the default language. Every response records the language it was answered in, shown in the Language column of the responses.
Display modes and the shareable link
Choose how the survey appears when embedded in your product:
| Mode | How it works |
|---|---|
| Popup | A modal overlay |
| Expanded | Always visible inline |
| Expandable Link | A collapsed link that expands when clicked |
You can customise the link text, the submit button text, and the thank-you message, so the survey speaks in your product’s voice rather than ours. Pilea generates embed code for your site, so getting a survey in front of users is a copy-paste job.
Every published survey also gets a shareable link: a hosted page with its own URL that you can drop in emails, docs, or chat. You’ll find it, together with the embed code, when you open the survey.
Where responses go
This is the part that makes Pilea surveys different from a standalone form tool: responses don’t pile up in a separate results tab waiting for someone to export a CSV.
Each response lands as a mention with the source Survey and goes through the same analysis pipeline as everything else - PII redaction (if enabled), sentiment, classification, customer linking, and linking to backlog items. A survey answer that mentions a pain point counts toward the same backlog item as the support tickets about it. One pipeline, one backlog, no silos.
The survey’s completion rate is the share of responses that answered every question. Hover it for the details.
If PII redaction is on, a response is not analysed until redaction has confirmed it is safe. See PII redaction settings.
ℹ️ Note: Already ran surveys elsewhere? You don’t have to abandon that data. Upload survey spreadsheets under Context and Pilea will process those responses too.
A sensible first survey
- Create a survey with one NPS question and one open follow-up.
- Publish it and send the shareable link to a recent cohort.
- Give responses time to arrive, then check your mentions filtered by source Survey.
- Watch the backlog: items your survey respondents echo will gain mentions - and priority score - accordingly.
The survey doesn’t just tell you a number. It feeds the same evidence engine that ranks your entire backlog.
Next: Working with mentions
Stuck? Email us — a human answers, usually the same day.