What’s new

Your office. Their office. One chat.

The RideBits team
Nov 5, 2026

You sent Friday’s 4:10 airport pickup to Northside, a partner you trust. At 1:30 the flight slips two hours. You need one answer.

Getting it used to mean calling whoever accepted the trip and hoping they were working that day. Now you open the trip and tap Message Northside. The chat opens with that trip already in the message. You type “Can your driver wait?” and send.

Every admin and staff member at Northside is notified, and whoever is on answers. You never need to know who’s at the desk. Four minutes later your phone lights up. Northside. “Sam Reyes: Yes, we’ll wait.”

The trip sits under your words as a card, with the facts you read on your board all day: the pickup, the time, where the trip stands. On your side it’s trip #1042. On theirs it’s their own number for the same trip, and a tap opens their own copy. Nobody reads a number over the phone. The card keeps up with the trip too. When the ride is finished it reads Completed, and you never had to ask.

While someone at Northside has RideBits open, the top of the chat reads Someone’s on now. When nobody does, it says nothing at all.

It’s one chat per partner, with both offices in it, and staff who join later can read all of it. Drivers aren’t in it. Clients aren’t either. On RideBits the conversation stays attached to the work, and this one is office to office: your client sees their trip and their driver, and none of what it took behind the scenes.

Partner chat is in your Inbox, in the RideBits app and the Console.

Part of Conversations

The conversation comes with the work.

← What’s new ← All posts