Your booking page
One page, live from day one
Your public page — ridebits.app/yourname — is where clients land from your links and QR code. From it they can book (seeing your real prices when automatic quoting is on), chat with you, or get the app. It exists the moment you pick your handle — nothing to build or host.
Make it yours
The page writes itself from how your company is set up — services, vehicle classes, prices — so it never claims something you don't offer. On a computer it opens straight into booking, with your company's name and a code for the app beside the form; on a phone it leads with the app and offers booking on the web underneath. In Settings → Your booking page, set the title and description used when your link is shared around — that's what shows in a message preview. The headline, intro and rows on that screen appear only on the computer version while web booking is switched off. Preview opens the real page on your phone.
The people on your page
Your drivers' faces are the one thing a ride-hailing app can't put on its page — it doesn't know who's coming. You do. Once a driver has a photo (they add it from their Profile, or you add it from their page under Drivers), a few faces appear under your company's name, each opening a short bio you write about them. With more drivers than fit, the page shows a different few each day. A single driver — or a solo operator — shows as one face. No names show until a face is tapped — then a first name and last initial with the bio, never a phone number. From each driver's page you can keep them off the booking page while their photo still shows clients who booked with them; Settings → Your booking page has the switch that turns driver photos off for your company altogether, and one that asks drivers for a photo until they add one. Nothing shows until a photo exists — never an empty circle.
Chat with visitors
People browsing your page can start a conversation before they have an account — those land in your team's inbox under a Visitors filter. Visitor chat is on out of the box; the switch lives on the same settings screen. Replies wait for the visitor's return — they're never notified, so a slow reply is never a broken promise.
On your own website
Already have a site? One script line puts the same booking-and-chat launcher on it — a button with a real action ("Book a trip"), not an anonymous chat bubble. The app has the exact snippet ready under your booking page's chat settings, with a Send to developer action that shares a plain install page. Your developer can open it as a corner panel instead of a centred card, or hide the floating button entirely and use your own Book buttons — the install page covers both. And ridebits.app/yourname/chat is a real link you can put anywhere — an email signature, a WhatsApp status — widget or no widget.
Your booking terms
Under Policies on the same screen, write the terms your business runs on — cancellation policy, wait time, luggage — and publish them. From then on, clients agree to your terms as part of booking, and every trip keeps a record of exactly what was agreed and when.