Concept · Telegram bot · workflow design

Fare-Bid Ride Bot

Passengers name their price, drivers bid, and the bot returns only what each side needs to decide. There are no human moderators. Trust comes from automatic rules that protect passengers and drivers alike, including in rush hour and typhoons. Select any step on the map.

Pickup gate

Pickup only works when both passenger and driver are sharing live location. Until both are live, the match stays pending and the driver never receives the exact pickup point. If either side stops sharing before pickup, the match drops back to pending.

Map view

The everyday flow. Switch views to see which steps change when demand spikes or a typhoon signal is up.

Rush hour mode

Bidding already lets prices rise when everyone wants a ride. These rules handle everything around the price.

1. Show the crowd so asks adjust themselves

  • Demand signal before posting: requests vs. drivers nearby.
  • Suggested range uses fares accepted in the last 30 minutes.
  • No bids after 3 minutes: the bot shows the going rate, one tap reposts higher.

2. Keep drivers from drowning in requests

  • Requests go to the 15 nearest drivers first, then widen.
  • Feed sorted by fare per km or distance to pickup.
  • Quiet mode: one digest every 30 seconds.

3. Stop the gaming a rush invites

  • One open request per passenger; raising the ask replaces the post.
  • One active match per driver, except a next pickup near the current drop-off.
  • Fare locked at match; asking for more at pickup is flagged.
  • Zero-trip accounts hidden by default while demand is high.

4. Take some demand out of the peak

  • Scheduled rides: book tomorrow's commute the night before.
  • Pasabay: two verified passengers going the same way split one car.
  • Opt-in demand alerts pull nearby off-duty drivers in.

Trade-off: in a rush, whoever pays more rides first. Scheduled rides and pasabay soften that; they don't remove it.

Typhoon signal mode

Open pricing is at its worst in a storm. This is the one place the bot limits price, and the switch is an official signal, not a person.

Trigger

  • On automatically when PAGASA raises Tropical Cyclone Wind Signal No. 2 or higher for the pickup area; off when it's lifted.

The cap

  • Asks and bids are capped at 1.5× the top of the normal suggested range for that route.
  • Bids above the cap are rejected with the cap shown. Accepting the passenger's ask always works.

What people see

  • Drivers see the cap is on before they bid.
  • The bid list carries a banner: "Typhoon cap in effect: max ₱420 for this route."

Trade-off: a cap can mean fewer drivers out in bad weather. 1.5× keeps a real premium for driving in a storm while ruling out the ₱1,500-for-5-km screenshots.