# Destinations

Every [routing rule](/help/routing-forms/routing-rules) ends at a **destination** — the
place 42min sends people whose answers matched that rule. There are four kinds.

<Screenshot
  src="/help/screenshots/routing-forms/destinations.png"
  alt="The Rules tab of the 42min routing-form builder: a rule with a Condition block, a Destination dropdown set to 'Event Type' with a 'Select event type...' picker below it, and the Default Rule below set to 'Custom Message' with the message text"
  caption="On every rule (and the Default Rule at the bottom), the Destination dropdown picks the type — Event Type, External URL, Custom Message, or another routing form — and the field directly below it is whatever that type needs."
/>

## The four destination types

- **Event type's booking page** — forward the person to one of your
  [event types](/help/event-types/overview) so they can pick a time. The most common
  destination: "enterprise leads → *Talk to the enterprise team*", "everyone else →
  *Intro call*". The answers they gave on the routing form travel with the booking, so
  the host sees the context.
- **External URL** — send them to any web address — a pricing page, a help article, a
  WhatsApp link (`https://wa.me/...`), a typeform, your support portal. Use this for
  "doesn't need a meeting" or "handled by another tool".
- **Custom message** — show a short message on the page instead of forwarding anywhere
  (e.g. *"Thanks — we only support customers in North America right now. We'll let you
  know when that changes."*). Good for politely turning someone away, or for "we'll
  email you".
- **Another routing form** — hand the person off to a *second* routing form, which then
  asks its own questions and routes again. This lets you build a decision tree: a short
  top-level form ("What do you need?") branching into specialized forms ("Sales →" /
  "Support →"). Each form's answers are kept as the chain progresses.

## How to do it

1. On a rule (on the form's **Rules** tab — [open the builder](/360/routing?new=1)),
   choose the **destination type**.
2. Fill in what it needs: pick the **event type**, paste the **URL**, type the
   **message**, or pick the **routing form** to chain to.
3. Do the same for every rule, including the **fallback**.
4. Save, then walk each path on the public link to confirm it goes where you intend.

## Common pitfalls

- **Linking to a turned-off event type.** If a rule points at an event type that's
  switched off, people who land there see "not available". Keep destination event types
  on, or point the rule elsewhere.
- **External URL typo.** An external-URL destination is only as good as the address —
  test it; a broken link is a worse dead end than a custom message.
- **Chained forms with weak fallbacks.** Each form in a chain has its own mandatory
  fallback. A solid first form routing into a second form whose fallback is empty still
  produces a dead end — give every form in the chain a real fallback.
- **Loops.** Don't route Form A → Form B → Form A. Chains should always make progress
  toward a final destination.