Forms and meeting booking

A form and a calendar in two different places is two drop-off points, and the gap between them is where inbound meetings die. Someone answers five questions, presses submit, and lands on a page promising that you will be in touch, which is a different mood and a different day from the moment they were ready. Putting the slot picker at the end of the same page removes the second click and keeps the intent. It also keeps the answers attached to the meeting, so whoever takes the call starts informed instead of asking the same five questions again. Use the questions for routing rather than for filtering: on inbound, qualification that turns people away is usually saving time nobody measured. Round-robin assignment decides who takes the call without anyone arbitrating by hand, and it is also how you know later who actually held it. One trap worth knowing before you ship anything: hidden fields fed from URL parameters can arrive carrying the literal string undefined when the parameter is missing, so every rule reading them must test for the exact values you expect and reject everything else. Expect a free tier that covers a small operation outright, then fifteen to seventy-five dollars a month metered on responses, with seats unlimited.

What to decide before you look at any tool

The choice here is narrower than the category name suggests. You are really deciding whether the form and the calendar live in the same object or in two tools stitched together, and whether your routing questions are written for the person answering or for the person receiving. I run these on client accounts and I pay for them myself, and the pattern I keep coming back to is the one described in Qualify and book on one page: the second click that costs you meetings: the slot picker belongs at the end of the same page as the questions, not on a page after it.

Where Fillout fits

Fillout is built around that single-object idea: the form and the booking page are one thing, so a submitted answer becomes a meeting without a second tool in the middle. That matters less for the form itself and more for what happens after, because the answers stay attached to the meeting and whoever takes the call starts informed. If your intake questions feed a routing rule rather than a rejection rule, this is the shape of tool you want. The same reasoning applies to how you structure the workspace behind it, which is the subject of One workspace per client: what changes when the CRM stops being shared.

What the tiers actually cost

The free tier covers 1,000 responses a month with unlimited forms and seats, which is enough to run a small operation outright. Past that, the Starter plan is 15 dollars a month billed annually (180 a year), or 19 billed monthly, for 2,000 responses a month and all question types. Pro is 40 dollars a month billed annually (480 a year), or 49 billed monthly, for 5,000 responses a month with branding removed and custom CSS. Business is 75 dollars a month billed annually (900 a year), or 89 billed monthly, for unlimited responses and the advanced controls.

Plan	Monthly price	Annual price	Included
Free	0 dollars	0 dollars	1,000 responses a month, unlimited forms and seats
Starter	19 dollars a month	180 a year (15 a month)	2,000 responses a month, all question types
Pro	49 dollars a month	480 a year (40 a month)	5,000 responses a month, branding removed, custom CSS
Business	89 dollars a month	900 a year (75 a month)	unlimited responses and the advanced controls

What to measure on your own side

Before you pick a tier, count the only thing these prices meter: responses. A month of real inbound traffic through one client intake form is usually far below the free ceiling, and the paid plans only start to matter when several client accounts push forms through the same workspace. That is also the moment to reread CRM for agencies: the number to read before you pick one, because the metered quantity and the workspace structure decide the bill together.

The check before you ship

Whatever you choose, the failure mode is the same and it is not about price. Hidden fields fed from URL parameters can arrive carrying the literal string undefined when the parameter is missing, and any rule reading them will route on garbage. Every rule must test for the exact values you expect and reject everything else. Write that test before your first campaign, not after the first misrouted meeting.