Help / Routing forms

Building a form

You build a routing form in the form editor, which you open from Routing Forms → New Routing Form (or by clicking an existing form). The editor is organized into tabs:

Zoom

• Settings: the form's title, its URL slug (the public link is 42min.us/r/<username>/<form-slug>, where the username is the slug of whoever created the form), a public description, whether to show the header on the public page, the language, the submit button text, and a Hide from search engines toggle (keeps the form's public page out of search results with a noindex signal, though anyone who has the link can still open and submit the form).
• Fields: the questions you ask. Add a field, give it a label, pick a type, mark it required if needed, and reorder with its ↑ / ↓ buttons (the order is the order visitors see them). Field types:
  • Dropdown / Radio / Checkboxes: choose from a list of options you define (checkboxes allow multiple).
  • Text / Textarea: short or long free text.
  • Number: numeric answers.
  • Email / Phone: typed appropriately.
• Rules: the routing logic. See Routing rules.
• Responses: every submission, with the answers given and where the person was routed. Visitors sent straight to a destination by a detected rule are listed here too, marked Routed on page load in place of answers.
• Customization: the public page's theme and branding.
• Share: the public link and embed options.

How to do it

1. Open Routing Forms → New Routing Form.
2. On Settings, set the title and slug (and tweak the description / language / submit text if you like).
3. On Fields, add the questions you need to route correctly, typically one or two (e.g. a "Team size" dropdown).
4. On Rules, add your routing rules and the mandatory fallback, each pointing at a destination.
5. Save, then test the public link yourself.

Common pitfalls

• A field with no good answer for everyone. A required field with options that don't cover every visitor will block some of them, so add a catch-all option or make it optional.
• Field referenced by a rule, then deleted. If you remove a field that a rule's condition uses, fix the rule too, otherwise the condition can't match.
• Slug clash. Each routing form needs a unique URL slug; the editor flags reuse.