Customer, driver and dispatcher in one workflow
Orders arrive through Telegram, drivers record trip events, and dispatchers control assignment and pricing. Manual adjustments remain in the history.
- 01Request
- 02Dispatch
- 03Driver
- 04Trip
Who it is for
Dispatch teams, transport operators and chauffeur services.
What it enables
Each participant sees their actions and order status in a familiar channel. Pricing connects to routes, waiting and trip events, while amount changes require a reason. The system provides a basis for controlled dispatch; licensing and commercial rollout remain separate steps.
Automate private trips and chauffeur hire while preserving dispatcher control over assignment and final pricing.
- Three roles operate in Telegram with different data and actions.
- Final pricing depends on route, waiting and real trip events.
- A live operation still requires local licensing, contracts and policy work.
- Customer, driver and administrator bot flows with explicit state transitions.
- Mini App map and server-side route calculation.
- Adjustment audit, completed-trip history and a financial model.
04 System scope
What was designed and built
Three Telegram interfaces
Route-selection Mini App
Dispatch and financial workflow
05 Verified scale
Route, stop, wait-time and hourly-hire calculation
Role-based states and geo events for start, wait and finish
Order history and reasons for manual adjustments
Three-role workflows, order and fare model, Mini App, event log, CRM capabilities and safe deployment.