HART I.T. Was Losing 17 Hours a Week to Dispatch. Then They Changed One Thing.

The Work Was Coming In. The Process Couldn’t Keep Up.

HART I.T. Solutions runs consulting, networking, cabling, special projects, and break-fix work for Fortune 500 accounts across the Southeast.

From its base in Tucker, Georgia, 13 field engineers cover jobs across Tennessee and Georgia, working inside hospitals, hospitality sites, warehouses, churches, offices, and other demanding environments.

The company had something most service businesses want… a steady stream of work.

Most jobs arrived already assigned by email, with the client, site address, scope, schedule, and line items sitting inside the message.

On paper, that sounds simple. But every one of those emails had to be turned into a work order manually.

Someone had to read the email, pull out the relevant information, type it into the system, deal with the attachments, and then somehow get that information into the hands of the engineer who was actually going to do the work.

And HART I.T. was doing that 25 to 35 times a day. The operation wasn’t short on information. It was short on a way to move it.

Thirteen Engineers Were Working Across Two States. The Office Was Still the Middleman.

The manual data entry was only half the problem. Once a work order had been created, the engineers still didn’t have it.

There was no mobile app. No work order on their phones. No place to see the next job or pull up the original scope.

So the information went through another human being.

The office would read the details over the phone. Engineers would call back to ask what was next, where they needed to go, or what exactly the job involved.

Scott Duhart, owner of HART I.T., put it simply…

“I had thirteen guys working across two states off information I was reading to them down the phone. That was the whole system.”

That system worked when the operation was smaller. At 13 field engineers, it had become a bottleneck. And the consequences went beyond wasted time.

A scope explained over the phone isn’t necessarily the same scope the client sent in the original email. For HART I.T., that mattered. Its engineers were working on Fortune 500 accounts, including live hospital environments where missing or misinterpreting a detail could have real consequences.

The Real Cost Was Hiding in the Hours Between Dispatch and the Job

Each dispatch took roughly four to six minutes to enter manually. With 25 to 35 new jobs arriving every day, that meant 2 to 3.5 hours of administrative work every day, or roughly 12–17 hours every week spent simply turning emails into work orders.

Then came the calls. More than 30 a day could come from engineers asking what was next, where the job was, or what the scope actually covered.

Then came the paperwork. Scope documents and site authorizations arrived as attachments, but they weren’t automatically part of the job record. Someone had to save them, rename them, attach them, or print them for the field.

And when closeout information came back late, billing and the next dispatch could fall a shift behind with it.

The bigger HART I.T. became, the more expensive that way of working would become.

There was another problem, too. HART I.T. recruits field engineers continuously. Every new engineer had to learn a system that partly lived inside someone’s memory. Growth was creating more demand for the same people-dependent process.

Scott Wasn’t Looking for Another Software Demo

The turning point wasn’t a search for a new FSM platform. Scott sat down with the Upvoit team and showed them how his dispatch actually worked.

How the emails came in. Where the information lived. What had to be extracted. What happened to attachments. What the engineers needed in the field.

That conversation changed the approach. Instead of asking HART I.T. to change its dispatch process to fit a software platform, Upvoit configured the workflow around the way HART I.T. already worked.

The AI Mailbox was delivered within a week of that meeting. That speed mattered because this wasn’t a theoretical problem. Every day the old process stayed in place meant another few hours of manual work and another round of calls from the field.

Now the Dispatch Email Starts the Workflow

HART I.T.’s dispatch inbox connects directly to Upvoit through Outlook. The initial connection takes about five minutes.

When a dispatch arrives, Upvoit reads the email and extracts the information Scott’s team used to type manually: the client, site address, scope, schedule, and line items.

The work order is created from there.

Instead of spending four to six minutes rebuilding every job by hand, the team now spends less than a minute checking what the system has already extracted.

And because HART I.T. receives dispatches in different formats, the workflow doesn’t depend on creating a separate rigid template for every source.

