The situation

A seven-person agricultural services business operating out of Armidale runs seasonal contract work across the New England Tablelands: spray programs, fencing, mechanical harvesting assistance, and pasture renovation. During the spring and summer rush the crew covers a radius of around 200 kilometres, with multiple crews going to different properties on the same day. Dispatch had always run through a WhatsApp group. The operations manager would post each morning with the day's jobs, and crew members were expected to pick up the details from the thread. During quieter weeks this worked. During the peak season, messages got buried, wrong addresses were written down, and crew turned up to the wrong gate or with the wrong equipment. Over a full spring season the business recorded five to eight dispatch errors: a significant number when a missed job means a frustrated farmer and a wasted day's travel on the Tablelands.

The flow we built

A Make.com flow monitors a shared Google Calendar where the operations manager books all jobs:

  • Each job event is entered with the property address, the assigned crew member or crew name, and a notes field covering the work type and any equipment needed.
  • At 6pm the night before each job, Make.com sends a personalised WhatsApp message to every crew member assigned to a job the following day. The message includes the property name, a Google Maps link, the job type, start time, and equipment list pulled from the calendar event notes.
  • At the same time, the job is logged into a Google Sheets dispatch register with its scheduled date, crew assignment, and status set to Scheduled.
  • At 4:30pm on the job day, Make.com fires an end-of-day completion prompt to each crew lead. The crew lead responds with a simple form capturing job status, hours worked, and any follow-up required. The Sheets register updates automatically.
  • The next morning, a summary of completed and outstanding jobs goes to the operations manager before 7am.

The platforms

Google Calendar as the central job book. Make.com for the automation logic, calendar monitoring, and WhatsApp messaging. Google Sheets as the dispatch register and reporting layer. The setup runs on an Essential Bot Care plan. The monitoring flagged a WhatsApp Business API token expiry six weeks after go-live and the credential was refreshed before any morning brief was missed.

The results

Across a full spring season following deployment, the business recorded zero dispatch errors attributable to missed or wrong information. The shift was not complicated: crew members now receive a single clear message the night before, with everything they need in one place, rather than hunting through a group chat. The operations manager recovered around three hours a week that had previously gone to chasing crew members for updates and manually logging job outcomes. The Sheets register also gave the business its first reliable record of hours by job type, which fed directly into the following season's quoting process.

The unlock was not the technology. The New England Tablelands are full of agricultural contractors who do excellent work. The unlock was the consistency: every crew member got the same clear brief every night, regardless of how busy the operations manager's day had been.

What this could look like for your agricultural business

If you are running seasonal crews across regional NSW and relying on phone calls or group chats to keep everyone on the right property, a Calendar-driven dispatch flow like this one removes most of the human error at the briefing stage. Small business automation in Armidale is something we do regularly for agricultural and rural services businesses across the New England.