I’m building a full-cycle taxi booking experience that lives entirely inside WhatsApp, covering the passenger flow, driver workflow, and a light admin back office. Passenger flow Users should trigger a ride request with a simple keyword, share their live location, receive a distance- and time-based fare estimate, then follow real-time updates—driver found, on the way, trip started, trip finished—right in the same chat. They must also be able to cancel or reach support at any point. Driver flow Drivers will register through WhatsApp, be manually activated, and toggle online/offline status with one tap. Incoming jobs must show pickup, drop-off and fare; the driver replies to accept or decline. Start and end-of-trip messages update the system and generate an earnings summary that is pushed back to the driver. Admin panel A simple web panel (or easily consumable API endpoints) is enough: view key ride statistics, search or deactivate users, and see live ride status. No need for deep analytics or complex integrations at this stage. Core logic requirements • Fare calculator: distance + time (no surge for now) • Matching engine that assigns the nearest available driver, handles timeouts/rejections, and retries sensibly • All notifications and interactive prompts must be WhatsApp messages—no SMS or email paths • Graceful handling of driver blocks, passenger no-shows, and automatic inactive-user cleanup Deliverables 1. Well-structured source code (preferably Node.js or Python) with clear README 2. Deployed bot running on the official WhatsApp Business API (Cloud API or Twilio) 3. Admin panel or documented endpoints with minimal front-end 4. Postman collection / Swagger docs for every endpoint 5. Short hand-off session and two weeks of bug-fix support Acceptance criteria • Passenger can complete an end-to-end booking and see accurate fare before confirmation • Driver can accept, start and finish a trip, with earnings calculated correctly • Admin can view live rides and disable any user instantly • All interactions occur through WhatsApp without fallback channels If you’ve shipped conversational commerce or on-demand logistics bots before and can move fast while keeping code maintainable, let’s talk timelines and milestones.