How Alvarez Technology Group Reclaimed 40 Hours a Week Without Adding Headcount
Luis Alvarez
President & CEO
Anil Melwani
Service Delivery Manager
- 40 hours per week reclaimed from automated ticket follow-up and triage, across a 10-person engineering team — equivalent to a full-time employee's weekly output.
- 13 consecutive weeks of 100% CSAT at the time of the interview, maintained through the entire Thread rollout and AI adoption period.
ConnectWise Manage
72
Alvarez Technology Group is a family-owned MSP-based in Salinas, California that has been delivering IT support to small and mid-sized businesses for 25 years. With approximately 72 managed clients and a service desk built on ConnectWise PSA, ATG has grown by staying close to its clients.
Some have been with the company for more than 20 years. That longevity shapes how The Alvarez Technology Group approaches change. New tools have to earn their place.
"When I look at technologies I want to implement in my company, there are two criteria, very simple, very definitive," said Luis Alvarez, CEO. "Either it's going to make me money or save me money. If neither one of those is going to happen, I'm just not going to implement it."
For most of ATG's history, the service desk ran on a dispatcher named Toni. With 11 years at the company, Toni owned the triage process start to finish: reviewing every incoming ticket, setting prioritization, assigning categorization, and following up on anything that needed more context before a technician could begin work.
The system worked. But as ticket volume grew, the limits of a single-dispatcher model became harder to ignore.
THE CORE PROBLEM:
Every ticket that arrived with missing context required a manual follow-up before meaningful work could start, and that burden fell entirely on one person.
"Someone would put in a ticket that said 'I need help.' And Toni would need to decipher what 'I need help' means," said Anil Melwani, Service Delivery Manager.
That decipher-and-follow-up loop was quietly consuming the team's capacity:
- Technicians spent two to four hours per week chasing status updates on open tickets
- Across a ten-person team, that totaled roughly 40 hours each week on follow-up work alone
- Toni had no time to do anything beyond triage: onsite scheduling, escalation management, and proactive client coordination went largely unaddressed
- When Toni was at lunch or off after 3 PM, the service manager stepped into the dispatch queue to keep clients off hold
The goal was not to replace Toni. It was to free her.
Thread was deployed as Alvarez Technology Group's AI service desk layer, connecting Microsoft Teams to ConnectWise PSA and automating ticket intake, triage, and follow-up across the full ticket lifecycle.
ATG's implementation followed a deliberate, low-risk sequence. They started with the features that required the least client-facing change and worked outward from there.
The first layer was auto-prioritization and categorization. When a ticket lands on ATG's triage board, Thread assigns priority and category automatically. Toni no longer needs to touch those fields. She moves the ticket to the right board and lets the AI handle the rest.
The second layer was the Teams-based triage agent. Clients who submit requests through Microsoft Teams now enter a conversational intake flow. Thread asks clarifying questions, collects the details a technician needs, and resolves what it can before a human steps in. For email-based tickets, the triage agent follows up and holds the ticket in a "gathering information" status for 15 minutes before releasing it to Toni as ready to dispatch.
The third layer was the voice overflow agent, which ATG named Fred. When a caller has been on hold for five minutes, Fred intercepts the call, captures the request, matches the caller's ID to their ConnectWise record, and generates a ticket automatically. The client receives a ticket number confirmation without ever speaking to a person.
"Just knowing that if a client has been on hold for five minutes, Fred is going to take that call — for me, that's been a huge weight off my shoulders," said Melwani.
Implementation was incremental by design. ATG introduced each capability first to clients who were already comfortable with digital communication, gathered feedback through quarterly business reviews and follow-up email campaigns, and adjusted before rolling wider. When clients expressed concern about response speed from the triage agent, Melwani explained the logic directly: the AI is asking upfront what a technician would have asked anyway, just faster.
Inefficient Dispatch is Replaced with Optimized Coordination
Before Thread, Toni's day was consumed by triage, follow-ups, updates, and eventually dispatch. Now, the triage agent handles the front end of that process, and Toni works on the work that actually requires human judgment.
Instead of sorting through a board of undifferentiated new tickets, she now looks at tickets that have already been categorized, prioritized, and enriched with context. Thread unlocks a superior coordination process that couldn't exist when triage took up 99% of the time:
-
Calling ahead to a client site to confirm a window before sending an engineer
-
Routing three onsites in the same area to one technician
-
Managing escalations proactively rather than reactively.
"We have been able to focus more on how to best handle onsites and manage escalations," said Melwani. "Whereas before it was often a warm body situation: I've got this person with a one-hour gap, let's just get them out there. Now, we provide the optimal service experience for our customers and our technicians."
How Thread Works: Day in the Life of a Ticket
A client submits a support request via Microsoft Teams at 10 AM. Thread's triage agent responds within seconds, asking clarifying questions and collecting the details needed to move the ticket forward. If the client replies, Thread incorporates the context and updates the ticket status. If they don't reply within five minutes, the ticket automatically moves to "new" on the triage board and Toni picks it up. She sees a ticket that already has a priority, a category, and whatever context the client provided. She moves it to the correct board and the AI finalizes the categorization. The technician receives a structured request and starts work immediately.
Customer Sentiment is Immediately Actionable
Melwani uses Thread's inbox primarily to monitor the sentiment agent. When a client's communication starts showing signs of frustration, he gets an alert and can intervene before the situation escalates.
"There's no way for me to look at every single possible ticket that's coming in to see if it's staying on track or if it's starting to spiral out of control," he said. "Thread's sentiment agent actively monitors every conversation and only alerts me when an escalation is actually necessary."
Inbox adoption among technicians followed the same intentional slow rollout as chat. Senior engineer Ben, a trusted voice on the team, began using Inbox before introducing it to the rest of the team and quickly became an enthusiastic advocate for it.
"Once he started using Inbox and said 'My God, this is the best thing' — all of a sudden, everybody else wanted to use inbox," said Melwani. "When the preference for doing things the new way comes from inside the team, the mindshift is so easy."
The team now uses Inbox for client communication, AI-assisted knowledge base lookups, and searching prior tickets for context. Time entries and some routine tasks still happen in ConnectWise directly, which Melwani considers a reasonable hybrid.
Alvarez Technology Group Reclaimed 40 Hours a Week and Scaled Without Hiring
With Thread automating ticket intake, follow-up, and triage, ATG recovered the capacity that had been quietly draining the team for years.
Technicians who previously spent two to four hours per week chasing open tickets no longer carry that load. The 40 hours per week that had been absorbed by follow-up work across the team is now available for billable, client-facing work.
Toni's role changed in a way that reflects the actual value she brings. She manages escalations, coordinates onsites, and handles the work that requires 11 years of institutional knowledge, rather than spending her day sorting tickets that AI can now handle.
The voice overflow agent removed the service manager from the dispatch fallback position during off-hours. When Toni is unavailable and technicians are busy, Fred handles the queue. Clients get a ticket number. The service manager stays focused on his actual job.
ATG also maintained a 13-week streak of 100% customer satisfaction scores through the transition, a signal that the client experience improved alongside the operational one.
And when new clients came on, ATG absorbed them. No new Tier 1 hires. The efficiency Thread created made room for growth that would otherwise have required headcount.
Did Thread reduce the manual triage burden on the dispatcher? Yes. Toni no longer sets prioritization or categorization on any ticket. Thread handles both automatically, leaving her to focus on scheduling and escalation decisions.
Did Thread eliminate the service manager as a dispatch fallback? Yes. The voice overflow agent intercepts calls when the team is unavailable, generates tickets automatically, and removes the need for leadership to monitor the phone queue.
Did Thread help ATG scale without hiring? Yes. ATG absorbed client growth during this period without adding Tier 1 headcount, a direct result of the capacity freed by automated follow-up and triage.
For Alvarez Technology Group, Thread wasn't a bet on AI as a concept. It was a practical answer to a specific question: how do you keep growing without growing your headcount?
The answer was removing the manual loops that were quietly consuming the team. Triage automation gave the dispatcher her time back to focus on impactful service operations. Voice overflow gave the service manager his focus back. Ticket follow-up automation gave engineers their mornings back. Forty hours a week, recovered.
Twenty-five years of client loyalty didn't require disruption. It required a tool that worked the way the team already worked, and improved from there.
Takeaway: Alvarez Technology Group shows that MSPs running ConnectWise Manage can recover 40+ hours of weekly capacity by deploying Thread as their AI service desk layer, without replacing their dispatcher, retraining their team, or disrupting the client relationships they've spent decades building.