Features

Distribution

Lives on your page, not on ours

The question should sit where your audience already is — under the post, on the landing page, in the email.

A link or a snippet

Share the link anywhere, or paste the embed into your site. Both point at the same project and collect into the same inbox.

It looks like you

House styles keep the fonts, colours and caption look consistent across projects, stored as what you changed rather than as a frozen copy.

Tell your other tools

Webhooks fire when a response arrives or gets enriched, and API keys let your own systems read what came in.

What actually happens

Publishing and embedding are two separate questions. A project can be live without being embeddable, and an embed can be locked to specific domains or gated by a token rather than left open to whoever copies the snippet.

A language version carries its own publication state — you can ship the English one and keep the Polish one in draft without cloning the project and hoping the two stay in step.

Your audience has something to say.

Give them a way to say it. We'll walk through what Wall of Voice could look like for your audience.

See what Wall of Voice could look like for your audience.