The AI interprets the information inside the email, while accuracy is continuously tuned using Scott’s feedback.

The process is no longer:

Email → person reads it → person types it → person calls engineer.

It becomes:

Email → Upvoit creates the work order → engineer gets the job.

The Documents Finally Follow the Work

The email itself wasn’t the only thing that needed to move. Scope documents and site authorizations often arrived alongside the dispatch.

Previously, those documents lived outside the actual work order. Someone had to save them, rename them, attach them, or print them.

Now, they flow into the job’s document management automatically. That sounds like a small operational change.

For an engineer standing at a customer site, it isn’t. The information they need is no longer sitting in someone’s inbox back at the office.

It’s attached to the job they’re working on.

The Biggest Change Happened in the Field

HART I.T.’s 13 field engineers now run their work orders through Upvoit’s mobile app on iOS and Android. For the first time, the field team doesn’t need the office to be the bridge between dispatch and execution.

They can access their own jobs. They can see the information attached to those jobs. They can work from the same system that received the original dispatch.

And that changes the role of the office.

Instead of spending its day telling 13 engineers what they should already be able to see, the office can focus on running the operation. That’s especially important for a company that continues to recruit engineers.

HART I.T. is no longer onboarding every new person into somebody else’s memory. It’s onboarding them into a system.

The Numbers Tell the Story

The change was immediate. Work orders went from four to six minutes of manual entry to under a minute of checking.

Daily dispatch administration dropped from 2–3.5 hours to under 45 minutes. That’s roughly 12–17 hours returned to the office every week.

But time wasn’t the only thing that changed. Scope documents and site authorizations now stay with the job instead of getting lost in an inbox.

The 13 engineers can manage their own work orders, removing most of the daily calls back to the office.

And because the original scope stays connected to the work order, much of the scope drift created by verbally relaying information disappears with it.

The implementation itself was fast.

The inbox connection took about five minutes, and the first working version was live within a week of Scott walking the Upvoit team through his dispatch process.

The Biggest Win Wasn’t Saving 17 Hours

It’s easy to look at the numbers and focus on the hours saved. But that’s not really what changed for HART I.T.

The bigger change is that the business no longer needs a person sitting in the middle of every job.

The dispatch information can move without someone manually rebuilding it. The documents can move without someone forwarding them. The engineer can access the job without calling the office.

And a new engineer can learn the workflow without having to learn everything from someone else’s head.

That’s what happens when software starts fitting the operation instead of becoming another process the operation has to manage.

Scott described the difference this way:

“They built it around my dispatch flow, not around a demo. That is why it worked in the first week instead of the third month.”

For HART I.T., Scaling Meant Getting Information Out of People’s Heads

HART I.T. already had the work. It already had the engineers. It already had the customers.

What was holding the operation back was the amount of human effort required to move information from the customer’s dispatch email to the person doing the job.

Upvoit didn’t ask the company to rebuild its operation. It took the process that was already working and removed the parts that were unnecessarily manual.

For a growing field service business, that’s an important distinction.

Because eventually, the question isn’t whether your team can handle another 10 jobs a day.

It’s whether handling those 10 jobs requires another 2–3 hours of admin, another 30 phone calls, and another person who knows exactly how everything works.

HART I.T. chose a different path.

The goal wasn’t to add more people to manage the work. It was to give the people already doing the work a better system.

Bring Us the Part of Your Workflow That Doesn’t Fit

Every business reaches a point where the way it used to operate starts getting in the way of where it wants to go.

For HART I.T., that point came when 13 engineers were still relying on the office to move information from dispatch to the field. Upvoit helped remove that dependency.

Because growing your field service business shouldn’t mean growing the amount of work it takes to manage it.

Your operation has its own way of working. Bring us the part that doesn’t fit, and we’ll show you what’s possible. Book a demo and let’s take it from there.