Webhook secret
Telegram sends a secret on every update. A mismatch is rejected.
Building a custom push system would have meant another app, another login, and another thing to check between trips. Telegram already sends a phone alert the moment a message arrives. New bookings, pickup reminders, and ride status go there. The phone app is still where the fare is confirmed and the invoice is written.
A secret on the webhook, and a list of driver chats. A random person who finds the bot is ignored. That list is how a small fleet shares the alerts without opening the account to everyone.
Telegram sends a secret on every update. A mismatch is rejected.
One chat or several. Alerts go to the whole list.
Set price, approve, and decline hit the same record. You can keep Telegram as a suggestion until the app confirms.
Start, today, upcoming, pending, and help. A new booking arrives with the route and the estimate, and buttons to set a price, approve, or decline.







Telegram is the interrupt. The PWA is the office. Longer forms, invoices, and the full booking chat stay in the app.
Complete asks how they paid. Directions go from here to pickup, then drop-off.
Reopen it to pending. Editing the trip and accepting after a call is in the phone app.
Invoices, manual trips, coupons, and the full booking chat. The bot links out.
We set up the bot as part of Driver. If your team lives in a different chat app, or the business is not a car service, Cedar Labs can build that notification path instead.