Altoona, IA · I-80 Exit 142
FUEL TO FULL TANK
Grand Junction, CO · Exit 26
FUEL 95 GALLONS
Three taps from group to plan
Dispatch starts with the group you're messaging — not a form. The truck, its live fuel, and its location come with it.
Pick a driver group
Choose the Telegram group you're sending to. Fuelstops auto-selects the mapped unit — no truck picker, no lookup.
Live status loads itself
Samsara fuel %, estimated gallons, DEF level and GPS load at compose. The starting point defaults to where the truck actually is.
Pick a route, send
Add your stops, pick a route option, and send. The driver gets a stops-only plan in the group in seconds.
Signup to first plan, in five scrolls
Self-service from the first email code to the first plan in the group. No sales call, no integration project.
- 1
Create your carrier
Sign in with a one-time email code and pick a sign-in handle. No passwords, ever — anywhere.
Passwordless auth - 2
Connect your bot
Paste a token from BotFather. Your own Telegram bot goes live instantly — the webhook is wired the moment you connect.
Your bot, your brand - 3
Map driver groups
Groups are captured automatically when your bot joins them. The unit is suggested from the group title — you confirm it once.
Captured on join - 4
Connect providers
Link your fuel-price provider (Pilot Flying J first) and fleet provider (Samsara first). Contract prices sync on a schedule; credentials are encrypted at rest.
Encrypted at rest - 5
Send your first plan
Compose, optimize, and send. Drivers get a stops-only message with Google-Maps links — straight into the group.
Stops-only to drivers
Everything a dispatcher needs, in one flow
The optimizer is the engine — but a plan gets sent by a person under pressure. Fuelstops is built around how dispatch actually works.
Group-first compose
Start from the driver group. It auto-selects the unit and becomes the send target — one flow, no truck lookup.
Live truck telemetry
Fuel %, estimated gallons, DEF level and GPS pulled live from Samsara at compose, with a low-DEF warning for dispatch.
Contract-price optimization
Gemini picks the cheapest contract-price stops along your corridor; the backend re-derives every price, gallon and total cost.
Dispatcher instructions
Add a plain-language note (“no stop for 250 miles after stop 1”). It’s a best-effort preference — never at the cost of reachability.
Audit-ready history
Every plan is kept with its savings. Carrier-admins get a weekly compliance grid of which trucks were planned on which days.
Route options
See the recommended route plus alternates — each with distance and ETA — and optimize fuel stops along the corridor you’ll actually drive.
One flow on two surfaces
Dispatchers work where the drivers already are — Telegram. The rest of the operation runs on the web. Both surfaces share the same backend, so a plan is a plan wherever it starts.
Telegram Mini App
Compose and send plans without leaving Telegram. Signed initData keeps every session tied to the right carrier.
- Group-first compose
- Live status + route options
- Send straight to the group
Web dashboard
Everything else lives at app.fuelstops.io — setup, providers, dispatchers, plan history, savings KPIs and the audit grid.
- Providers & dispatchers
- Plans history + savings
- Trucks & compliance grid
Connected to what you already run
Fuelstops plugs into your existing fuel account, your telematics and your drivers' Telegram — no new hardware, no new driver app.
Pilot Flying J
Contract fuel prices synced from your Pilot account — plans are built on the price your carrier actually pays.
Samsara
Live telematics — truck location, fuel level and odometer read straight from your fleet.
Telegram
Stops-only plans delivered to the group chats your drivers are already in.
Don't see yours?
Tell us which fuel provider or ELD you use — we reach out to them on your behalf and set the connection up.
Request an integrationYour prices never leave dispatch
Contract fuel pricing is your leverage. Fuelstops treats it that way — prices, savings and optimizer reasoning stay on the dispatcher review. The driver only ever sees where to stop and how much to fuel.
Row-level tenant isolation
Every carrier's data is fenced off in Postgres with row-level security — enforced at the database, not just the app.
Allow-listed dispatchers
Only the people you add can compose and send. Access is scoped to your carrier and nothing else.
Envelope-encrypted keys
Provider credentials are encrypted per connection, never logged and never returned — your Samsara and fuel tokens stay sealed.
Time-boxed, audited support
If you ask us for help, support access is read-only, expires on a clock, and every impersonated read is audited.
Altoona, IA · I-80 Exit 142
FUEL TO FULL TANK
Grand Junction, CO · Exit 26
FUEL 95 GALLONS
What the driver receives — no price, no savings, no reasoning.
Priced per truck. Paid for by the pump.
Two tiers, billed per active truck per month. Start with a 3-day trial — the savings show up in-app on every plan.
The core product, complete — sold on the savings number itself.
Get started- Compose → optimize → send on both surfaces
- Live Samsara status + low-DEF warning
- Plans history + savings KPIs
- Stops-only driver messages
Everything an operation runs on — the advanced optimizer plus the back-office tools.
Get started- Route-options selection before every plan
- Audit / compliance weekly grid
- Per-vehicle Avg-MPG sync from Samsara
- Dispatcher web logins
- Per-plan policy overrides at compose
Billed on active trucks from your fleet sync (minimum 5). Fair-use is pooled across your fleet — plans keep generating over the pool.
Your next load could cost less
Connect your bot, map a group, send your first plan. Three days to see the savings on every plan — no card, no passwords.