Partner Spotlight: How Integritek’s William Kapes Uses AI to Save Teams 5 Hours a Week

Technical teams now support more users, cloud tools, security controls, and documentation without adding internal drag. The question is not whether AI sounds impressive. It is whether AI helps a technician close a ticket faster, document a site visit clearly, or give a manager better visibility before a deadline slips.

That is where MSP AI automation, AI for technical operations, Hatz AI use cases, and MSP workflow automation belong: inside operational maturity, not the part of the presentation with the galaxy background. Technical teams today support more systems than ever. In a recent Hatz AI Partner Roundtable, William Kapes, Director of Technical Operations at Integritek, shared how our team uses practical AI to cut manual work in half.

As William Kapes notes: “Start with the repetitive tasks your team already hates. Small wins build momentum fast.”

MSP AI Automation Should Start With The Work Your Team Already Hates

Durable AI adoption starts with repetitive workflows that already slow down technicians and managers.

• Skip the grand plan: Ticket summaries beat vague automation roadmaps when the helpdesk queue is full.

• Earn small wins first: Staff see value when AI reduces typing, not when it asks them to become prompt poets.

• Start where work repeats: Site visit notes, inventories, reports, and documentation cleanup are natural first targets.

• Tie time to handoffs: With 93% of teams saying AI helps save time, the case is clearer when fewer delays and less rework show up in service delivery.

The next step is seeing where those wins appear in real workflows, especially when the organization has outgrown informal IT support but does not need a full internal department.

Capability areas include helpdesk triage, field documentation, secure cloud access, and reporting.

AI For Technical Operations Works Best When The Process Is Already Understood

AI supports known workflows best because the team already knows where judgment, escalation, and review belong. We see this in managed IT work across professional services environments, where the failure point is often a missing note, unclear ticket history, or late follow-up that affects a client deadline. NBER research found support productivity increased by an average of 14% when professionals used AI agents.

• Ticket intake: Summaries help technicians spot affected users, systems, and deadlines.

• Knowledge base drafts: Cleaner first drafts reduce manager rewrite time.

• Handoff notes: Escalations carry context, so the next person does not reconstruct the last three emails.

• Follow-up tasks: Extracted next steps reduce forgotten vendor updates, replies, or approvals.

Hatz AI Use Cases From The Field Show Where Time Savings Become Visible

Real-world snapshot: When an Integritek field tech snaps photos of a client’s server rack, they email them to the Field Tech Agent. In one visit, the agent scanned a photo, identified an aging SonicWall TZ370 firewall, flagged it as End-of-Life (EOL), and created an automated action item for the account manager to quote a replacement.

Anthropic found the median conversation had an estimated 84% time savings, with variation by task. We test these uses internally first because client service depends on repeatable output, not impressive demos that fail when a label is half peeled off a switch.

MSP Workflow Automation Reduces Delays Across Support Handoffs

1. Faster context for tickets

   Helpdesk staff see the user, device, recent changes, and business impact sooner. That reduces rework when a billing system login, document access issue, or cloud permission problem blocks staff.

2. Cleaner field-to-office handoffs

   Photos, notes, and part details move into usable records, so project engineers do not chase missing model numbers.

3. Better leadership visibility

   Our flat-rate managed services and active account management work better when approvals, open risks, and recurring issues are visible without turning status meetings into archaeology.

4. Less internal chasing

   AI-supported workflows improve productivity and collaboration, including 51% increased productivity, 51% more automation, and 48% increased cross-functional collaboration. The result is cleaner ownership between technicians, vendors, account managers, and client contacts.

A Field Tech AI Agent Turns Site Data Into Usable Next Steps

A technician finishes a site visit, captures photos of switches, cabling, battery backups, and labels, then has to turn messy observations into documentation someone else can use.

• Equipment identification: Photos help draft lists of models, serials, and locations for human review.

• Replacement flagging: End-of-life notes prompt budget or approval conversations before hardware failure becomes the planning committee.

• Procurement next steps: Missing parts move into purchasing requests with clearer quantities and vendor details.

• Readable ticket updates: The next technician sees what changed, what remains open, and why the visit matters.

