Before automation, Imona's dispatch workflow involved a five-step manual routine repeated for each of the 20β25 loads received daily.
minutes per load for manual PDF data extraction, adding up to 80β100 hours of administrative work each month.
Flowbetta designed a 3-layer automation system using Google Apps Script to connect existing tools (Gmail, Telegram, Google Sheets, Google Drive)βwithout requiring new software subscriptions or changing team habits.
Gemini AI was integrated to read incoming broker PDFs in varying layouts and extract structured load data into a consistent format.
The system checks Gmail every 10 minutes for new broker load emails. When received, it passes the PDF attachment to Gemini AI, which extracts key details (origin, destination, rate, mileage, pickup windows) and posts them to the dispatch Telegram group while archiving the PDF to Google Drive.
Simultaneously, the extracted load data is populated into a dedicated Google Sheet. Each load creates a new structured row, giving the team a centralized log of all incoming requests without manual copy-pasting.
The system monitors driver Telegram chats every 30 minutes. When a driver accepts a load, the script identifies the message and updates the corresponding row in the Google Sheet, marking the load as assigned.
Prior to Flowbetta's Gemini AI automation, a dispatcher required approximately 10 minutes per PDF load document to open the email, read the unstandardized rate sheet, extract origin/destination/rates, retype the summary into Telegram, and log the row into Google Sheets.
What previously took ~10 minutes of manual handling is parsed and broadcast to Telegram in under 1 minute.
Over 19,800 PDFs parsed with Gemini AI across hundreds of broker document formats without data loss.
Both fleets doubled processing capacity over 16 months without adding a single administrative hire.
The second deployment came about when Imona Logistics' CEO introduced Flowbetta to his brother's company after seeing positive results in his own operations.
"Practical results build confidence."
Expanding the workflow to a second fleet confirmed that a clean automation structure could be adapted easily to similar logistics routines.
Open communication during initial testingβhandling edge-case PDF layouts and API quota limitsβhelped maintain clarity and steady progress throughout setup.
Mapping out manual steps thoroughly before writing code ensured the system fit how dispatchers actually work.
Communicating openly during testing and resolving early edge cases promptly kept project progress smooth.
Using Gmail, Sheets, Drive, and Telegram minimized setup overhead and helped the team adopt the system quickly.
Delivering practical, reliable value for the primary client led directly to a word-of-mouth referral.