# Routing forms

{/* AUTO-SYNCED SOURCE: this page lives in apps/app/src/modules/booking/docs/ and is mirrored into the docs app by `bun sync:module-docs`. Edit it in the module, not in apps/docs. */}

<Lead>
One link, a few questions, and every enquiry automatically lands at the matching event type. A **routing form** pre-sorts your enquiries: sellers to the valuation appointment, seekers to the viewing, everything else to a message. You share just one single link.
</Lead>

Routing forms live in the **Routing** area (configure permission required). Each form has its own public link at `/book/r/link-name`.

## The builder: three tabs

### Form tab

Here you build what prospects see:

- **Internal name** (for your team only) and the **link**.
- **Heading** and **intro text** for the public page.
- Up to **6 questions**. Question types: **name**, **email**, **phone**, **choice (list)**, **choice (buttons)**, **short text** and **long text**. An email question is a required part, so answers can be matched against your address book.

### Logic tab

Here you decide where answers lead:

- Up to **20 rules**, each checking answers against conditions. Rules are evaluated top to bottom: **the first match wins**. Order is priority.
- Three target types per rule: **open an event type** (the guest lands directly in the booking), **redirect to a URL** (an info page, say) or **show a message** (for example that you will get in touch personally).
- The fallback **In allen anderen Fällen** (in all other cases) applies when no rule matches. Nobody ever runs into a dead end.

### Answers tab

All submissions with the filters **all**, **booked** and **without booking**. Answers are matched against your address book; known contacts are recognized. Bookings made through a form carry their origin in the appointment detail.

<Callout tone="note" title="Automatic deletion">
Submissions without a booking are deleted automatically after 90 days. Data minimalism by default: what does not lead to an appointment does not linger forever.
</Callout>

## Active switch and edge cases

- Each form has an **active** switch. When off, the form is paused and the link shows a neutral notice page instead of the form.
- If a rule points to a **deactivated event type**, the fallback message applies automatically. Nobody ever lands on a page that cannot be booked.

## A practical example

1. Question 1 (choice, buttons): "What is this about?" with "I want to sell", "I am looking for a property", "Something else".
2. Rule 1: answer "I want to sell" opens the **valuation appointment** event type.
3. Rule 2: answer "I am looking for a property" opens the **viewing** event type.
4. In all other cases: show the message "Thank you! We will get back to you within one business day."

## Further reading

Back to the overview: [Appointment Booking](/tools/booking). Next page: [Analytics](/tools/booking/auswertung). You maintain the target event types under [Event types](/tools/booking/terminarten).