---
title: "What is a routing form?"
url: https://meet.barq.dev/glossary/routing-form
updated: 2026-11-17
author: "Hammad Ali"
---

# What is a routing form?

> **Short answer:** A routing form uses a visitor's answers to choose a booking destination, such as a particular representative or appointment type. It applies rules before the visitor picks a time. For example, two service choices can lead to two different booking pages; collecting answers alone doesn't create routing.


## How does a routing form decide where someone books?

A routing form matches answers against conditions you define, then sends the visitor to the matching destination. Ownership comes before availability. If an inquiry needs a specialist, the form should identify that specialist before offering appointments on a general sales calendar that can't handle the request.


1. Ask a question that changes who should handle the inquiry.
2. Match the answer to a destination or eligible host pool.
3. Offer times for that destination.
4. Provide a fallback when no condition matches.


Keep the rules readable. A form with twelve questions isn't necessarily better at routing than one with two; each question should change an assignment or provide information the eventual host needs.


For neighboring definitions, use the [scheduling terms index](https://meet.barq.dev/glossary/scheduling-glossary). Routing answers who should handle the request; availability answers when that person can meet.


## What happens to twelve inquiries in a routing example?

In a hypothetical two-service setup, seven installation inquiries go to an installation booking page and five support inquiries go to a support page. That's twelve destinations selected by service need. The example describes rule behavior, without claiming any measured improvement in bookings or response speed.


Suppose both pages offer 30-minute calls. Seven installation bookings would occupy 210 meeting minutes, while five support bookings would occupy 150 minutes, before buffers or cancellations.


Those totals aren't balanced. Equal distribution wasn't the rule: the selected service determined the destination, so unequal demand produces unequal meeting loads even when the form works exactly as intended.


## Is a routing form the same as round robin?

A routing form qualifies or directs a request; round robin distributes appointments among eligible hosts. They can be combined. A form could choose the support team, after which a rotation selects one available support representative according to that scheduler's assignment policy.


| Mechanism | Decision it makes |
| --- | --- |
| Routing form | Which destination should receive this inquiry? |
| Round robin | Which eligible host receives this appointment? |
| Booking question | What should this appointment's host know? |

Our [round robin definition](https://meet.barq.dev/glossary/round-robin-scheduling) explains why multiple calendars belonging to one host don't create a staff pool. Don't use a qualification question as evidence that another representative's availability has been checked.


## Does collecting answers in a booking page create routing?

No. Barq Meet collects custom booking questions for the chosen host, but those answers don't select a different representative automatically. We keep the appointment attached to its host. We can check several Google calendars for that person's conflicts; those calendars aren't a lead-assignment engine.


We also recheck availability when the guest submits, which protects the chosen time without changing who owns the inquiry or assigning it to someone else. If you need rules based on answers or CRM ownership, choose a product that documents those capabilities.


Chili Piper lists routing from web forms and CRM-based assignment in its [pricing information](https://www.chilipiper.com/pricing), as of 17 Nov 2026. Our [Chili Piper comparison](https://meet.barq.dev/compare/barq-meet-vs-chili-piper) covers that distinction without treating an individual booking link as a substitute.


Review [what an individual account includes](https://meet.barq.dev/pricing), or [make a link for inquiries you've already assigned](https://meet.barq.dev/app/sign-in).

## Frequently asked questions

### Can I route inquiries by asking for a company name?

A company-name field collects an answer, but assignment requires a rule that uses it. Decide what each answer should change, including a fallback, before assuming the form will send visitors to different representatives. Define and test the routing rule separately, because merely collecting a company name doesn't decide which person should own the resulting appointment.

### Should I ask qualification questions before showing times?

Ask before scheduling when the answer changes the responsible person or appointment. Questions that only help preparation can stay on the chosen host's booking form, so visitors aren't asked to complete the same information twice. Ask only for the information needed to decide the next step, leaving detailed discovery questions until the prospect reaches the correct owner.

### Does routing guarantee an equal share of meetings?

No. Routing can deliberately produce unequal totals because requests have different needs. Equal allocation among eligible people is a separate rule, and even that needs to account for who is available at the requested time. Review the assignment rules and eligible hosts, since qualifying an inquiry and distributing a balanced workload are separate decisions for the team.

## Related pages

- [What is round robin scheduling?](https://meet.barq.dev/glossary/round-robin-scheduling)
- [Chili Piper vs free Google Calendar scheduling](https://meet.barq.dev/compare/barq-meet-vs-chili-piper)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
