How one logistics firm cut IT tickets with AirWatch
When a Brisbane-based freight operator first plugged AirWatch into its mobile fleet, the idea was simple: stop the constant stream of helpdesk calls from drivers, dispatchers and warehouse staff. Six months later, the IT team had reclaimed entire afternoons, the service desk queue had shrunk noticeably, and the operations team could finally focus on moving freight instead of rebooting phones.
The story belongs to a mid-sized carrier running linehaul routes out of depots in Wetherill Park and Townsville, with a smaller regional office in Wagga Wagga. Like many Australian transport businesses, the company runs on tight margins, a young workforce, and devices that get tossed between forklift cabs, truck sleepers and kerbside deliveries every day.
What changed wasn't just the software. It was the way the IT team started treating mobile endpoints the way banks treat ATMs: pre-configured, locked down, and watched over from a single console.
Where the wheels were coming off the bus
For years, the carrier's IT support tickets came from three persistent pain points. Drivers were getting locked out of dispatch apps after operating system updates. Warehouse supervisors in Townsville and Sydney were reporting battery drain and slow barcode scanners. Office-based planners in Melbourne were asking for VPN access they could actually trust on their personal phones.
Each ticket on its own looked small. Together they averaged around 110 requests a week, which is a heavy load for an internal team of three support staff. The IT manager estimates the team spent roughly a quarter of its time on repeat issues that had nothing to do with the core logistics platform the business runs on.
For an industry where every minute of downtime costs money, the steady drip of "my scanner won't pair", "I can't see the run sheet" and "this app crashed again" was a quiet but persistent drag on operations.
Why AirWatch over other EMM platforms
The shortlist for the project included two other enterprise mobility management tools, but AirWatch, now part of the broader VMware family, stood out for the depth of its integration with the carrier's existing virtual desktop environment and its granular policy controls.
AirWatch gave the IT team a proper staging process. New tablets came out of the box, enrolled themselves over the air, and pulled down the right apps and settings without anyone at the depot needing to touch them. For a yard that receives twelve new devices a quarter as the fleet expands, that hands-off workflow mattered.
The other deciding factor was local support. With a regional VMware presence across Sydney and Melbourne, the team could get an engineer on a call within hours rather than chase support tickets across time zones from California.
The rollout, depot by depot
Deployment began at Wetherill Park, then spread north to Townsville and eventually to the smaller satellite office in Wagga Wagga. Each site kept its own quirks: in Townsville, supervisors needed ruggedised devices that could handle humidity and dust; in Wagga, the team relied more on personal phones for after-hours dispatch work.
Rather than roll out the full AirWatch stack at once, the IT team prioritised three cohorts, each with its own profile and policy bundle.
| Cohort | Devices in scope | AirWatch policy applied | What changed |
|---|---|---|---|
| Linehaul drivers | 95 corporate-issued tablets | Corporate-owned, single-use mode with locked catalogue | Dispatch, maps and fatigue app only; lockouts virtually disappear |
| Warehouse supervisors | 40 ruggedised scanners | Dedicated work profile with barcode app pushed over the air | Faster enrolment, far fewer pairing and battery tickets |
| Office planners (BYOD) | 28 personal iPhones and Androids | Secure container for email, documents and dispatch app | Work data sealed off; remote wipe in under a minute |
The phased approach let the team learn as it went. By the second depot, enrolment scripts were running smoothly and the helpdesk had already seen fewer lockouts. By the third, the IT lead was confident enough to bring BYOD into the mix.
Field feedback shaped the rollout as much as the technology did. Drivers asked for a darker night-mode skin for the dispatch app to cut glare on night runs between Brisbane and Townsville, and the IT team built that into the next catalogue update.
The service desk numbers
Six months in, weekly ticket volume had fallen from roughly 110 to around 42, with most of the remaining requests being genuine infrastructure issues rather than device or app frustrations. Average resolution time on mobile-related incidents dropped from over six hours to under forty minutes, because the IT team could now see the device state remotely and push fixes without a truckie even parking the ute.
The head of IT described the shift as the difference between fighting fires and patrolling the building. Lockouts virtually disappeared once AirWatch's identity policies tied the dispatch app to a single sign-on flow. App crashes fell sharply after the team standardised on a single build of the dispatch tool and pushed it through the AirWatch catalogue instead of letting drivers sideload their own versions.
Helpdesk staff also noticed a change in tone. Drivers who once called in frustration began emailing screenshots ahead of time, knowing the support team could already see what was happening on their tablet.
Security, compliance and the BYOD question
Australia's Notifiable Data Breaches scheme and the Privacy Act's tougher expectations around personal information meant the carrier couldn't afford to keep its old approach of letting staff mix work data with personal apps. AirWatch's containerisation feature gave the IT team a way to draw a hard line between a planner's personal photos and the company's freight manifests.
Remote wipe became a routine tool rather than an emergency reaction. When a planner in the Melbourne office left for a competitor, the IT team wiped the corporate container from her phone in under a minute and handed her off to HR without anyone needing to recover a lost handset.
The same controls made the BYOD rollout far less risky. Staff kept their own phones for personal use, while the corporate profile tucked emails, documents and the dispatch app away in a managed workspace the IT team could lock or wipe on demand.
What the business looks like now
The metrics tell part of the story. Tickets down by just over 60 percent. Mobile-related escalations down by more than three quarters. Driver satisfaction scores, measured through the carrier's quarterly pulse survey, ticked up noticeably after the second depot went live.
The numbers don't capture the harder-to-measure gains. Drivers no longer ring in at three in the morning because a navigation app has gone rogue. The IT team has shifted from reacting to planning, with time freed up for a telematics integration project and a long-overdue refresh of the dispatch software.
The carrier now treats mobile endpoints as enterprise infrastructure rather than consumer accessories. The same disciplined approach taken to a B-double pre-trip inspection applies to every tablet and phone that touches a load.
Running your own trial of AirWatch
If a portion of this story sounds familiar, the quickest way to test whether AirWatch can do the same for your operation is to spin up the 30-day trial directly through the VMware site. The trial bundle includes the core console, support for iOS, Android and Windows devices, and access to the same knowledge base the Brisbane team leaned on during its rollout.
For IT leaders who want a guided walkthrough or a side-by-side comparison of packaging options, the AirWatch website lists current pricing tiers, customer case studies from Australian industries, and a sales contact form that routes enquiries to the Sydney-based team. Booking a demo through that channel typically returns a same-day response and a tailored plan for businesses running fleets across multiple states.