Calendly's routing form is conditional logic, not an AI agent

The setup

Calendly's routing forms are meant to replace a single static booking link with a short form: a visitor answers a few questions, and the answers decide which calendar they land on. Building one requires an owner or admin role — Calendly's own instructions for creating a Routing Form, updated 1 September 2026, note that only owners, admins, and group admins can create a form, though any user can view and share one once it exists. It is a Professional-tier feature and above; Calendly's plan documentation lists it under Professional, Teams, Teams Plus, and Enterprise.

What the documents show

The setup guide describes building a form with a set of questions, then a separate routing logic tab where an admin defines conditions using a question, a qualifier, and an answer, combinable with and or or. Each condition ends in one of three destinations: an event type, so a qualified visitor books directly with a specific person; a custom message, for a visitor who does not qualify; or an external URL. A fallback route catches anyone whose answers match nothing. Calendly's own Routing overview page markets this as connecting a lead to the right team member based on their skills or calendar, which is table-driven matching against form answers, not a described AI-reasoning step. Notably, Calendly's own product navigation lists Meeting routing and its separate Callie AI assistant as two different line items — the vendor's own materials do not describe routing forms themselves as AI.

The friction

Every route in this system has to be built by hand: a person defines each condition and its destination, and the guide recommends previewing and test-submitting the form before publishing, because responses typed during preview are not recorded. There is no described mechanism for the form to write or adjust its own routing logic from past outcomes; it runs exactly the conditions an admin set, which means a change in a team's structure or qualification criteria requires someone to go back into the routing tab and edit it.

What changed in the work

Before a tool like this, a static scheduling link sent every visitor to the same calendar regardless of who they were, and sorting them into the right person's queue happened after the fact, by a human triaging bookings. What the documents support is that routing forms move that triage earlier, into the form itself, using rules a team writes once. Labelled as editorial, calling this an AI routing agent overstates what the vendor's own pages describe: it is conditional logic connected to a booking calendar, and the destination is still always a human's calendar, never an automated decision about the visitor.

• Who on the team is responsible for updating routing conditions when roles or territories change?
• Does every condition have a defined fallback, or could an unmatched visitor land somewhere unintended?
• Has the form been tested in preview mode since the last time routing logic was edited?

Whatever a team calls this feature internally, Calendly's own documentation describes rule-based routing to a human calendar, not a decision made about the person filling out the form.