Webhook secret
X-Telegram-Bot-Api-Secret-Token verified on every update.
Product · Telegram bot
Dispatch where drivers already respond
The bot is the interrupt path: new requests, fare decisions, status changes, morning summaries, and pickup reminders. UI frames below mirror production message builders with Gotham Limo synthetic data.
Security model
Fail-closed. Random Telegram users are ignored silently.
Chat allowlist
One or many driver chat IDs. Alerts fan out to the full list.
Shared lifecycle
Approve/reject/set-price uses the same server actions as the PWA.
Workflow gallery
Commands: /start · /today · /upcoming · /pending · /help
Welcome for allowlisted drivers. Menu button + reply keyboard: Today, Upcoming, Pending, Help.
Push-native request with route, estimate, passenger, notes. Approve · Reject · Set Price.
ForceReply fare entry, then approve with the locked final fare.
Each request as its own card. Fare shown once set.
Morning-style schedule plus per-ride complete / no-show / cancel.
Seven-day outlook; tap through for detail actions.
Cron-driven 15- and 5-minute pickup reminders to all allowlisted chats.
What stays in the PWA
Telegram is optimized for decisions and glances—not multi-step forms.
Invoices
Bot links out; full invoice form lives in the PWA.
Manual bookings
Phone-ins and walk-ins are created in Add trip.
Deep edits
Post-create trip field edits and coupon admin are PWA-side.
Add Telegram ops to your fleet
We configure the bot, allowlist, and webhooks as part of Driver.