Help / Routing forms

Routing forms overview

A routing form is a short questionnaire you put in front of people before they book. Based on their answers, 42min sends each person to a different place — an event type's booking page, an external URL, a message, or even another routing form. It's how you make sure a 500-person company talks to your enterprise rep and a solo founder gets your self-serve link. Manage forms from Routing Forms.

What it is

A routing form has three parts:

1. Fields — the questions you ask (dropdowns, text, number, checkboxes, email, phone…). See Building a form.
2. Rules — evaluated top to bottom; the first rule whose conditions match the person's answers wins. See Routing rules.
3. A fallback — a mandatory last rule for everyone who matched nothing else, so no one hits a dead end.

When someone submits the form, 42min finds the matching rule and forwards them to its destination. The form has its own public URL (42min.us/routing/<slug>) and you can also reach a routing form from another routing form, chaining them.

Zoom

When to use it

• Inbound leads should go to different reps (by company size, region, product).
• A "Contact us" link that needs to triage before booking — sales vs support vs partnerships.
• You want a public link that asks one or two qualifying questions and then shows a booking page.

If everyone who clicks should book the same meeting with the same person, you don't need a routing form — just share an event type link.

How to do it

1. Open Routing Forms → New Routing Form.
2. On Fields, add your questions — see Building a form.
3. On Rules, add rules from most specific to least, and set the fallback — see Routing rules.
4. Pick each rule's destination.
5. Save and share 42min.us/routing/<slug>. Watch submissions on the form's Responses tab and in Analytics → Routing.

Common pitfalls

• No fallback. Every form needs a catch-all rule. If a person's answers match no specific rule, the fallback decides where they go — make it something sensible (often your general intro-call event type).
• Rules in the wrong order. First match wins — put narrow conditions above broad ones, or the broad rule will swallow everyone first.
• Asking too much. Each extra question costs you submissions. Ask only what you need to route correctly; collect the rest on the booking form afterwards.