Skip to content
Driive Help Center home

Creating a Booking Page

Creating a booking page takes two fields: a name and a URL. Everything else — questions, routing, copy, branding — is configured afterward in the page editor, so you can get a page on the board in a few seconds and shape it over time.

Create the page

  1. Navigate to Setup > Booking Pages.
  2. Click New booking page.
  3. Enter a Name. This is internal — it's the label on the card in your dashboard, not the heading customers see.
  4. Check the URL slug. Driive suggests one from the name as you type, and you can edit it freely.
  5. Click Create page.

Driive drops you straight into the page editor with the page saved as a Draft.

Picking a URL

Your page lives at book.getdriive.com/{slug}, so the slug is the part your customers will actually see, type, and read out loud.

The rules:

  • Lowercase letters, numbers, and hyphens only — no spaces, no underscores, no leading or trailing hyphen.
  • Between 2 and 63 characters.
  • Unique across all of Driive, not just your company.
  • A short list of reserved words (like book, admin, api, and app) can't be claimed.

The field checks availability as you type and tells you which of those it hit — already taken, reserved, or not valid — so you'll know before you submit.

Good slugs:

SlugPublic URL
acme-roofingbook.getdriive.com/acme-roofing
free-estimatebook.getdriive.com/free-estimate
spring-tuneupbook.getdriive.com/spring-tuneup

Tip: Keep it short enough to say on a phone call. A slug you can read to a customer without spelling it is a slug that works on radio, yard signs, and voicemail.

Build it out

With the page created, work through the tabs. A reasonable order:

  1. Form — add your questions and routing rules, or set a default destination if this is a single-service page. This is the only tab a page genuinely needs.
  2. Content — write the heading, the intro line, and the thank-you message.
  3. Design and Reputation — customize the branding if this page shouldn't just inherit your company look.
  4. Behavior — add redirects and legal links if you have them.

Changes across every tab accumulate into a single draft. Save changes commits all of them; Discard throws all of them away. If you try to navigate away with unsaved work, Driive stops you and offers to save first.

Publish it

Click Publish in the page header. That's the whole step — there's nothing to deploy and no cache to wait on.

Before publishing, a page is invisible to the public: its URL shows the "booking unavailable" screen, and Preview is disabled with a note explaining why. After publishing:

  • Preview opens the live page in a side panel. Preview submissions don't create real requests, so you can walk the whole flow as a customer without cleaning up afterward.
  • Open page opens the real public URL in a new tab.
  • Copy URL in the ⋯ menu grabs the link for sharing.

Tip: Walk every path in Preview before you share the link — every option on every question, all the way to a time picker or an external redirect. Routing mistakes are invisible in the builder and obvious to a customer.

Renaming, unpublishing, and deleting

Rename

The General tab holds the page's name. Renaming is purely internal — it changes the card in your dashboard and nothing a customer sees.

Change the URL

You can edit the slug on the General tab too, but it breaks every existing link to the page — anything you've texted, embedded, printed, or handed to an ad platform. Driive warns you inline when you edit a saved slug. If a page is already out in the world, it's usually better to create a new page than to move an old one.

Unpublish

Open the ⋯ menu and choose Unpublish. The URL stops resolving immediately, and the page returns to Draft with its whole configuration intact. This is the reversible way to take a seasonal or campaign page offline.

Delete

Delete from the ⋯ menu or the bottom of the General tab. Deleting is permanent and frees the slug. Appointments and requests already booked through the page are not affected — they live on the appointment and customer records, not the page.

How many pages should you build?

Start with one. Add another when a specific audience needs a genuinely different experience:

PageWhy it's separate
Main booking pageLinked from your website nav; asks the full set of routing questions
Free estimateA paid-ads landing page with no questions — straight to the estimate type
Existing customersMaintenance and warranty services only, sent by text
Storm responseSeasonal, unpublished the rest of the year

Every page reports into the same Requests list and the same calendar, so more pages don't mean more places to check.

What's next