Messaging

Every trip has its own thread

A conversation is created with every booking. The client is in it from the start; the assigned driver joins when they take the trip (and comes off if you reassign); and everyone on your team can see every trip thread — you join in one tap when you want to speak. The thread also keeps the record: booking created, driver assigned, changes requested and approved — all posted as cards in place.

The driver reads the thread from the moment they join it — what was said before stays between you and the client, unless the driver is one of your team, who see all of it. Only the client's and the driver's phone numbers are shared in it, so the chat's Call button reaches one of them, never a teammate's phone unless they're the one driving.

When a trip finishes, its thread stays readable but closes to new messages a day later — post-trip questions belong in the client's Help line, so old trip threads don't become support queues.

The Help line

Separate from any trip, each client gets a direct Help conversation with your company — think of it as your front desk in the app. Your whole team sees it, the first person to reply handles it, and you can mark it resolved (the client just sees the conversation; writing again reopens it). Your team's phone numbers are never shared there — clients reach you by chat. You can set the expectations line clients see when they start one ("we typically reply within a few hours") — and if you'd rather not offer client chat at all, the RideBits team can switch it off for your account.

Visitors

People can also write to you from your public booking page or your own website's chat widget — before they have an account at all. Those conversations land in your inbox under a Visitors filter, numbered per visitor. Replies wait for their return visit (visitors aren't notified), and idle visitor threads tidy themselves away after 30 days.

Photos, PDFs and links

Anyone in a conversation can send a photo, a screenshot or a PDF — an invoice, an itinerary, a quote — from the attach button, and on the web you can paste a screenshot straight in. Photos up to 10 MB, PDFs up to 20 MB, one per message. Visitors receive what you send them but can't send files themselves. Links turn into a tappable preview card, and a long press copies a message, a number or a link.

A message with no signal waits — a small clock beside it — and sends itself when the connection returns; it only says Not sent when it was refused, such as in a trip thread that has closed. Someone on an older version of the app sees a photo or a PDF as a short line with an Open link that opens it in their browser.

Notifications

Messages push to everyone in the thread except the sender — nothing to set up. Drivers get actionable pushes for offers ("ride now" and scheduled) that open straight to the decision screen. You're never notified about your own actions.