Questions, answered. How it installs, who sees it, and where the answers go.

In-product surveys. A small card opens inside your own product, asks one or two questions, and the answers arrive in Respondo as people give them.

Four: a 0–10 score for NPS, a rating on a 3, 5 or 7 step scale shown as numbers or faces, single or multiple choice with an optional Other box, and open text. Any question can be marked optional, and an answer can branch to a later question or end the survey.

No. There are templates for NPS, customer satisfaction, product–market fit, onboarding, feature feedback, cancellation, pricing, docs feedback and open feedback. Each one is a starting point you can edit.

Yes. You pick the accent, background, text and border colours, one of three corner radii, one of three widths, and one of seven positions on the page. Button and text colours can be worked out from your accent and background for contrast.

Paste one script tag, carrying your public key and the survey's id, into the pages you want to ask on. If you would rather control it from code, the typed client does the same job and lets you open a survey on your own trigger.

Yes. Give the client an onSession handler and render the questions however you like. Question order, skip logic, required answers, targeting and submission still come from Respondo.

The script tag runs on any page that serves HTML, so React, Next.js, Vue, Svelte, Rails, Django, Laravel and plain HTML all work the same way.

Yes. Match pages by URL — contains, exact, starts with, or a regular expression — and show it to a share of visitors. Each visitor's place in the sample is rolled once and remembered, so it does not change between visits.

Not by default. Once someone answers, Respondo remembers it in their browser and does not show that survey there again. You can switch this off per survey. A different browser or device counts as a new visitor.

Yes. Set a delay in seconds, or set the trigger to manual and open it from your own code at the moment that makes sense.

By default, yes: each browser gets a random id so a partial answer can be told from a new one, and nothing more. If you want to know who answered, your site can pass an email, a name and any other traits — your own user id included — and they are stored with the response.

In Postgres, on Supabase. Self-hosting, when it ships, will let you keep them in a Postgres you run yourself.

It lets Claude, or any client that speaks the Model Context Protocol, read your results and responses and create, edit, publish, pause or delete surveys, through eight tools.

Most clients open a Respondo consent screen in your browser the first time they connect. Clients that cannot do that can use a secret key instead, created in Settings. Secret keys are stored hashed and shown only once.

Yes. Access is split into reading surveys and changing them, and every connected client is listed in Settings under Connected apps, where it can be revoked.

Not yet — self-hosting is on the way. Email us what you need, and we will tell you when it ships.