← Back to all guides
Sell & support · Forms & surveys · ~8 min read

Formbricks

Live

Build forms and surveys with logic, collect responses privately on your own instance, and read the results without a data science degree.

See Formbricks in the tool catalogue →

What is Formbricks?

Formbricks builds forms and surveys: contact forms, customer feedback, NPS, event registrations, internal polls. Share them as a link or embed them on your website; responses collect on your own instance - respondent data never goes to a third party. It replaces Typeform, Google Forms and SurveyMonkey.

How it works: you assemble a survey from question blocks, style it, and publish. Each survey gets a share link and an embed option. Responses land in a dashboard with summaries per question, and can flow onward via webhooks (e.g. into Twenty CRM through Activepieces).

Getting started

  1. Log in at your company's Formbricks address with your Brundo account.
  2. Create a survey from a template - templates for feedback, NPS and contact forms are solid starting points.
  3. Edit the questions: add, remove, reorder. Question types include multiple choice, open text, rating, NPS and more.
  4. Publish and test: open the share link yourself, submit a test response, and check it appears in the dashboard.

Core concepts

Question types

Choose the type by the answer you need: ratings for comparison over time, multiple choice for clean stats, open text for insight (but expect fewer completions the more you ask people to type).

Logic (branching)

Show or skip questions based on earlier answers - "If rating ≤ 3, ask what went wrong." Logic keeps surveys short for each individual respondent.

A link works everywhere (email, chat, QR code). Embedding puts the form inside your website. In-app/website surveys can pop up contextually for visitors.

Responses dashboard

Per-question summaries, individual response browsing, CSV export, and completion metrics - where drop-off happens tells you which question is the problem.

Everyday tasks, step by step

Send a post-project client satisfaction survey

  1. Create from an NPS or feedback template.
  2. Keep it to 3–5 questions: one rating, one "what should we improve", one open field.
  3. Add logic: low rating → "what went wrong?" follow-up.
  4. Send the link in your project-close email. Review responses in the dashboard weekly.

Put a contact form on your website

  1. Build the form: name, email, message. Nothing more - every extra field costs conversions.
  2. Choose embed, copy the snippet, and place it on the site (Brundo can help).
  3. Set a notification so new responses alert the right person - or auto-create a contact in Twenty via Activepieces.

Run an internal poll

  1. Create a 1–2 question survey (e.g. team event date options).
  2. Drop the link in Mattermost.
  3. Results tally themselves - no spreadsheet counting.

Tips & good habits

  • Shorter wins. Completion drops with every question; ask only what you'll act on.
  • One open-text question yields more insight than five - and more completions.
  • Test on a phone before sending; most respondents will be on one.
  • Close the loop: when clients suggest improvements, tell them what changed. Response rates rise when feedback visibly matters.
  • Date-stamp recurring surveys (e.g. quarterly NPS) with consistent wording so results compare cleanly.

Troubleshooting & FAQ

Can respondents stay anonymous? Yes - link surveys are anonymous unless you ask for identifying details. Say so explicitly for internal surveys; honesty follows anonymity.

Can I edit a live survey? Typo fixes are fine. Changing question meaning mid-run corrupts your data - duplicate the survey instead and start a clean version.

Where do responses go? To your own instance's dashboard, and onward wherever you wire them (email alerts, webhooks, CSV export). Nothing goes to a third-party survey company.

GDPR? Self-hosting on EU infrastructure is a strong start. Still: collect only what you need, state the purpose, and set a retention habit for old responses.

Useful resources

Curated for the version Brundo hosts (community / self-hosted editions) — cloud-only or enterprise-only material is skipped.