Case Study

How Innovative Automations helped DaZZee I.T. Services add an Always-On Voice AI Technician with Thread

Hunter Holderfield
AI & Automation Engineer
Innovative Automations 

Key Outcomes

If you're an MSP asking whether Thread works, here's what DaZZee IT Services saw:

Key Outcomes

From 25 ticket categories to about 150, set automatically by Thread on every ticket

  • ✓ The Voice AI overflow agent covers the 4 to 6 p.m. gap and after-hours calls, asking the same intake questions a technician would
  • ✓ Technicians no longer feel pressured to drop what they're doing to catch every ring
  • ✓ Flows built on the new categories resolve common tickets with no technician involved
  • ✓ Teams chat rollout dropped from 3 to 5 hours per client to 2 to 3 hours once DaZZee had a process
Company

DaZZee IT Services

PSA

Halo

Managed Clients:

~50

About DaZZee IT Services

DaZZee IT Services is an MSP based in Branson, Missouri that provides managed IT, cybersecurity, AI automation and managed print services to small businesses and local governments, including accounting firms, insurance agencies, nonprofits and manufacturers. Founded in 1999, DaZZee also serves Springfield and Kansas City and supports clients across Missouri, Arkansas, Kansas and Oklahoma. Its service model puts most of its effort into prevention, planning and monitoring, backed by a two-hour response commitment.

DaZZee joined Thread early, before Voice AI existed. Hunter Holderfield, now Innovative Automation's AI and Automations Engineer, led its Voice AI rollout.

The Challenge

Many tickets reached DaZZee by phone, through one person on the front line. That person created the ticket with a description of the issue, but the category, priority and other details technicians needed were left for later. When the front-line role ended at 4 p.m., technicians spent the next two hours juggling inbound calls on top of their own work, and after-hours voicemails arrived as tickets with little more than a callback request. DaZZee wanted every ticket to arrive ready to work, no matter when or how the client called.

The Core Problem

Every ticket needed a person to set it up by hand, and every missed call became a ticket with no context.

"Tickets were coming in from a phone call at our front line. There was one person typically handling that ticket interaction, and then they would go and create the ticket. But that would just be the issue. It wouldn't really include a category or all of the other items that our technicians were doing when they would create a ticket."

— Hunter Holderfield, Innovation Automations

Technicians setting ticket title, status and category before they could start resolving anything

  • A 4 to 6 p.m. window when technicians had to cover the phones themselves
  • Voicemail tickets that arrived with a generic subject line and no analysis of the issue
  • Only 25 to 30 parent categories, too broad for AI to act on

DaZZee started with the tickets, then moved to the phones.

The Solution

Thread was deployed as DaZZee IT Services' AI service desk layer, connecting phone, email and Microsoft Teams intake to HaloPSA and automating ticket categorization, prioritization and titling, then overflow call handling through Voice AI.

The groundwork came first. DaZZee built a master spreadsheet of ticket categories, opened it up to the whole team for feedback, and broke each parent category into detailed subcategories. A single password reset category, for example, became four distinct types. With about 150 categories loaded into Thread, Magic now sets the category, priority and title on every ticket in HaloPSA automatically.

When Voice AI launched, DaZZee started with the overflow agent. It answers any call no one can pick up, asks structured intake questions, creates the ticket and posts a summary with the recording and transcript. DaZZee kept close to Thread's default question set and still runs mostly on the defaults today. Before going live, Hunter mapped every path through DaZZee's phone system and tested what would happen when a caller was or wasn't matched to a contact. That testing stretched the first rollout to about three weeks, and he estimates a new partner could do it in one to two weeks today.

"It allowed that one person juggling all of those inbound phone calls to not have to stress, because they knew there was another agent similar to them that was going to ask the same exact questions if they were not available. So they didn't feel as pressured."

— Hunter Holderfield, AI and Automations Engineer, Innovation Automations

