MSP ✦ Service desk ✦ Dedicated

Service desk
agent

Tickets triaged and categorised properly, level 1 requests resolved to your runbooks, and the queue accurate enough that your engineers open a ticket already understood.

Looking for this kind of work yourself? Apply at staffingsolutions.ph — this page is written for businesses hiring.
$14/hrFrom, + GST · full-time
Up to 70%Vs. a local hire
Level 1Resolved, not escalated
~2 wksBrief → first day

Your engineers are the most expensive triage layer available

In most small MSPs there is no real triage. A ticket arrives, an engineer picks it up, and half the time it is a password reset or an access request that took two minutes and interrupted an hour of focused work.

The cost is not the two minutes. It is the context switch, and the fact that the engineer who could be doing project work is instead running the queue.

A dedicated service desk agent absorbs the volume: triage, categorisation, information gathering and everything covered by a runbook. Your engineers get a queue of genuine technical work.

What they handle

  • Ticket triage — Every ticket categorised, prioritised and routed against your matrix, with the obvious diagnostic information gathered before an engineer opens it.
  • Level 1 resolution — Password resets, MFA re-enrolment, access requests, licence assignment, mailbox permissions and standard provisioning — anything with a documented runbook.
  • Information gathering — Screenshots, error text, affected users, time of onset and reproduction steps collected up front, so an engineer is not asking basic questions on day two.
  • Queue hygiene — Statuses accurate, stale tickets chased, and "waiting on client" actually meaning that — so your SLA reporting is real.
  • Time entry chasing — Engineers chased for time entries, so billing reflects the work rather than what anyone remembered.
  • Alert triage — Monitoring alerts reviewed against your rules, noise suppressed, genuine issues escalated with context attached.
  • Onboarding and offboarding — User provisioning and deprovisioning run to a checklist — the process where security gaps most often appear.
  • Client updates — Clients kept informed on open tickets, which is what drives satisfaction scores more than resolution speed.

Where to draw the access line

The technical work travels further in IT than most industries. The boundary is privileged access and change authority, not capability.

  • Standing privileged accessGlobal admin and domain admin should be scoped, time-bound and logged — never standing access for a service desk role.
  • Production changesAnything outside a documented runbook goes to an engineer under your change process.
  • Security incident decisionsContainment and response decisions require your senior engineers.
  • Client contractual mattersScope, billing and contract conversations stay with your account managers.
More IT roles

Related roles

All IT roles →
Questions

Frequently asked

Is the talent pool deep enough for service desk work?
It is one of the deepest we have — the global MSP and BPO industry has been hiring in the Philippines for two decades, so genuine service desk experience with Australian and US clients is common. We verify it by asking what they resolved, not whether they have used a tool.
How do we handle privileged access safely?
The same way you should for local staff: named accounts, least privilege, just-in-time elevation where your tooling supports it, full logging and no shared credentials. Location is not the risk factor — standing global admin is, wherever the person sits.
Can they cover after-hours?
Yes, and it is one of the strongest arguments for offshore in IT. Manila covers your evening naturally, so after-hours triage stops being an on-call burden for your local engineers.
How much does it cost?
From $14/hr + GST full-time — up to 70% less than a local hire, with no placement fee. Run your numbers →
Full-time, part-time or fewer hours?
Forty hours a week is our standard engagement and twenty is common. Below that we look at fifteen, ten or even five hours to get a role started, priced accordingly — a smaller engagement costs a little more per hour because the recruiting and management effort is the same. Plenty of clients begin at ten hours and grow the role once they see what comes off their desk.
Is there a minimum term?
Three months, then month to month. It's the same runway you'd give a new local hire to learn your systems, your clients and your standards — and the team members who get a fair run are the ones who stay for years. There are no exit penalties at any point, and if the issue is the person rather than the role, the first-week refund and free replacement cover that separately.
How do you handle confidentiality?
The same way you'd treat any remote team member. Every placement signs an NDA and a confidentiality clause before day one, and they work inside your systems — your email, your CRM, your file storage — so you control what they can see and can revoke access instantly. No client data is stored on our side.