How Imran IAC Books Freight Faster Inside DAT

Imran IAC runs more than 100 trucks across the United States, hauling van, reefer, and flatbed freight. At that scale, dispatch is less about any single decision and more about how many good decisions a team can make before the best freight is gone. The carrier had already built its booking around DAT, where its dispatchers and updaters live every shift. What it had not solved was everything that happens around the board: the outreach, the checks, the missing details, and the broker updates that pile up between searching for a load and actually covering it.

This is the story of how that team kept its existing DAT workflow and used Numeo to take the repetitive work out of it. The goal was never to replace dispatchers or add more of them. It was to let the dispatchers Imran IAC already had spend less time on copy-paste and more time on the part of the job only a person can do well: deciding which load to take.

Where the gaps did the damage

Imran IAC did not have one obvious thing breaking. As the fleet grew past 100 trucks, dispatch started to fray in the seams instead. Load details got copied from one place to another. Updates scattered across tabs and apps. Follow-ups went out late, and too many tools competed for a dispatcher's attention at the same moment. None of these were dramatic failures on their own, but together they added a tax to every load.

The team's day-to-day reality made that tax expensive. Dispatchers at Imran IAC manage high volume, often in the range of 60 to 80 trucks depending on the shift, while updaters handle another 30 to 40. At that load, the company runs a handful of core jobs over and over: sending broker emails while browsing loads in DAT, following up to collect missing rate, pickup, delivery, commodity, and notes, running broker and factoring checks during booking, and keeping tracking and broker updates moving for active loads. Every one of those is fast in isolation. Done hundreds of times a day, by hand, across tools, they become the thing that slows a good dispatcher down.

The room above is a busy one, and that is the point. With this much volume flowing through a single shift, small inefficiencies do not stay small. The carrier wanted the floor to feel calmer without taking anyone off it, which meant the work itself had to get lighter rather than the headcount getting larger.

The first hour decides the day

For Imran IAC, better freight usually means earlier freight. The strongest loads on the board are claimed in the opening stretch of a shift, so a team that moves slowly at the start ends up choosing from what is left. As one dispatcher put it, "If you cannot find the needed freight early, you may end up with not good freight, maybe bad rate." That is the whole problem in a sentence: speed at the front of the shift decides the quality of the day.

The trouble was that the first hour kept getting eaten by tasks that do not actually improve a decision. They just keep the machine running. Dispatchers rewrote and sent the same kinds of broker emails again and again. They chased missing details. They checked records. They flipped between tools to update brokers and customers. Each of these is necessary, but none of it is the judgment work that wins a good load at a good rate. The faster freight market does not wait while a dispatcher reassembles context across five tabs, and Imran IAC was losing time at the exact moment it could least afford to.

Booking from inside DAT, without the copy-paste loop

What changed was not where the team works. The workflow still begins in DAT, the same as before. The difference is what happens after a load starts to look promising. Instead of rebuilding context across tabs to reach out to a broker, dispatchers run that outreach from inside the search. With Numeo Spot, a dispatcher can shortlist several loads while searching, send outreach to multiple brokers in a single pass, and keep follow-ups moving in the background, all without leaving the board they were already on.

The dispatcher stays in control of every message. The system assists and the person approves, which matters in a business where the wrong rate or the wrong commitment is costly. One dispatcher described the new rhythm plainly: "I can send emails for two or three loads at the same time, AI can check it for me, and I will choose what I need." That last clause is the heart of it. The repetitive sending and checking get handled, and the choice stays with the human who knows the lane, the truck, and the customer.

The effect is a shift in where a dispatcher's hour goes. Fewer minutes disappear into micro-tasks, and more of them go toward the actual call of which load to take. For a team booking against the clock at the start of every shift, moving that balance even a little is what separates earlier freight from leftover freight.

Follow-ups that keep the whole shift moving

A familiar pattern in dispatch is waiting. You email a broker, then stall until you hear back, and while you wait the board keeps moving and the best loads quietly disappear. Imran IAC wanted the opposite of that: momentum that does not depend on any single reply landing on time. The model the team settled into is simple. If a load has an email, send it and keep searching. If another load needs a call, make the call while the email follow-ups continue on their own elsewhere. Several conversations stay in motion at once instead of one blocking the rest.

"I might find another load, and at the same time AI can check for me on the email," a dispatcher explained. "It's helpful for multitasking." The result is less dead time between actions and fewer moments where one slow broker derails an entire shift. For a high-volume floor, that steadiness compounds. A dispatcher who never has to sit and wait is a dispatcher who can keep working the board while the follow-ups resolve themselves.

Tracking and broker updates without juggling tools

Booking faster helps, but the day does not end when a load is covered. The other time sink at Imran IAC was the constant operational updating that follows every booked load: drivers, brokers, live tracking links, internal notes, and group chats. Before, that meant separate apps for tracking, manual location sharing, updates sent one by one, and a lot of time spent switching tools instead of managing the exceptions that actually need a person. "Before, we had to use different applications," an updater said. "It took a lot of time."

The carrier moved its updaters into a single operational flow with live tracking, broker updates, check calls and notes, and instant notifications for delays and alerts. The shift was less about adding capability and more about collapsing many tools into one place, so the updater spends time on what goes wrong rather than on routine status-pushing. The same updater described the change bluntly: "It is automated, I can do all the loads in seconds." That is the qualitative result the team points to most: the operational tail of each load stopped being a job in itself.

More time to decide, not just react

Imran IAC describes the impact in practical terms rather than hype. The team gets more time back during the shift. Outreach and checks move faster, so good freight gets booked earlier. There is less manual chasing for missing load details, broker updates go out faster and more consistently, and the floor is calmer overall, with fewer tabs and fewer repeated steps to get through. None of that came from adding people. It came from taking the repetitive layer off the people already there.

What stands out is how the team frames it for the dispatchers themselves. "It's making your job easier. It's not taking your job," one of them said, and that framing is what made it stick on the floor. Asked whether they would go back to the old way of working, the answer was just as direct: "Of course not. Now I'm saving more time, better work at the end." For a 100-truck carrier that grew faster than its manual process could keep up with, that is the real change: a dispatch day spent deciding, instead of one spent reacting.