Customization gets dismissed as "making the form look nice."
That is too shallow. In surveys, customization changes how legitimate the experience feels, how much effort the respondent spends, and whether the data is actually usable. Every setting below maps to one of those three things.
Brand is trust
When someone opens a survey, they make a snap judgment:
Is this real? Is this from the company I know? Is this worth my time?
That is why Formaly lets you customize logo, colors, typography, background, and visual treatment, and why we added AI theme generation so you can get to a branded starting point in seconds. Generic, unbranded forms quietly raise doubt, and doubt costs you completion. This is not decoration; it is reducing the friction of "should I trust this?"
Tone matters more in conversational surveys
Static forms can get away with neutral labels. Conversational surveys cannot, if the survey talks to the respondent, tone becomes part of the experience.
| Survey type | Tone that usually works |
|---|---|
| Churn survey | Direct, respectful, low-pressure |
| Product feedback | Curious, specific, concise |
| Event feedback | Warm, appreciative, quick |
| Research screener | Clear, neutral, precise |
| Employee feedback | Careful, trustworthy, non-performative |
Formaly gives you tone controls because a survey should not sound the same in every context.
Question types are customization too
The biggest customization decision is often not visual, it is choosing the right input. Formaly supports 30+ question types, and the choice shapes respondent behavior: ratings, rankings, sliders, matrices, image choices, and open text all create different effort.
Bad type selection makes a survey feel harder than it needs to be. A prioritization question should be a ranking, not a paragraph field. A nuanced objection should be open text, not a forced dropdown.
Logic keeps the survey respectful
Logic is how you avoid wasting the respondent's time. If someone never used a feature, do not ask five follow-ups about it. If someone gives a low rating, ask why. If someone is not the buyer, skip the pricing questions.
Good conditional logic makes a survey feel shorter without removing useful questions, which matters, because drop-off rises sharply once a survey crosses ~12 questions. Branching is how a longer survey stays short for any one person.
Quotas are for serious research
Sometimes you do not just need responses, you need the right distribution of responses. Quotas let you cap or balance groups: role, region, company size, age range, plan type, or answer segment. Especially useful when over-sampling one group would distort the result.
Translations reach the audience you meant to reach
If your respondents are not all in one language, an untranslated survey silently filters them out. Formaly's translation management lets you localize a survey across languages, so a multi-region program measures everyone, not just your default-language users.
Delivery is customization, too
Where the survey appears changes how it performs:
| Delivery | Best for |
|---|---|
| Public link | Simple sharing and open surveys |
| Website embed | Landing pages, docs, post-purchase flows |
| Email invite | Named, tracked outreach |
| SDK popup | High-intent product moments |
| SDK slide-in | Lightweight product feedback |
| SDK widget | Always-available feedback |
The same survey can perform very differently depending on where and when it appears.
What I am optimizing for
Customization is not the opposite of rigor, it is part of rigor.
A well-customized survey is clearer, more trusted, better timed, and easier to finish. That is why these settings exist in Formaly: not to decorate the form, but to protect the data.