Fleet Master connects a self-service desktop terminal, cloud administration, roster control and a Telegram operations bot into one auditable workflow.
Only the operating logic that matters: who can take a vehicle, what the system records, how exceptions are detected and how management is notified.
A rider selects a valid shift, takes an available moped and creates one authoritative cloud record. The same record drives the live fleet list, Telegram tasks, overdue control and reports.
Instead of a team leader manually checking messages, the bot starts the photo workflow, matches evidence to the right shift and records what was delivered, received or missed.
Moped replacement, late uploads, missing evidence, urgent support and repeated violations are handled as structured workflow exceptions - not buried in chat history.
Finishing time does not automatically hide the assignment. The moped remains Online until it is returned. After the configured grace period, the record becomes Overdue and requires action.
Adjacent roster rows are merged into one planned window. Management can see entered start and finish next to roster start and finish, then investigate mismatches through the audit trail.
Telegram becomes a controlled interface for evidence and support, while Fleet Master keeps the actual business state in PostgreSQL.
Requests arrive privately, reducing noise in the operations group.
Photos posted in the correct moped topic can still be matched when the active rider, shift and timing agree.
Telegram is the communication layer. Fleet Master remains the source of truth.
Delivery failures, missing evidence and urgent support are visible without manually reading every conversation.
Rider signs in on the office terminal.
Available moped is reserved inside a database transaction.
Telegram bot starts the evidence workflow.
Admin sees Online, roster boundaries and Overdue.
Return, exceptions and reports remain traceable.
Riders handle routine key actions without waiting for an administrator.
The Telegram bot performs repetitive requests and evidence follow-up.
Every assignment, return and exception is connected to a rider and time.
The same workflow can be introduced in additional hubs without duplicating manual control.
Fleet Master is already operating in Göteborg. These pilot signals explain why the next conversation is about measurement and scale - not whether the workflow can work.
Seven concise pages covering the operational gap, live pilot evidence, current capabilities, production reliability and the proposed 30-day measured evaluation.
Pilot observations and financial estimates are clearly identified in the document.