What Fixify launched
On 4 November, US company Fixify announced general availability of Fixify for MSPs. It's a managed service in which AI agents work routine Level 1 tickets from first contact through to closure. At launch, the agents handle the everyday requests that fill an L1 queue: resetting passwords and MFA, unlocking accounts, granting app access, changing group memberships, and the routine steps when staff join or leave. The agents connect to Microsoft Entra ID, Microsoft 365, Google Workspace and Okta. They record their work in the MSP's professional services automation (PSA) tool, which is where the MSP logs and bills its support tickets. Fixify supports ConnectWise, Kaseya Autotask, HaloPSA and NinjaOne. According to the release, Fixify's own IT analysts watch the agents around the clock and step in when a request needs human judgement or approval.
Fixify's pricing model is the bigger change. MSPs pay per completed ticket, with no platform fee, setup fee or per-seat charge. The pricing page counts a ticket as completed once Fixify has worked it through to resolution and closure in the PSA, documentation included. The page recommends a volume of at least 200 Tier 1 tickets a month and doesn't publish a dollar rate.
For now the service is sold only in the United States and Canada, so NZ firms can't buy it today. We're still writing about the launch because the model will reach local MSPs, through Fixify or through the PSA and RMM vendors they already use. If your IT support is outsourced, your provider may start routing your access requests through an AI agent before you've been asked.
Why the ticket list deserves attention
Most of the ticket types on Fixify's launch list change who can get into your systems. A password reset, an MFA change or a new group membership grants access, and a missed offboarding step leaves access in place after someone has gone. Those are the requests attackers try to trigger.
New Zealand's National Cyber Security Centre published a focus piece on attacks against helpdesks in its Quarter Two 2025 insights report. It describes callers posing as staff to get passwords reset or MFA moved to a device they control, and says the NCSC knows of similar techniques used to get into a number of New Zealand organisations. The NCSC recommends clear criteria for verifying callers before any reset or MFA change, and a defined process for callers who can't verify. It also tells organisations to assess the risk in the access they give managed service providers, because attackers target those providers too.
An AI agent working those tickets doesn't remove the attack. The agent will follow whatever verification steps sit in its playbook. If your MSP's current process lets a confident caller through, an automated version will let the same caller through faster and at 3am. Fixify's MSP page says any skill or action can be set to need human approval and that each action gets a risk score. Neither the release nor the MSP page explains how the agents confirm a requester's identity before a password or MFA reset. Buyers should get that answer in writing from whoever runs the service.
Per-ticket pricing changes the incentives
Most NZ managed service contracts we see bill per user, per device or as a monthly block of hours. Under those models the provider gains when tickets go away, because fewer tickets means less work for the same fee. A per-resolved-ticket charge flips that between the MSP and its automation supplier. The supplier earns more when more tickets close, and the definition of "resolved" decides what gets counted.
Fixify's pricing page says partial work is only billed when both parties have agreed in the contract that it's worth paying for. That's a reasonable starting point, but the arrangement sits between Fixify and the MSP. You'll see the effect in your own service: how fast tickets close, how many get reopened, and whether a request marked resolved actually left the person able to work. Few SME contracts track reopen rates today, and agent-driven closure makes that measure much more useful.
The release gives no figures for resolution rates, time saved or error rates, so nobody outside Fixify and its customers can judge the agents' accuracy yet. Treat any savings your MSP quotes as a vendor claim until it's backed by your own ticket data.
What it means for NZ businesses
The pattern matters more than the vendor. MSPs on both sides of the Tasman are under the same margin pressure that Fixify's chief executive pointed to: keeping up with client growth without hiring technicians at the same rate. Expect AI ticket handling to show up as a feature of the PSA or RMM platform your provider already uses, or as a subcontracted service. You might only hear about it from a line buried in a contract variation.
Service management practice already gives you the tools to handle the change. A clear service catalogue, agreed request types, defined approval steps and change records apply whether a person or an agent closes the ticket. Firms that have put a structured ITSM framework in place will find it much easier to say which requests an agent may complete alone and which need a human sign-off.
Practical next steps
- Ask your MSP in writing whether any AI agent, its own or a subcontractor's, currently works your tickets or will in the next 12 months, and which ticket types it covers.
- Get the identity verification steps for password resets, MFA changes and access grants written down. Check them against the NCSC criteria, including what happens when a caller can't verify.
- Mark privileged accounts, finance system access and MFA changes as requiring human approval, whatever tool closes the ticket.
- Add reopen rate and time to restore working access to your service reports, alongside the usual ticket counts and response times.
- Check where agent actions are logged and make sure your own team can see them. An audit trail kept only inside the MSP's PSA won't help much during an incident review.
- Write offboarding as one checklist with named owners. Automated offboarding only works when the steps it runs are complete.
- If your provider moves to per-ticket or outcome pricing, settle what counts as resolved before you sign. Check whether a ticket reopened within a set number of days still gets billed.
If you're redesigning request handling ahead of this, our process and automation work starts with the same questions: what can safely run without a person, and what evidence shows that it did.
Sources
Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.
Get my free assessment How we help