Page Questions
The Form tab is where a booking page gets its personality. It's laid out as a numbered flow, top to bottom, in the order a visitor moves through it: your questions first, then the page's default destination, then the contact information you collect. What you build here decides whether the page feels like a service menu, a guided questionnaire, or a single "book now" form.
Adding a question
- Open the booking page and go to the Form tab.
- Click Add a question — the dashed slot at the end of the flow.
- A question card appears. Click it to expand and configure it.
New questions arrive as a two-option Choice question, ready to rename. Reorder them with the up and down arrows on the left of each card, and delete one with the trash icon. Deleting a question also cleans up any routing rules that referenced it, so you never leave a rule pointing at nothing.
Question types
Every page question is a pick-one-or-more question. Free-text and photo questions belong on the appointment type, where they're asked after routing — see Booking Questions.
Choice
A single-select question. The visitor picks exactly one option.
Use it for the branching decisions that drive routing: "What kind of service do you need?", "Is this residential or commercial?", "Is this an emergency?"
Multi choice
The visitor can pick several options.
Use it when more than one answer can be true at once: "Which areas need work?", "What have you already tried?" Multi-select answers work with the contains family of routing conditions rather than a plain equals.
Services
A single-select question rendered as a grid of service cards instead of a plain list. Each option gets an icon, a label, and an optional description — so a visitor sees what you offer laid out like a menu.
This is how you build a service-list page. Add one Services question, give each option a card, and point a routing rule from each option to the matching appointment type.
Tip: Service card descriptions are marketing copy, not internal notes. "Full roof inspection with a written report, usually about an hour" beats "ROOF-INSP-1".
Question settings
Expand a question card and you get:
| Setting | What it does |
|---|---|
| Question Label | What the visitor reads. Write it the way a customer would ask it. |
| Question Type | Choice, Multi choice, or Services. Switching type keeps your options. |
| Required | On by default. When off, the visitor can continue without answering — the answer then routes nowhere and they fall through to the next step. |
| Options | The answers available. Every question needs at least two. |
| Help Text | An optional line of context under the question. |
| Routing Rules | Where each answer sends the visitor. See Routing Rules and Destinations. |
A question with no routing rules shows an amber No rules badge on its card. That isn't an error — everyone who answers it simply continues to the next question, or to the page's default destination if it's the last one. It's a reminder that the question is collecting information, not making a decision.
Contact information
The last card in the flow is Contact Information — the form every visitor fills out before Driive creates their request. Click the card to expand it.
First and last name are always collected. They're not configurable, because a request without a name isn't much of a lead.
Everything else is a three-way choice:
| Field | Options | Notes |
|---|---|---|
| Phone number | Required / Optional / Hidden | SMS consent only appears while the phone field is visible. |
| Email address | Required / Optional / Hidden | Used for booking confirmations and reminders. |
| Description | Required / Optional / Hidden | A "describe what you need help with" text box. Lands on the request as its summary. |
Phone and email can't both be hidden. Driive needs a way for you to reach the customer back, so hiding one pins the other to visible and explains why inline.
Choosing your fields
- Both phone and email required is the default and the safest — reminders go by text, confirmations go by email.
- Phone required, email optional cuts friction on mobile-heavy traffic, at the cost of some email deliverability.
- Turn on the description when the page is a general "contact us and book" front door. It gives your team the customer's own words, which is often worth more than three dropdown answers.
Tip: Every field you add is a chance for someone to give up. Ask for what you'd actually use before the visit, and let the technician ask the rest on site.
Forwarding answers into your appointment types
Here's a common annoyance: your page asks "Which areas need work?" and then the appointment type asks something nearly identical after routing. The visitor answers the same question twice and wonders whether anyone's paying attention.
Expand a question card and open Pass this answer into booking questions to fix that. For each appointment type the page can route to, choose which of that type's booking questions this answer should prefill — or leave it on Don't pass.
What can map to what:
| Page question type | Can prefill |
|---|---|
| Choice | A single-select, multi-select, or text question |
| Multi choice | A multi-select question |
| Services | A multi-select question |
If a type has no compatible question, the card says so rather than offering a broken mapping.
Translating option values
Your page's options and the appointment type's options rarely use identical wording. When you pick a target question, Driive matches them up automatically wherever the labels or values line up, and shows the result as green pills — Roof → Roofing.
Anything it couldn't match is flagged in amber as won't be passed, with a dropdown to map it by hand. Leaving one unmapped is fine; that particular answer just isn't forwarded.
Text targets need no mapping at all — the answer text is passed through as-is.
What's next
- Routing Rules and Destinations — Turn answers into destinations.
- Page Content and Behavior — Write the copy around the form.
- Booking Questions — The questions asked after routing, on the appointment type itself.
- How Customers Book — See the form in the context of the full journey.