How the Team Uses Thread

New tickets land in DaZZee's triage queue, where Thread categorizes them as they arrive. When a category matches a common request, a Flow runs and helps the user resolve the issue, often closing the ticket with no technician involved. Hunter built those Flows by pulling the most frequently reported tickets from HaloPSA and automating them one at a time.

On live calls, Voice AI's technician handoff tells the technician who's calling and why before connecting. When the technician accepts, Thread assigns the ticket to them in HaloPSA with the category and title already set. Clients also reach DaZZee through Thread's Microsoft Teams app, and every request they report there flows straight into the PSA.

"With the technician handoff, it was automatically assigning that agent to the ticket. So it was fully automating that process, assigning the ticket, assigning the categories, assigning the title, to where the technician was able to just pick up the phone and work directly on the issue."

— Hunter Holderfield, AI and Automations Engineer, Innovation Automations

Day in the Life

At 8 p.m., a client's office manager calls DaZZee and nobody can pick up. The overflow agent answers under DaZZee's name, asks what's wrong and who's affected, and creates a ticket with a full summary and the call transcript. Thread categorizes and prioritizes it before morning. When the first technician logs in, Thread Inbox shows the ticket already flagged by urgency, and the technician calls back knowing exactly what the problem is.

The Results

DaZZee IT Services Achieved Ready-to-Work Tickets from Every Call

Every ticket at DaZZee now arrives categorized, prioritized and titled by Thread, across about 150 categories instead of 25. The overflow agent has replaced bare voicemail tickets with structured ones, so technicians can tell what's urgent and what can wait until the next day. The front-line team no longer races to catch every ring, and the overflow agent now covers the 4 to 6 p.m. window technicians used to juggle.

The system needs little upkeep. Hunter has personally handled about one maintenance issue every three weeks. When the agent can't confidently match a caller, it still gathers every detail, creates the ticket and flags the caller as unverified for the team to fix. Rollout keeps getting faster too: deploying Teams chat took 3 to 5 hours per client at first and now takes 2 to 3.

The expertise has become a business line of its own. DaZZee spun up a sister company, Innovation Automations, to help other MSPs deploy automations, and helped onboard another MSP onto Thread in about four hours as a paid engagement.

"We would get tickets at 8 p.m. from a voicemail. We've now replaced that with overflow, and now it's asking those correct questions and making sure we don't get a ticket that just says, 'Hey, I need a phone call.' Then Thread Inbox is able to correctly prioritize that urgency."

— Hunter Holderfield, AI and Automations Engineer, Innovation Automations

 

Did Thread reduce manual work for technicians? Yes. Thread sets the category, priority and title on every ticket across about 150 categories, and technician handoff assigns calls to the technician automatically in HaloPSA.

Did Voice AI change the customer experience? Barely, and that was the goal. Clients were told by email that an AI agent may answer if no one is available, and the agent asks the same intake questions DaZZee's team would.

Does Voice AI take a lot of maintenance? No. Hunter has needed to step in about once every three weeks, and DaZZee still runs mostly on Thread's default settings.

Did Thread help DaZZee resolve tickets without a technician? Yes. Flows built on DaZZee's categories help users resolve common issues and close the ticket with no technician involved.

Conclusion

DaZZee IT Services didn't start with Voice AI. It started by rebuilding its ticket categories so Thread's AI had something precise to work with, then layered on Flows, Teams chat and the overflow agent. Today a four-person support team gets every call as a structured ticket, technicians answer the phone without racing the next ring, and clients get the same intake questions whether a person or the agent picks up. Hunter's advice for MSPs starting out: clean up your categories and map your phone system first, because that groundwork is what makes everything else work.

Takeaway: DaZZee IT Services shows that MSPs using HaloPSA can turn every call into a ready-to-work ticket by deploying Thread and Voice AI as their AI service desk layer, without replacing their existing tools.

Get started with Thread today.