Blacklane offers not showing?
A quiet feed usually has a boring explanation. Work through these in order — the causes are listed from most to least common, and the first three cost you nothing to check.
1. Are you actually eligible right now?
- Vehicle class approval. You only see offers for classes your vehicle is approved for. If a vehicle was recently added or changed, approval may still be pending.
- Documents. An expired licence, insurance or permit can quietly suspend your eligibility before anyone tells you.
- City or service area. Offers are tied to where you are registered to operate, not to where you happen to be parked.
2. Is your account in an active state?
Availability toggles get switched off and forgotten — after a holiday, after a maintenance day, after a phone reinstall. Check that your account is set to available and that nothing is paused on the partner side.
3. Is it simply a quiet period?
Before assuming something is broken, sanity-check demand. Mid-week afternoons, the weeks after major holidays, and cities outside conference or event season are genuinely quieter. If a colleague in the same city is also seeing little, nothing is wrong with your setup.
4. Are your filters excluding almost everything?
This is the most common cause among drivers who use any kind of rule-based setup, and it is rarely one setting — it is the combination. A price floor that is fine on its own, plus a narrow class list, plus a long advance-notice requirement, plus a blocked drop-off area, can multiply out to almost nothing.
Diagnose it by loosening one rule to an obviously permissive value for an hour. If offers appear immediately, you have found the family; now tighten back gradually.
The trap: a filter that silently rejects everything looks exactly like a platform with no offers. The only way to tell them apart is a log that shows you the offers that arrived and the rule that rejected each one.
5. If you use an automation tool
Check these before you conclude the platform is quiet:
- Is the bot actually running? Most tools pause themselves after repeated errors. That is correct behaviour, but only helps if you notice.
- Has the session expired? Login tokens expire. A well-built tool refreshes them and tells you when it cannot.
- Did it back off after errors? If the platform returned rate limits or server errors, a sensible tool waits — and waits longer each time. During that window it is deliberately doing nothing.
- Are conflict rules blocking everything? If buffer or return-time settings are generous, one accepted ride can block a large part of your day.
- Read the decision log. It should tell you whether offers arrived and were rejected, or never arrived at all. Those are completely different problems and the log is the only thing that distinguishes them.
6. The boring technical ones
- Notifications disabled for the app, so offers arrive but you never hear them.
- Signed out on the device you actually carry.
- Battery optimisation killing the app in the background.
- An app version old enough to misbehave.
How limobotai makes this visible
Every offer the bot sees is logged with the decision and the rule behind it, and sent to Telegram. When nothing is happening, you can tell at a glance whether the feed is empty or your rules are rejecting everything — which is the distinction that takes drivers the longest to make on their own. Errors and automatic pauses are reported too, so a stopped bot does not look like a quiet market.
If the answer turns out to be “my filters were too tight,” how to get more Blacklane rides walks through which settings to loosen first.