How a Blacklane bot actually works

A Blacklane bot sits between the offers your chauffeur partner account receives and the accept or reject you would otherwise tap yourself. It watches continuously, evaluates every incoming offer against rules you configured in advance, and answers the ones that qualify — typically in well under a second from the moment the offer appears.

That speed matters because a good offer is visible to several qualified chauffeurs at once, and the first valid answer takes it. The bot does not change which rides you want. It removes the delay between the offer arriving and your answer reaching Blacklane.

Setup starts by connecting your Blacklane chauffeur partner account. The platform needs to see the same offer stream you see in the app, which means it authenticates as you. Those credentials are encrypted at rest and are never displayed back in the interface once saved.

Nothing is automated at this stage. Until you define at least one rule and switch automation on, the bot only observes. That deliberately gives you a window to watch what arrives before anything is answered on your behalf.

This is the part that decides whether automation helps or hurts. You are not telling the bot to “accept everything fast”. You are describing the shape of a job worth taking: what it pays, how far it goes, which vehicle class it needs, which cities you cover, and how much notice you need to reach the pickup.

Rules are set per vehicle, so a two-car operation can run a strict rule set on one car and a looser one on the other. Most chauffeurs start conservative — a high price floor and a small list of cities — then relax the rules once they have seen a few days of decisions.

The loop is where the product lives. It runs continuously rather than checking on a slow schedule, because an offer that is polled for every thirty seconds is an offer someone else has already taken. When a new offer appears, it passes through the rule engine in a fixed order:

An offer has to clear every gate. Failing one is enough to reject it, and the gate that failed is written to the decision log so you can see exactly why.

Once a decision is made you get a notification with the offer details and the outcome. There is nothing to confirm; by the time you read it, the answer has already reached Blacklane. Accepted rides appear in your schedule and immediately become part of the capacity check for the next offer.

• Every accept and reject is logged with a timestamp and the rule that produced it
• Accepted rides join your schedule and constrain future decisions automatically
• Rejections are kept too, so you can spot rules that are tighter than you intended
• Automation can be paused instantly, returning you to answering offers by hand

Automation that silently stops is worse than no automation, because you stop watching the app while nothing is being answered. A separate watchdog process monitors the scanner independently and restarts it if it stops responding, and repeated failures raise an alert rather than being retried forever in silence.

The design assumption is that you should never have to wonder whether the bot is running. If it is not, you hear about it.