Hiring customer support staff in the Philippines is the most common first step companies take when they outsource, and for good reason: the country is widely seen as the world’s main hub for English-language customer support, the labour pool is deep, and the time zone can be made to fit a US, UK or Australian business day. It is also easy to get wrong. Hire on rate, skip the practical interview and hand over the queue with no onboarding, and you will get exactly the offshore support experience your own customers complain about.
This guide covers the practical decisions in order: which support roles to outsource, whether a dedicated team or a BPO call centre fits, how to write the job description and run the interview, how to plan shifts across time zones, what the first 30 days should look like, which KPIs to track, and how to keep customer data safe. It is written for a founder or operations lead hiring their first one to ten agents, though most of it applies at any scale.
Why the Philippines is the default for customer support
Three things make the Philippines the first place most companies look when they outsource customer service, and none of them is price.
English. English is an official language of the Philippines and the medium of instruction in schools, so agents have been reading, writing and being taught in it since childhood. The country consistently ranks among the top Asian countries on the EF English Proficiency Index. Accents are generally neutral and, unlike some offshore locations, written English is a strength rather than a weakness — which matters when most of your tickets arrive by email and chat.
Service culture. Customer support is a respected, mainstream career in the Philippines rather than a stopgap. Agents are used to working for foreign companies, to Western customers and to Western expectations of tone. The stereotype of Filipino patience and warmth on the phone is a stereotype, but it exists for a reason, and you will notice it in interviews.
Scale. The industry body IBPAP puts the Philippine IT-BPM sector at roughly 1.7–1.9 million people and around US$35–40 billion a year in revenue, a large part of which is customer support and customer experience work. In practice this means experienced Filipino customer service representatives exist for almost every tool, industry and channel you can name. Someone who has worked a Zendesk queue for a US software company, or a Gorgias inbox for a Shopify store, is not hard to find.
Cost is real, but it comes fourth. Third-party industry guides report fully-loaded rates for Philippine staff in the region of US$8–18 per hour depending on role and seniority, with savings of 50–70% against equivalent local hires. Treat that as orientation, not a quote: our pricing page explains how a dedicated-staff rate is actually built, and why the Philippines makes the wider case.
The roles inside “customer support”
“Customer support” is not one job. Before you write a job ad, decide which of these you are actually hiring for, because the skills, tools and shift patterns differ.
| Role | What they do | Core skills | Typical tools |
|---|---|---|---|
| Tier-1 chat and email agent | First response to inbound tickets, FAQs, order status, account changes, password resets | Clear written English, speed with macros, empathy in text, triage | Zendesk, Freshdesk, Intercom, Gorgias |
| Phone support agent | Inbound calls, callbacks, voicemail follow-up | Neutral accent, active listening, call control, composure | Aircall, Zendesk Talk, RingCentral |
| Tier-2 / technical support | Escalations, bug reproduction, integrations, account-level fixes | Product depth, troubleshooting logic, clear bug reports for engineering | Intercom, Jira, admin panels, log viewers |
| E-commerce order support | Where-is-my-order, returns, refunds, exchanges, chargeback responses | Attention to detail, policy judgement, speed | Shopify, Gorgias, Amazon Seller Central, ShipStation |
| Social-media support | Public replies and DMs on Instagram, Facebook, X and TikTok; review responses | Brand tone, de-escalation in public, knowing when to take it private | Meta Business Suite, Sprout Social, Gorgias |
| Team lead | Rostering, QA sampling, coaching, escalations, reporting | Two to three years on the floor, coaching ability, spreadsheet fluency | Your helpdesk’s reporting, Google Sheets, Slack |
Most companies hiring their first agent want a tier-1 chat and email generalist who can grow into tier-2. E-commerce brands usually want the order-support profile, which overlaps with the e-commerce roles we place; B2B companies with a sales team often pair a support agent with sales support so that leads and tickets do not fall between the two. The customer support role page lists the full set of profiles.
Dedicated team or BPO call centre?
There are two ways to outsource customer service to the Philippines, and they are not interchangeable.
A BPO call centre sells you an outcome: tickets answered within an SLA, calls handled, a per-minute or per-ticket price. The agents are the BPO’s employees, work from the BPO’s scripts, and are typically shared or rotated across clients. You get scale and coverage fast, and you get less control over who is answering, how they are trained and how much of your product they actually understand.
A dedicated support team is a person or team sourced and screened for you, working only on your queue, trained and managed by you day to day, with a Philippine provider handling payroll, HR, statutory contributions and the office. They are your staff in every way that matters to a customer; they are simply engaged locally.
| Dedicated support team | BPO call centre | |
|---|---|---|
| Who manages the agents | You | The BPO |
| Who trains them | You, on your product | The BPO, on scripts |
| Volume it suits | 1–30 agents, steady | Larger seat counts, spiky or seasonal |
| Product complexity | Medium to high | Low |
| Pricing basis | Monthly rate per person | Per seat, per ticket or per minute |
| Brand tone | Yours, because they are yours | The BPO’s house style |
| Replacing an agent | You interview replacements | The BPO swaps them |
The honest rule of thumb: if your product takes more than a week to learn, if tone matters to your brand, or if you need fewer than about twenty seats, the dedicated model is nearly always the better fit. If you need 200 agents for a six-week seasonal spike on a simple script, a BPO is the right tool and a dedicated provider should tell you so. The BPO vs dedicated staffing guide compares the models in detail.
Hiring: the job description and the interview
A job description structure that works
Filipino support candidates read a lot of job ads, and the good ones filter hard for clarity. A vague ad (“customer service representative, must be a team player”) attracts volume; a specific one attracts the people you want. A structure that works:
- Title and one-line summary. “Customer Support Specialist (chat and email) for a US software company — night shift, office-based, Bohol.” State the shift and the setup up front; it saves everyone a wasted interview.
- About the company and the product. Three or four sentences. Candidates want to know what they will be supporting and for whom.
- Responsibilities. Six to ten concrete bullets. “Answer 40–60 chat and email tickets per shift in Zendesk” beats “handle customer enquiries”.
- Must-haves. Two or more years in a similar role, professional written English, experience with your helpdesk or a close equivalent, comfort with the shift.
- Nice-to-haves. Your industry, your specific tools, phone experience, a second channel.
- Shift and setup. Exact hours in Philippine time, days, whether weekends rotate, office-based or not, how public holidays are handled.
- What you offer. 13th-month pay and statutory contributions (SSS, PhilHealth, Pag-IBIG), leave, equipment, and a growth path into tier-2 or team lead.
If you hire through a provider, they will usually draft this with you. The input they need from you is the responsibilities, the must-haves and the shift.
An interview process that tests judgement, not scripts
Scripts are easy to teach. Judgement — knowing when to refund without asking, when to escalate, when to say no politely — is what separates a good agent from an expensive one, and it is what you should be interviewing for.
| Stage | What you are testing | What good looks like |
|---|---|---|
| Written screening test (30 minutes, unsupervised) | Written English, structure, tone, spelling | Replies you would send as-is or with light edits |
| Mock tickets (three real anonymised tickets, 45 minutes) | Judgement, policy reading, empathy under ambiguity | They ask a clarifying question, cite the policy and offer a next step |
| Live role-play (chat and, if relevant, phone, 20 minutes) | Composure, listening, accent clarity, handling an angry customer | They slow down, acknowledge, and take control of the conversation |
| Conversation with you (30 minutes) | Motivation, shift reality, how they think about the job | Specific stories about tickets they got wrong and what they changed |
| Reference and tool check | Track record, tenure, tool claims | Two references who confirm the role and the tools |
Two details matter. First, include at least one mock ticket with no clean answer — a customer asking for something your policy does not cover — and watch whether the candidate makes a reasonable call or freezes. Second, assess English and tone separately: plenty of candidates have excellent grammar and a cold, formal register, and plenty have warm instincts with slightly loose grammar. For chat and email, warmth that needs light editing usually beats correctness with no empathy.
Shift planning and coverage
What your business day looks like in Philippine time
The Philippines is UTC+8 and does not observe daylight saving, so the offset to your office shifts by an hour twice a year. Here is what a 9am–5pm business day in each market looks like for an agent in the Philippines.
| Your market | Offset to the Philippines | Your 9am–5pm in Philippine time | What that means for the agent |
|---|---|---|---|
| US Eastern | 12–13 hours ahead | 9pm–5am or 10pm–6am | Full night shift |
| US Pacific | 15–16 hours ahead | Midnight–8am or 1am–9am | Overnight into early morning |
| UK | 7–8 hours ahead | 4pm–midnight or 5pm–1am | Afternoon-to-evening shift |
| Australia (east coast) | 2–3 hours behind | 6am–2pm or 7am–3pm | Early day shift |
For Australian companies this is the easy case: your day is their day, starting an hour or two early. UK companies get an evening shift, which most agents find workable. US companies are asking for night shifts, and that deserves some honesty.
The reality of night shifts
Night shifts are normal in the Philippine outsourcing industry; a large share of the workforce has been on a US clock for years. But three things are true. A night-shift premium is common practice, and you should budget for it. Attrition on night shifts tends to be higher than on day shifts unless the environment is good. And working from home at 3am is where remote setups fail: power cuts, a shared family connection, and nobody to swap a shift with.
This is the strongest practical argument for office-based support teams. A well-run office has backup power, redundant internet connections, security and transport arrangements for night staff, and a supervisor on site, which is why office-based night shifts tend to be safer and more reliable than home-based ones, particularly in typhoon season (roughly June to November). It is also easier to build a shift pattern: three agents in one office can cover a queue around the clock with rotating weekends; three agents in three homes usually cannot.
Two coverage tips. Do not hire a single agent for a shift that must be covered every day; one person cannot cover leave, sickness and the roughly 18–20 Philippine public holidays a year. And decide up front whether your agents follow Philippine public holidays or yours. Many companies pay the holiday and have agents work it, but that has to be written into the offer.
The first 30 days
The biggest predictor of whether an offshore support hire works out is what happens in the first month. Agents who are handed a login and told to “just answer the tickets” tend to underperform for months; agents with a structured first 30 days are usually close to full productivity by week five.
| Week | Focus | What they should have by the end |
|---|---|---|
| 1 | Product and customer training, shadowing your best person, reading a few hundred closed tickets | A mental model of the product and of who your customers are |
| 2 | Drafting replies to live tickets that you review before sending; learning the macro library | A feel for tone and 20–30 approved replies of their own |
| 3 | Answering live with a same-day review of every reply; escalation paths documented | A written escalation map: who to ask, when, and how |
| 4 | Answering live with sample review against your QA rubric; first KPI readout | A baseline QA score and a coaching plan |
Three things should exist before the agent starts, not after: a macro library (even a rough one), a one-page escalation path (what goes to engineering, what goes to the founder, what the agent decides alone), and a QA rubric. If you do not have them, the first week is you and the agent writing them together, which is time well spent. The guide to managing a Philippine offshore team covers the ongoing rhythm once onboarding is done.
KPIs, coaching and growing the team
The KPIs that matter
Five numbers tell you most of what you need to know.
- First response time. How long a customer waits for a first human reply. Set a target per channel: minutes on chat, an hour or two on email.
- Resolution time. Time from first contact to solved. Watch the median, not the average; one stuck ticket distorts the mean.
- CSAT. Post-ticket satisfaction, usually a one-question survey. Track it per agent and per ticket type.
- QA score. Your own rubric — accuracy, tone, policy compliance, completeness — scored on a sample of tickets each week.
- Average handle time. Minutes per ticket or call.
The warning is about the last one. Handle time is the easiest metric to measure and the most dangerous to optimise alone. Push agents to cut it and they will close tickets early, send macros that do not fit, and stop asking the clarifying question that would have solved the problem in one go; CSAT falls and repeat contacts rise. Use handle time as a diagnostic (why is this agent twice as slow as the others on refunds?), never as a target on its own.
A QA and coaching cadence
A rhythm that works for a small team: sample five to ten tickets per agent per week, score them against the rubric, and hold a 20-minute coaching conversation with each agent weekly for the first three months, then fortnightly. Share the scores; agents improve faster when they can see the number. Once you have a team lead, they run this and you review the trend.
From one agent to a team with a lead
Most companies start with one agent and add a second within a few months, usually to cover the other half of the day or the weekend. At around four to six agents, or as soon as you run two shifts, hire or promote a team lead. A good Filipino team lead handles rostering, QA sampling, first-line coaching and escalations in the team’s own hours, and gives you one person to talk to rather than six. Promote from within where you can; the best leads already know your queue. Beyond ten agents, add specialists — a dedicated tier-2, an e-commerce order desk, a social-media agent — rather than more generalists. The customer support role page describes how these profiles differ.
Security when support staff handle customer data
Support agents see names, addresses, order histories and sometimes payment details, so treat security as part of the hiring design rather than an afterthought.
- Least privilege. Agents get the helpdesk, the order system and whatever else the role genuinely needs. They do not get your bank, your ad accounts or full admin rights in Shopify. Use the roles and permissions built into each tool.
- No card data on screen, ever. Keep full card numbers out of the helpdesk and out of chat. Refunds and payment updates go through your payment provider’s tools, which show agents the last four digits and nothing more.
- Individual logins and MFA. No shared accounts. When an agent leaves, one switch removes their access to everything.
- NDAs and a data-handling policy. Every agent signs one and is trained on it in week one; the provider should countersign.
- Local law. The Philippines’ Data Privacy Act of 2012 governs personal data locally, and a provider should have policies aligned with it. That does not replace your own obligations under the GDPR, US state privacy laws or Australian privacy law, which follow the data wherever the agent sits.
- Environment. Managed devices, a clean-desk rule and an office you can walk into make all of the above enforceable. At home they run on trust. This is a large part of why the office-based vs work-from-home guide leans the way it does for any role that touches customer data.
Mistakes to avoid
- Hiring on rate alone. The cheapest agent costs you customers. The difference in rate between a mediocre agent and a strong one is small; the difference in CSAT is not.
- Skipping the mock ticket. A conversation tells you whether someone is pleasant; a mock ticket tells you whether they can do the job.
- One agent, seven-day coverage. It fails the first time they are sick.
- No macros, no escalation path, no rubric. The agent will invent all three, and you will not like the results.
- Measuring handle time and calling it quality. See above.
- Home-based night shifts for critical queues. The outage always happens at 2am on a Friday.
- Silence. An agent who hears from you only when something goes wrong disengages. A daily check-in message and a weekly call is the minimum, especially in the first three months.
- Skipping the fundamentals. If this is your first offshore hire, read the complete guide to outsourcing to the Philippines first; most support-specific mistakes are general outsourcing mistakes in disguise.
Where BuildNextTeam fits
BuildNextTeam is a dedicated staffing company, not a call centre. We source, screen and shortlist customer support staff to your brief, engage them locally in the Philippines, run payroll and statutory contributions, provide HR and the office, and give you a named account manager. You lead the work: the training, the macros, the KPIs and the daily queue. If what you need is 200 seats on a script for one season, we are not the right fit and will say so.
Our teams are office-based in Bohol, Philippines, which matters more for support than for most roles: a well-run office with backup power, redundant connections and a supervisor on site is what makes a US-hours queue reliable. Clients are welcome to visit — see our offices.
Every hire is full-time and dedicated to you, on one all-inclusive monthly rate per person with no upfront fee. We have been doing this for more than eight years for companies in the US, Australia and the UK. How it works explains the process from brief to start date; if you already know the role and the shift, get a quote and we will come back with a rate for that specific hire.