Help centre

Stuck on something
specific?

This is the task-level help for people already building a survey: why a question is not showing, how to let someone finish later, how to stop a survey collecting, where uploaded files live, and what ends up in the CSV. A full searchable help centre is still being assembled. The twelve answers below cover the questions that come up first when you build a survey, and each section points at the reference page that goes deeper.

If your question is not here, send it over — the help centre is being written from real questions rather than guessed ones.

Ask a question Open the builder

Common questions

Why is a question not appearing in my published survey?
Almost always conditional logic. A question with a show rule stays hidden until the rule matches, and rules match either any or all of their conditions — an all rule with two conditions needs both to be true. Check the rule on the hidden question, not on the question above it.
How do I let people finish a survey later?
Turn on save and continue. The respondent gets a resume link keyed on a 24-character token, and their partial answers are stored separately from completed responses until they submit.
How do I stop a survey collecting responses?
Set a close date, a response cap, or both. Each is enforced by a database trigger rather than by the interface, because responses insert directly from the browser. You can also write your own closed message, which is what a late respondent sees.
Can I show one question at a time?
Yes. Switch the survey to the conversational layout, where one-tap questions advance automatically. The alternatives are classic, which is a single scrolling page, and paged, which shows one section per screen.
How do I put a respondent’s earlier answer into a later question?
Use piping: write {{question_id}} in a question title, description or inline heading and it is replaced with what that respondent answered. If the question was not answered, it renders as “your answer” rather than showing a raw token.
How do I pass information into a survey from a link?
Declare a hidden field on the survey, then add it to the query string of the survey link. The value is stored with the response and appears in the CSV export, which is how panel IDs, cohort names and source tracking are handled.
Where do uploaded files go?
Into a private storage bucket. They are never publicly readable — access is restricted to your organisation and served through signed URLs that expire after 300 seconds.
How do I get rid of my test responses?
Use “clear test responses”. It removes the responses along with their uploaded files and any partially saved sessions, so your export starts at the first genuine respondent. Run it immediately before publishing the live link.
How does a matrix question export?
Each row of the matrix becomes its own column in the CSV. An eight-statement grid produces eight columns rather than one combined cell.
Can I add a partner or council logo to one survey only?
Yes. Collaborator logos are set per survey rather than per account, so one workspace can badge a different partner on each survey without changing the organisation’s own branding.
Who in my organisation can see responses?
Members of that organisation. Roles are owner, admin and member, row-level security applies throughout, and organisation isolation is pinned server-side rather than trusted from the browser. The last owner of an organisation cannot be removed or demoted, which is enforced at database level.
Will I get an email when someone responds?
Yes. Add the addresses to notify on the survey and each new response triggers an email. The answers are not included in it — notifications get forwarded and sit in backups, so the response stays in the results view where the access controls are.

By area of the product

Each of these is a full reference page rather than a help article, which means it explains the mechanism as well as the steps.

Things that are not going wrong — they are just not built

Some questions are about features that do not exist, and it saves everyone time to say so up front. There is no AI summarising of free text, no Zapier app or Google Sheets connector, no in-app template library, no payment collection, no offline or kiosk mode, no qualified electronic signatures, no multi-step approval chains, no SSO and no mobile apps. If you are hunting for a setting that controls one of those, stop hunting.

What exists instead is documented in detail across the product overview, and the pricing page lists both sides of that line in one place.

Questions about data rather than the product

Information governance questions get their own pages, because the answer usually has to be forwarded to someone else. Survey content and responses are stored in London (eu-west-2), encrypted in transit and at rest, with row-level security throughout. The detail lives on the security page, the UK GDPR page and the sub-processor list. If you have been sent a DPIA to complete, start there — most of the questions on a standard one are already answered.

Getting a person

There is no ticket queue to disappear into. Questions come to the people who wrote the code, through the contact page. If you are still deciding whether to use the product at all, the guides section covers survey design and the template structures sketch out thirty surveys you can build today.

Most answers are quicker to try.

Logic rules, resume links and close dates are easier to understand with a survey open in front of you. Build a test one, try the setting you are stuck on, then clear the test responses.

  • Twelve answers above, plus six reference pages that go deeper
  • Questions go to the people who wrote the code, not a queue
  • Clearing test responses removes their uploads and partials too
Open the builder