Here's a breakdown of the platform building blocks a taxi-service bot is made of: order intake, rates, working with drivers, and ride payment.
| Task | How it's handled on the platform |
|---|---|
| Order intake (pickup, destination) | A regular message dialogue, or an AI agent that collects the pickup and destination addresses as text |
| Rates and ride cost | Fixed zones and rates are written into the scenario text; for dynamic pricing based on external data (like maps), use the "API request" action |
| Passing the order to drivers | The "Send message to a segment of subscribers" action broadcasts the request to the driver group — whichever driver is free taps a button in their own bot first |
| "Driver accepted / arrived" notifications | The driver sends these themselves via an action button in their own bot, or the admin sends them via the "Send message" action to a specific subscriber |
| Ride payment | A product with a fixed price, or a payment link the dispatcher creates for that specific ride |
Tip: for more advanced logic — like automatically matching the nearest driver on a map — it's easiest to build that in an external service and connect it to the scenario via the "API request" action.
Ready to automate your business?
More than 15,000 bots have already been created on the platform
Create chatbotFree trial — no card required