Page Content and Behavior
Two tabs cover everything around the form itself. Content is the words on the page. Behavior is what happens once the visitor is done with it. Both are optional — a page with neither configured still works, using your company name and Driive's defaults.
Content
Open the Content tab. Every field here falls back to a sensible default when you leave it empty, and the placeholder text tells you what that default is.
| Field | Where it appears | Default |
|---|---|---|
| Page title | The heading at the top of the page | Your company name |
| Intro | A line under the heading | Nothing |
| Contact form title | Above the contact details step | "Your details" |
| Contact button text | The button that submits the contact form | "Continue" |
| Thank you message | Shown when the request needs your team to confirm it | "Thanks! We'll see you soon." |
Writing the heading and intro
The page title is the first thing a visitor reads, and it's also what search engines and link previews use. Your company name is a fine default for a general page — but for a targeted page, something specific does more work:
| Page | Title | Intro |
|---|---|---|
| Main page | Acme Roofing | Book online in under two minutes. |
| Free estimate | Free Roof Estimate | No obligation, no pressure — we'll tell you what we'd do and what it costs. |
| Maintenance | Schedule Your Annual Service | Pick a time that works. We'll confirm by text. |
The thank you message
This one only shows on a specific path: when the customer finishes the form but the request can't be booked on the spot — the appointment type requires approval, the lead didn't meet your qualification threshold, or the address falls outside your service area.
It's worth writing deliberately. The customer just did everything you asked and didn't get a time, so tell them what happens next: "Thanks — we've got your request. Someone from our office will call within one business day to confirm your appointment."
Tip: Customers who can book straight through never see this message. Don't put anything essential in it.
Behavior
Open the Behavior tab.
Bot protection
On by default. Visitors pass a Cloudflare security check before their submission goes through, which keeps junk requests out of your Issues list. Most people are verified invisibly and never see a thing.
One thing worth knowing: a link that pre-fills and auto-submits the form can't submit silently on a protected page — the visitor sees the form and one confirming click instead. If you use auto-submitting links from a CRM, that's the trade-off. Leaving protection on is still the right call for any page reachable from the open web.
Redirects
By default, a customer stays inside Driive after booking — landing on their own confirmation page where they can add the appointment to their calendar, reschedule, or cancel. Two fields override that and send them to a page of yours instead:
| Field | Fires when |
|---|---|
| Redirect after request | The request was submitted but still needs your team to confirm it |
| Redirect after confirmation | The appointment was booked and confirmed on the spot |
These are the hooks for conversion tracking — point them at a thank-you page carrying your analytics or ad-platform pixel. UTM parameters and custom fields from the original booking link are appended automatically, so attribution survives the round trip. See Booking Links and Sharing.
Set here, these override the equivalent redirect URLs on the appointment type, which means a campaign page can report to its own landing page without touching your other pages.
Note: Redirecting away means the customer never sees their self-service confirmation page. Make sure your own thank-you page includes the appointment details — or link back to the confirmation link from the email.
Terms and privacy links
Both fields feed the consent text under the contact form. Leave them empty and the page links to its own generic terms and privacy pages; fill them in and it links to yours.
If you collect phone numbers, filling these in is worth the two minutes. SMS consent is more defensible when the consent text points at your actual policy.
All four fields need a full URL starting with https:// or http:// — the field tells you inline if the URL isn't valid.
What's next
- Branding Your Booking Page — Logo, colors, and trust badges.
- Booking Links and Sharing — URL parameters and attribution passthrough.
- Notifications — The emails and texts customers get after booking.
- How Customers Book — See this copy in context.