IT & managed services
support
Tickets triaged and kept accurate, asset registers current, licences renewed before they lapse, documentation actually written and client reporting produced on schedule — the work that makes an MSP scalable.
MSPs scale on documentation, and nobody writes it
Every managed service provider knows the constraint: growth is limited by how much of the environment lives in engineers' heads. Documentation is the fix and it never gets written, because the engineer who could write it is billable.
The same applies to the surrounding work — ticket hygiene, asset registers, licence renewals, client reporting. All necessary, none of it requiring an engineer, all of it done by engineers.
Offshore support takes that layer. Your engineers stay on the technical work; the administration, triage and documentation happen consistently instead of when there is a gap.
What comes off your engineers
- Service desk triage — Tickets categorised, prioritised and routed to the right engineer against your matrix, with the obvious information gathered before an engineer opens it.
- Level 1 resolution — Password resets, access requests, standard provisioning and documented fixes handled to your runbooks.
- Ticket hygiene — Statuses accurate, stale tickets chased, time entries chased from engineers, so your reporting and billing reflect reality.
- Asset and licence registers — Hardware, warranties, licences and subscriptions tracked with rolling renewal dates — the thing that always lapses quietly.
- Documentation — Runbooks, network diagrams and client environment notes written up from engineer input and kept current.
- Onboarding and offboarding — User provisioning and deprovisioning run to a checklist, which is where security gaps usually appear.
- Monitoring alert triage — Alerts reviewed against your rules, noise suppressed, genuine issues escalated with context attached.
- Client reporting — Monthly reports produced consistently — tickets, uptime, patching and recommendations.
The work that comes off your desk
Most of an MSP's cost is engineer time, and a large share of that time goes on work that is not engineering: setting ticket types, reconciling seat counts, chasing serial numbers off a delivery, keeping IT Glue current after the project closed. It accumulates quietly in the PSA and the RMM, and it is the first thing dropped the moment a P1 lands.
Works the ConnectWise PSA, Autotask or HaloPSA service board from the start of the Australian day: sets type, subtype, priority and board, attaches the correct agreement, merges duplicates, and clears documented runbook items such as password resets, mailbox permissions and print queues before an engineer picks it up.
Keeps the dispatch board honest. Matches tickets to engineer skill and availability, books onsite visits around travel time, reshuffles when an outage lands, and chases tickets sitting in Assigned with no time entry against them or no note since yesterday.
Audits closed tickets for missing time entries, wrong agreement mapping and blank resolution notes so contract hours reconcile at month end. Reopens anything closed without a documented fix and pushes the detail back into the ticket before it goes anywhere near an invoice.
Runs the daily aged-ticket and SLA views in Autotask or HaloPSA, follows up clients sitting in Waiting on Customer, and escalates anything approaching a response or resolution breach to the service delivery manager with the ticket history already summarised.
Reconciles seat counts three ways each month: what the tenant shows in the Microsoft 365 admin centre, what the distributor bills through Pax8, Crayon or Dicker Data, and what the PSA agreement charges the client. Flags orphaned licences on disabled accounts and unassigned seats still being paid for.
Keeps configuration records current in the PSA and RMM: serial numbers, Dell, HP and Lenovo warranty expiry, device age, assigned user and site. Produces the list of machines out of warranty or off the supported Windows build for the client's technology roadmap.
Maintains the client documentation set: ISP and circuit records, DNS registrar and domain renewal dates, application vendor and support contacts, licence keys, and standard operating procedures. Chases engineers for detail after a project closes so it does not stay in one person's head.
Reviews the overnight patch compliance report in NinjaOne, Datto RMM or Intune and backup job results in Datto, Veeam or Backup Radar. Reports only the exceptions — failed jobs, devices pending reboot, agents that stopped checking in — with the ticket already raised against each.
Takes the onboarding form from the client's HR contact through the documented build: creates the account, assigns groups and licences, sets mailbox delegates and shared drive access, raises the hardware order, and books the engineer for imaging and day-one handover.
Executes the offboarding runbook step by step: revoke sessions, convert the mailbox to shared, set forwarding and delegate access to the manager, remove from distribution lists and security groups, reclaim the licence, retire or wipe the device, and record the date each step was completed.
Raises quotes and purchase orders in the PSA, places orders with Dicker Data, Ingram or Synnex, tracks ETAs and backorders, collects serial numbers on delivery for the asset register, and matches supplier invoices back to the original quote before the client is billed.
Assembles the pack ahead of the technology business review: ticket volumes by type and site, SLA performance, patch and backup compliance, asset age and warranty position, licence counts and outstanding recommendations, so the vCIO arrives with figures already checked.
Works the alert queue rather than letting it become wallpaper. Closes self-resolving alerts such as disk space that recovered or a scheduled reboot, raises tickets for anything persisting, and keeps a running list of noisy monitors so thresholds get tuned instead of ignored.
What stays with you
We are a staffing company, so this list argues against our own interest. It is also the part that matters: the work below is reserved, and no amount of supervision moves it. Get the line written down before anyone starts in an MSP.
- Assessing and notifying a data breachWhen personal information is exposed, the client entity must assess whether it is an eligible data breach — an assessment the Act requires to be completed within 30 days — and notify affected individuals and the OAIC. Outsourcing the systems does not outsource that duty; the call is made onshore by the accountable person.OAIC, Privacy Act 1988 (Notifiable Data Breaches scheme)
- Cyber incident response decisionsIsolating systems, engaging insurers and counsel, and deciding what is reportable are the client's decisions, not a contractor's. Where the client is a responsible entity for a critical infrastructure asset in one of the sectors prescribed by the SOCI Act, a critical cyber security incident having a significant impact must be reported within 12 hours and an incident having a relevant impact within 72 hours; most MSP clients sit outside that scheme, and the ones inside it cannot delegate the call. A separate duty under the Cyber Security Act 2024 requires businesses over the turnover threshold to report a ransomware payment. A contractor can gather evidence and draft the timeline; only the responsible entity authorises the response.CISC (Department of Home Affairs), Security of Critical Infrastructure Act 2018; reports made to ASD's ACSC
- Fixed cabling and onsite workInstalling or modifying customer premises communications cabling requires an ACMA-registered cabler physically present, who certifies the work against the wiring rules. Unregistered people may only work under direct supervision. No remote role touches this at all.ACMA, Telecommunications (Cabling Provider) Rules 2025
- Deciding what offshore staff accessUnder APP 8 the client stays accountable for personal information disclosed overseas. The client decides the access level, which tenants, vaults and datasets are in scope, and enforces it in their own systems rather than relying on assurances.OAIC, Australian Privacy Principle 8, Privacy Act 1988
- Classified and government-related client dataWork touching security-classified government information must be handled by appropriately cleared Australian personnel in assessed environments, with clearances issued by AGSVA rather than granted by an employer. Offshore contractors are excluded from that scope entirely, so those clients or those systems stay with the onshore team.Protective Security Policy Framework (Department of Home Affairs); security clearances via AGSVA
Roles for MSPs and IT teams
Service desk support specialist
Triage, level 1 resolution and ticket ownership.
Explore →Help desk support specialist
End-user support to your runbooks.
Explore →IT service management support
Process, reporting and ITSM administration.
Explore →System administrator
Server, identity and infrastructure administration.
Explore →Database administrator
Database maintenance, backups and performance.
Explore →QA tester
Test execution, regression and defect reporting.
Explore →Where to draw the security line
The technical work travels further in IT than in most industries. The boundary is about privileged access and change authority, not capability.
- Privileged credentialsGlobal admin and domain admin access should be scoped, time-bound and logged — not standing access for a new starter.
- Change authorisationProduction changes are approved by your engineers or change process, never self-authorised.
- Client contractual mattersScope, billing and contract conversations stay with your account managers.
- Security incident responseContainment decisions during an incident require your senior engineers.
Specialist roles for MSPs
Three dedicated roles that free your engineers from triage, documentation and licence admin.
Service desk agent
Triage, level 1 resolution and queue hygiene.
Explore →Documentation specialist
Runbooks and client environments — the thing that never gets written.
Explore →Licence & asset administrator
Registers, renewals and billed-vs-purchased reconciliation.
Explore →