# Hi everyone, I’m building a WhatsApp-based taxi dispatch system (no mobile app for customers) **URL:** \ **Category:** Hire Help\ **Tags:** ai\ **Created:** [June 22, 2026, 6:57am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119 "2026-06-22T06:57:03Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Fast\_5](https://avatars.discourse-cdn.com/v4/letter/f/898d66/32.png) [@Fast\_5](https://community.make.com/u/Fast_5)\ **Post date:** [June 22, 2026, 6:57am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/1 "2026-06-22T06:57:03Z")
**🧩 What I need to build:** - Customers send pickup & destination via WhatsApp - System understands the message (AI parsing) - Automatic driver assignment (nearest available driver) - Real-time updates to customer via WhatsApp - Admin dashboard (manage drivers, trips, pricing) - Optional live tracking link (Google Maps) **⚙ Tools I want to use:** - [Make.com](http://make.com/) (automation core) - WhatsApp Business API (Cloud API or provider like Twilio / 360dialog) - Google Maps API - OpenAI (for address parsing) - Database (Airtable / PostgreSQL) **❓ What I need help with:** I’m looking for someone experienced in [Make.com](http://make.com/) to: - Design the full automation scenario - Suggest best architecture for WhatsApp + dispatch system - Possibly help build MVP or guide setup step-by-step **💰 Budget:** Open to paid help (freelance / consulting). If you have built something similar (WhatsApp automation, booking systems, dispatch/logistics flows), please reach out. ---
**Author:** ![TinyOpsStudio](https://avatars.discourse-cdn.com/v4/letter/t/7bcc69/32.png) [@TinyOpsStudio](https://community.make.com/u/TinyOpsStudio)\ **Post date:** [June 22, 2026, 7:17am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/3 "2026-06-22T07:17:11Z")
This post was flagged by the community and is temporarily hidden. ---
**Author:** ![Pathfinder\_Automate](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/pathfinder_automate/32/92144_2.png) [@Pathfinder\_Automate](https://community.make.com/u/Pathfinder_Automate)\ **Post date:** [June 22, 2026, 8:23am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/4 "2026-06-22T08:23:39Z")
Hello @Fast_5, Building a WhatsApp dispatch system without a mobile app is a smart move and totally doable in Make. A few architecture notes: use 360dialog over Twilio for cleaner WhatsApp Cloud API pricing and webhook handling. Route inbound messages into Make, then pass the text to OpenAI with a structured JSON output (function calling) to reliably extract pickup/destination. For driver assignment, store driver locations in PostgreSQL and use Google’s Distance Matrix API to find the nearest available one Airtable works for MVP but gets slow with live geo-queries. Trigger status updates back via WhatsApp templates as the trip progresses. I’ve built booking and dispatch flows like this before happy to design the full scenario or help you ship the MVP. ─── Website: [https://www.pathfinderautomationsolutions.com](https://www.pathfinderautomationsolutions.com) Upwork: [https://www.upwork.com/freelancers/pathfinderautomate](https://www.upwork.com/freelancers/pathfinderautomate) Book a call: [Calendly](https://calendly.com/taiwo-pathfinderautomationsolutions/30min) ---
**Author:** ![opspilotai](https://avatars.discourse-cdn.com/v4/letter/o/e95f7d/32.png) [@opspilotai](https://community.make.com/u/opspilotai)\ **Post date:** [June 22, 2026, 10:43am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/5 "2026-06-22T10:43:57Z")
This looks like a good fit for a small bounded MVP. I would keep the first slice very narrow: - WhatsApp intake for rider requests - one simple dispatch routing rule - logging to Google Sheets or Airtable - driver confirmation / status update - basic error handling and audit trail If you share your current flow and which tools you want to keep in v1, I can turn that into a fixed-price milestone proposal for a 1-3 day slice. Best, OpsPilot AI Studio ---
**Author:** ![Felipe-Aspirity](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/felipe-aspirity/32/53142_2.png) [@Felipe-Aspirity](https://community.make.com/u/Felipe-Aspirity)\ **Post date:** [June 22, 2026, 12:40pm UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/6 "2026-06-22T12:40:34Z")
Hi @Fast_5 this seems like a rally nice project. About WPP API, recently WPP has released Coexistence which makes it easier to connect and you wont need to get all the permissions and credentials from Whatsapp Business API, you can just connect your phone using a QR code. You would still need to set up some templated messages approved if you want to write to someone who has not engaged with your phone number before. I have build several AI agents running on WPP and would love to help. If you are interested you can schedule a call in here: [https://cal.com/aspirity/discovery?utm\_source=make](https://cal.com/aspirity/discovery?utm_source=make) discovery or check our website [www.aspirity.com](http://www.aspirity.com) ---
**Author:** ![mikedev](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mikedev/32/89712_2.png) [@mikedev](https://community.make.com/u/mikedev)\ **Post date:** [June 22, 2026, 1:15pm UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/7 "2026-06-22T13:15:13Z")
Hi, @Fast_5! This is a very achievable MVP and the architecture is quite straightforward. I would approach it as: Customer sends pickup and destination via WhatsApp → AI extracts and validates addresses → Google Maps calculates route and distance → system finds the nearest available driver → trip is assigned automatically → both customer and driver receive WhatsApp updates throughout the process. For the backend, I would use [Make.com](http://Make.com) as the orchestration layer, OpenAI for message understanding and address parsing, Google Maps APIs for routing and ETA calculations, and PostgreSQL for drivers, trips, pricing, and dispatch logic. For the admin side, I’d recommend a lightweight dashboard where you can manage drivers, monitor active trips, update pricing rules, and manually override assignments when needed. My focus is building the entire workflow architecture, reducing manual dispatch work, and making sure the system can scale beyond the initial MVP without requiring a rebuild later. I’ve built multiple AI automation systems involving LLMs, workflow orchestration, databases, lead routing, and operational automations, so this project fits well within my expertise. Happy to discuss the scope and provide a fixed-price proposal for the MVP once I understand a few details about driver volume, expected trip volume, and dispatch rules. Telegram: @hely\_chatbotshely\_chatbots WA: +375293761570 Portfolio: [https://mikedevai.netlify.app/](https://mikedevai.netlify.app/) ---
**Author:** ![Folafoluwa\_Olaneye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/folafoluwa_olaneye/32/91924_2.png) [@Folafoluwa\_Olaneye](https://community.make.com/u/Folafoluwa_Olaneye)\ **Post date:** [June 22, 2026, 8:27pm UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/8 "2026-06-22T20:27:17Z")
Hi Fast\_5, Welcome to the Make community. I’ve built automation systems involving WhatsApp integrations, AI-powered data processing, CRM workflows, APIs, and database-driven automations using [Make.com](http://Make.com) and n8n. For your use case, I’d recommend a Make.com-centered architecture with WhatsApp Business API, OpenAI for address parsing, Google Maps APIs for routing, and either Airtable or PostgreSQL depending on scalability requirements. I’ve attached a few relevant case studies and would be happy to discuss the MVP, architecture, and implementation approach. Website Portfolio: Click [here](https://mavin-collins.my.canva.site/flowedge-portfolio-website) to view my Portfolio website. Book a Call: Click [here](https://cal.com/folafoluwa-olaneye-osrofp/30min) to book a walkthough call session. Email: [folafoluwaolaneye@gmail.com](mailto:folafoluwaolaneye@gmail.com) Looking forward to connecting. Folafoluwa Olaneye [AI-Powered Telegram Community Management System.pdf](https://community.make.com/uploads/short-url/8g2u6T2uKDAAlRYFum2gcA0te32.pdf) (260.6 KB) [Amazon Price Monitoring & Competitive Intelligence System.pdf](https://community.make.com/uploads/short-url/2Ohx2nUvL4JJ8AVBIR44KlDDusr.pdf) (280.9 KB) [Automated Document Processing & Approval Workflow.pdf](https://community.make.com/uploads/short-url/p19CvXrtEOAAHnhtqmi5Jt3tAZ0.pdf) (138.6 KB) ---
**Author:** ![Thomas\_Cloarec](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@Thomas\_Cloarec](https://community.make.com/u/Thomas_Cloarec)\ **Post date:** [June 30, 2026, 5:46am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/9 "2026-06-30T05:46:16Z")
Hi @Fast_5, I can help scope and build a narrow paid MVP slice for this. I would start with WhatsApp intake, OpenAI address parsing to JSON, one driver assignment rule, Airtable or PostgreSQL trip logging, customer status updates, and error handling before a full dashboard. What driver volume are you expecting at launch, what assignment rules matter first (nearest only, zones, driver status, manual override), and do you prefer Airtable or PostgreSQL for v1? Best, Thomas ---
**Author:** ![Yvoo\_Lab](https://avatars.discourse-cdn.com/v4/letter/y/c2a13f/32.png) [@Yvoo\_Lab](https://community.make.com/u/Yvoo_Lab)\ **Post date:** [August 3, 2026, 10:56am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/10 "2026-08-03T10:56:36Z")
Two architecture points will make or break this before any scenario gets built: State does not belong in Make. “Nearest available driver” is a question your database answers, not your automation — driver status, live trips, and assignment locks need one source of truth — a database you own (Airtable or Postgres both work) — with Make orchestrating around it. If availability lives implicitly in scenario logic, two simultaneous bookings can end up assigned to the same driver. WhatsApp’s 24-hour session rule shapes the customer flow. Inside a session you can free-form reply; outside it (status updates, tracking links sent later) you need pre-approved template messages. The message design has to be split along that line from day one or the update flow silently fails in production. The MVP slice I’d propose: booking intake with AI address parsing, DB-backed assignment, confirmation + one status update — dashboard and live tracking as phase two once dispatch is trustworthy. I work fixed-price per deliverable with a written architecture note first, async, CET, written briefs over meetings. ---
**Author:** ![Ahmed\_Habib](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@Ahmed\_Habib](https://community.make.com/u/Ahmed_Habib)\ **Post date:** [August 31, 2026, 6:54am UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/11 "2026-08-31T06:54:17Z")
Hi If this opportunity is still open, I’d be interested in implementing a small, clearly scoped paid MVP milestone first. My practical experience includes Make workflows, webhooks and API integrations, Supabase/PostgreSQL, authentication, CRM and operational workflows, dashboards, error handling, and AI-assisted engineering with manual testing and validation. To be transparent, I have not previously delivered this exact taxi-dispatch product. However, the underlying components match systems I have worked with: structured data intake, workflow routing, database state, API integrations, operational dashboards, and audit/error tracking. I suggest starting with one bounded milestone: • Receive a test booking request • Parse pickup and destination into structured JSON • Store the booking in PostgreSQL/Supabase • Apply one simple driver-assignment rule • Log the decision and send a test confirmation • Add basic duplicate and failure handling We can initially test the workflow without production WhatsApp or paid API credentials. After you verify the functional flow, we can agree on the production integration, scope, price, and external API costs. If the project is still available, please share your current progress and preferred WhatsApp provider. ---
**Author:** ![faraz\_shah](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/faraz_shah/32/93437_2.png) [@faraz\_shah](https://community.make.com/u/faraz_shah)\ **Post date:** [September 2, 2026, 12:30pm UTC](https://community.make.com/t/hi-everyone-i-m-building-a-whatsapp-based-taxi-dispatch-system-no-mobile-app-for-customers/111119/12 "2026-09-02T12:30:52Z")
Hi, I’m Faraz, a full stack JavaScript developer (Next.js, TypeScript, Node, Postgres).Saw your WhatsApp dispatch post. Straight answer on architecture, since you asked for one: the dispatch core should not be Make. Nearest-driver assignment and live trip state is a job for a small Node service on Postgres. Make is fine around the edges, notifications and admin alerts, but a real-time dispatch system built on scenarios will break in ways that are hard to debug. WhatsApp Cloud API + Node + Postgres + a Next.js admin dashboard is the version that holds up, and it’s what I build daily. I run my own SaaS, Parhako, solo for 3 years. On Upwork: 5 stars on every contract, $12k+ earned, one ran 942 hours. My minimum for an MVP build is $3,000 USD. If that works, reply with a yes and a short description of what you want in the first version, and we can do a Google Meet to scope it. Faraz Shah > **[faraz-35 - Overview](https://github.com/faraz-35)** > > Full Stack Web & Mobile developer. faraz-35 has 41 repositories available. Follow their code on GitHub. [https://www.linkedin.com/in/s-m-faraz-shah-4639291b2/](https://www.linkedin.com/in/s-m-faraz-shah-4639291b2/)