How Do You Hire an Offshore Zendesk Administrator or Support Specialist?
Most companies hiring for Zendesk write one job description and get one of two very different people.
One resolves tickets well and never touches the configuration. The other builds a clean trigger architecture and is slow in the queue. Both are competent. Only one matches what you needed, and which one you got tends to become clear in month two.
This guide separates the two roles, gives a screening exercise that tells them apart in an hour, and prices each against a task-matched occupation code rather than a blended support average.
What Does an Offshore Zendesk Administrator Do?
An administrator configures the platform rather than working the queue: triggers, automations, macros, views, SLA policies, Guide article structure, Explore reporting, and app integrations. The work is closer to systems administration than to customer service, and it is usually a poor fit for someone hired purely on ticket throughput.
The specific scope covers:
Trigger and automation logic. Auto-routing by tag, form, or channel; SLA warning escalations; satisfaction surveys with conditional exclusions. This is where most instances quietly break, because triggers accumulate over years and nobody owns retiring them.
Macro library maintenance. Building macros for recurring ticket types, and retiring the ones that no longer match current policy. An outdated macro library is worse than none, because agents send stale answers with confidence.
Views and group structure. Shared views per team, personal views for efficiency, and group routing that reflects how the team is actually organised today rather than two reorganisations ago.
Zendesk Guide. Help-centre article structure, maintenance, and search behaviour, which is the difference between deflection working and customers filing tickets anyway.
Explore reporting. Custom dashboards for first reply time, CSAT, and volume by agent or channel, built to match the metrics leadership actually asks for.
Integrations. App and API connections to storefronts, CRMs, and issue trackers, plus the maintenance those connections need when either side ships a change.
Zendesk Administrator vs Support Specialist: Which Do You Need?
A support specialist resolves tickets and maintains the macro library. An administrator builds and fixes the configuration underneath. Under roughly 500 tickets a month one person usually covers both. Above that, splitting the roles stops configuration work from being permanently deprioritised behind the live queue.
| Function | Support specialist | Zendesk administrator | Where F5 places |
|---|---|---|---|
| Ticket resolution | Primary responsibility, Tier 1 and 2 | Occasional, usually escalations only | Yes, through the customer support role |
| Macros and tagging | Uses and suggests | Designs, builds, and retires | Yes, both levels |
| Triggers and automations | Rarely | Owns the logic end to end | Yes, as an administration-weighted placement |
| Explore reporting | Reads dashboards | Builds dashboards | Yes, screened for specifically |
| Integrations and API work | No | Configures and maintains | Scope-dependent; confirm on the discovery call |
| Who should NOT use F5 | Companies needing a W-2 US employee, on-site presence, or coverage for under six months |
The honest version of the split: if the queue is the problem, hire the specialist. If the queue is fine but the reporting is wrong and nobody trusts the SLA numbers, the problem is configuration and a faster ticket-handler will not touch it.
What Does a Zendesk Hire Cost Compared With a US One?
Two occupation codes cover this work, and they are far apart. Using one blended support average hides that.
Customer service representatives earn a $44,770 median (BLS OEWS May 2025, SOC 43-4051). Loaded at x1.4265 (BLS ECEC, Dec 2025): 44,770 x 1.4265 = $63,864 per year.
Computer user support specialists, the closer match for administration work, earn a $61,860 median (BLS OEWS May 2025, SOC 15-1232). Loaded the same way: 61,860 x 1.4265 = $88,243 per year.
Both figures are wages plus employer-paid benefits and taxes. Neither includes recruiting, equipment, or software.
F5 Hiring Solutions places at $375-$1,200 per week, all-inclusive, which is $19,500 to $62,400 per year at 52 weeks. One rate covers salary, HR, payroll, equipment, and F5 management, with no recruiting fee, setup fee, or termination cost.
Price the role against the right code. Comparing an administrator against the customer-service median understates the US side; comparing a Tier 1 hire against the user-support median overstates it.
The loading multiplier is an economy-wide ratio applied to a national median. Treat it as a planning figure, not a quote.
How Do You Screen for Real Zendesk Depth?
Set a practical exercise rather than asking about features. Anyone can list Explore and Guide on a profile; configuration ability shows up in an hour of actual work.
Task 1, ticket response. Three sample tickets: a refund request, a product complaint, a shipping delay. Judge tone, policy adherence, completeness, and whether the writing apologises appropriately without over-apologising.
Task 2, macro creation. "We get thirty tickets a day about the return policy. Build a macro." Judge structure: subject handling, body, tags applied, resulting ticket status, and whether it can be sent without editing.
Task 3, trigger logic with an exclusion. "Send a satisfaction survey twenty-four hours after a ticket is solved, but only if it was never escalated." The conditional exclusion is the whole test. Candidates who can build the simple version and not the exclusion are ticket-handlers, not administrators.
Task 4, Explore. "What report would you build to track agent performance, and what would you deliberately leave out?" The second half of that question is the useful half.
Task 3 is the single strongest signal for administration work. Task 1 is the strongest for queue work. Weight them according to which role you are actually filling.
The Access Setup
Zendesk uses role-based user management, so the access decision follows the role split directly.
For ticket handling: add as Agent with standard permissions, scoped to the relevant views and groups. Agent access covers full ticket management without account-level or billing access.
For administration: add as Admin. That covers triggers, macros, views, automations, integrations, and Explore. Admin access does not include billing, which stays with the account owner.
In both cases: enable two-factor authentication, review the activity log periodically for configuration changes, and give the person a sandbox to test configuration before it touches production. Never share account-owner credentials.
Philippines or India?
The Philippines suits customer-facing ticket handling and Guide article writing, where written communication quality is the constraint. India suits administration and configuration work, where trigger logic, integrations, and Explore reporting matter more.
The rate band is identical either way, so the choice is role-specific rather than cost-driven. F5 shortlists from both hubs unless the brief specifies one.
Honest Limitations
F5 does not publish a per-specialism sub-band. Where a Zendesk role lands inside $375-$1,200 depends on whether it is queue-weighted or administration-weighted, and that is confirmed on the discovery call rather than quoted from a page.
Deep API and app development is scope-dependent. Configuring and maintaining existing integrations is standard. Building a custom Zendesk app is engineering work and should be scoped as such before you assume it is covered.
F5 places from India and the Philippines only, not Latin America, Eastern Europe, or Africa, and not onshore US.
There is no self-serve portal. A discovery call comes before any profile is shared.
Who Should NOT Use F5
Companies needing a W-2 US employee, an on-site presence, or coverage for under six months. Every placement is a full-time hire rather than a task-based contract, so short bursts of overflow support are the wrong fit.
Bottom Line
Decide whether you are buying queue throughput or platform configuration before you write the job description, because the two hires screen differently and rarely overlap in one person below senior level.
Price the role against SOC 43-4051 or SOC 15-1232 depending on which it is. F5 Hiring Solutions places either at $375-$1,200 per week, all-inclusive, with a shortlist in 7-14 business days and replacement at zero cost.
For the role page, see full-time remote customer support from the Philippines. For the cost math, see customer support cost, Philippines vs USA. For the hiring process, see how to hire remote customer support from the Philippines.