Two camps, and the businesses caught between them
Scheduling software tends to pick a side.
One camp is the instant booker. Here's my calendar, grab a slot, done. It's fast and it's frictionless and it's perfect right up until the meeting is the kind you'd actually like to look at before it lands on your day.
The other camp is the request form. Tell us what you need, and we'll be in touch. It respects that some meetings deserve a human glance first — and it pays for that respect with a two-day lag and a follow-up that quietly goes cold in someone's inbox.
Most real businesses live in both camps in the same week. The quick consult should just book. The custom job walk-through should get a look first. Forcing one tool's philosophy onto both kinds of meeting is how you end up with a fast path that books the wrong things and a slow path that books nothing at all.
So we didn't pick a camp. We put both behind the same field and let you choose per meeting.
The meeting tells you which one it wants
Here's the test I'd use, sitting across from someone who runs the business.
If you'd be happy for this meeting to appear on your calendar with no human in between — a discovery call, a 20-minute intro, anything where your open time is genuinely up for grabs — that's auto mode. The visitor sees your real availability, picks a slot, and it books on submit. Calendar event, video link, confirmation emails, all of it, before they've left the page.
If you'd want to read the request first — a site visit, a custom quote, anything where you'd glance at the ask before committing an hour — that's propose-back. The visitor says when they're free, your team picks up to three times that fit, and the visitor confirms one with a single click. A person stands at the gate. The booking still happens in two clicks instead of a two-day email thread.
Same field, same calendar underneath. The meeting decides which path it wants.
The part that makes both of them work
There's an unglamorous piece holding all of this up, and it's worth saying out loud, because it's the part most scheduling bolt-ons skip.
A form has owners. You assign staff to it — a person, or a whole department or team in one move — and those people are the ones the form answers to. They get the notification. They manage the submission. They can turn it into a job. And their real calendars are the ones a meeting books against.
That's why auto mode knows whose Tuesday is open, and why propose-back knows who to ask. It's not a scheduling setting bolted to the side. It's the same routing that sends an HR form to HR and a service request to the install manager. Scheduling just happens to be one of the things that good routing makes possible.
The fast meetings should book themselves. The careful meetings should get a careful look. You shouldn't have to run two tools, in two tabs, to get both — and now you don't.
Related: how a form books the meeting before the visitor closes the tab.