A field tech AI agent is useful when it reduces repeat visits, creates cleaner ticket handoffs, and cuts vendor confusion. Anthropic found hardware issues saw time savings of 56%.

An Internal AI Deployment Strategy Needs Champions, Not Theater

An internal AI deployment strategy works when leaders can see actual use, outcomes, and guardrails. William’s team reviews token usage in the admin console to find power users, then asks what problems they are solving. That matters because Gartner has predicted that by 2030, 80% of routine project management tasks will be handled by AI.

1. Start with repetitive tasks

   Pick work tied to tickets, reports, or documentation, where the before-and-after comparison is visible.

2. Watch actual usage patterns

   Look for adoption in daily work, not announcements. A launch email is not a workflow.

3. Ask power users directly

   They know which prompts save review time, reduce typing, or make handoffs cleaner.

4. Share useful workflows

   Turn repeated wins into shared procedures so staff know when AI belongs in the process and when it does not.

Calculating AI ROI For Smbs Should Start With Time Saved

Calculating AI ROI for SMBs starts with time because time is where the pain shows up first: late approvals, stalled tickets, delayed billing updates, and technical staff doing clerical cleanup instead of higher-value work. Cutting a 10-hour weekly reporting task to 5 hours gives a smaller firm value it can see in schedules, handoffs, and open work.

Measure the workflow before calling it successful:

• Hours saved weekly: Compare the old task time with the new one.

• Reduced review time: Track manager edits on reports or ticket notes.

• Faster response: Watch turnaround on tickets, approvals, and status updates.

• Lower opportunity cost: Keep skilled staff on technical work instead of repetitive cleanup.

IT Operations Time Savings Depend On Secure Access And Clean Governance

IT operations time savings lose value when staff paste confidential client files, billing information, legal updates, approvals, or internal documents into unmanaged tools. Integritek Secure AI, Powered by Hatz.ai, gives organizations a secure AI platform with consumption-based pricing, so teams can test useful workflows without creating shadow systems around sensitive data.

• Secure user access: Staff use approved accounts tied to role and need.

• Usage visibility: Leadership can see adoption, cost, and risky patterns.

• Practical guardrails: Policies match real tasks, such as summarizing ticket notes or drafting internal documentation.

• Clear approval paths: New use cases move through review before rollout, especially when compliance or confidentiality is involved.

Consumption-Based Access vs. Per-Seat Gatekeeping

Traditional AI platforms use per-seat monthly licenses, forcing companies to gatekeep who gets access. By using Hatz AI’s consumption model, Integritek gives AI logins to everyone—from tier-1 techs to warehouse staff—without paying extra per-user fee penalties.

Leadership tracks token usage in the admin console to easily spot natural “power users” who become internal AI champions.

Integritek Hatz Partner Spotlight Lessons For Growing Technical Teams

Change is difficult because teams already have tickets, projects, client requests, and vendor follow-ups moving at the same time. The Integritek Hatz partner spotlight shows why next steps should stay modest, measurable, and close to daily operations. Our longevity helps here: we have seen enough messy handoffs to know where pattern recognition beats theater, with local service supported by Lyra Technology Group scale.

• Pick one workflow: Choose a high-friction task, such as recurring client reports or field visit documentation.

• Define before and after: Record the time spent now and compare it with the new process.

• Test internally first: Do not experiment on client deadlines.

• Review usage data: Find champions through behavior, not meeting-room enthusiasm.

• Standardize what works: Turn useful prompts or agents into repeatable procedures.

Make AI Useful Before You Make IT Bigger

Start with repetitive technical work, measure time saved, protect sensitive data, and expand only after the workflow proves useful in tickets, documentation, approvals, or vendor coordination. That is how AI becomes part of stable operations instead of another tool someone has to babysit.

If you want a practical review of secure AI, managed IT, or technical operations improvements, contact Integritek for a complimentary consultation. We will give you a direct read on where AI fits, where it does not, how our 90-day guarantee applies, and whether the first useful win is as simple as cleaning up the site-visit notes that keep slowing everyone down.