FlexControlWhat a bot sees on the Offers screen
When you open Offers in the Flex app, Amazon sends a list of blocks you are eligible for. Each one has a station, a start and end time, and the base pay. Good blocks often disappear in seconds because other drivers see the same list.
A bot does what you would do with your thumb, but without a break. It asks for a fresh list, reads every offer, and compares it with your rules. Then it waits a short, random pause and asks again.
Drivers call this tool many names: Flex bot, block grabber, flex grabber, auto-accept app. The name does not tell you how it works. Two things do: where it runs and who holds your Amazon login. We compare the kinds in Cloud bot vs phone app.
The rules a bot checks
Every offer is checked against every rule you set. If it fails any one, it is skipped. These are the rules FlexControl uses. Most bots have some version of them.
- Stations. Only the stations you picked. The list comes from your own Flex filters, so you can only pick stations your account can see.
- Minimum pay per block. Base pay, without tips. This stops short, low-value blocks.
- Minimum pay per hour. $60 for 3 hours is $20 an hour. This stops long, cheap blocks. Zero means no limit.
- Block length. From and to, in hours.
- Arrival buffer. The minutes you need to reach the station. A block that starts sooner is skipped. Without this rule, a bot can book a block you can't reach in time. If that happens, see what to do.
- Days and hours. Each weekday on or off, with its own window. The whole block has to fit inside the window. With 08:00–12:00, a block must end by 12:00.
- Overlap. A block that overlaps one already in your schedule is skipped.
- After a booking. Stop after one booked block, or keep looking for blocks that don't overlap.
Set your stations, minimum pay and hours. FlexControl searches in the real Flex app on your own device. You stay in control through Telegram. Try it free for 3 days, no card required.
Why it skipped: a sample log
Rules are easy to set too tight. That is why FlexControl keeps a log of every offer it saw and the reason it skipped it. Type /log in Telegram to see it. A sample, with the same example offers as our home page:
| Offer | Reason in the log | Result |
|---|---|---|
| DUR3 · Sat 07:00 · $66 | before your hours | Skipped |
| DDA9 · Sun 08:00 · $71 | under your $25/h | Skipped |
| VTX2 · today 14:50 · $72 | starts in 29 min, your buffer is 45 | Skipped |
| VTX3 · Sat 10:30–14:30 · $148 | fits every rule | Booked |
You will also see a reason when a station isn't on your list, when a block overlaps one you already booked, or when it is shorter than your minimum length. If most skips give the same reason, that rule is the one to loosen.
How fast is fast enough
A booking has several stages: an offer becomes available, the service checks it, an acceptance is attempted and the result is confirmed. A filter-check time alone does not measure the complete booking process.
With FlexControl, search pace is a setting. Choose your pace and watch /log to understand the offers being checked. A block is yours once the booking is confirmed in Flex.
When search pauses
If Amazon limits requests, search pauses and restarts by itself after an hour, up to four times per session. Check /status and Telegram messages to understand the current state.
For a captcha: Search pauses and you receive a Telegram notification. Follow the instructions in that message. Fully automatic captcha handling is in development. Read the captcha guide for more detail.
What happens after Accept
Accepting is not the end. Sometimes the accept request fails, or another driver got there first. A bot that pings you right after it taps can be wrong.
FlexControl reads your Flex schedule after each accept. It sends you a Telegram message only when the block is there, with station, time and pay. The same message has a one-tap cancel. You can see all your blocks with /calendar and check whether search is running with /status.
Where FlexControl fits
Your own device runs the real Amazon Flex app. Nothing to buy and nothing to install: FlexControl sets the device up and keeps it running for you, and it is included in every plan. Manage search from Telegram on your personal iPhone or Android.
- Sign in directly with Amazon by following the Telegram instructions.
- Search scheduled blocks at your selected stations.
- Check bookings with /calendar, search state with /status and offer decisions with /log.
Explore plans or setup questions.
Questions
How does an Amazon Flex bot accept blocks?
It keeps requesting your offer list, checks each offer against your rules, and accepts the ones that pass. Then a careful bot checks your schedule to confirm the block is really yours.
Why does my bot skip good blocks?
Usually one rule is too tight: arrival buffer, hours window or pay per hour. Check the skip reasons in the log. If most say "before your hours", widen the window.
Can a bot accept a block faster than Amazon allows?
No. A bot can decide fast, but Amazon decides who gets the block and how quickly it answers.
Can I adjust how often it checks?
Yes. Search pace is configurable. Check /status for the search state and follow any pause notification in Telegram.
What happens when Flex shows a captcha?
Search pauses and you receive a Telegram notification. Follow the instructions in that message. Fully automatic captcha handling is in development.
Sources
Sources are linked below. Product details describe FlexControl, and sample calculations are marked as examples.