Team Up Now – Ethical Outsourcing Australia
Get Started
customer support outsourcingoffshore staffinghiring philippinesjob description

How to Write a Job Description for an Outsourced Customer Support Agent

A step-by-step guide to writing a customer support job description for offshore hiring — key sections, communication requirements, and common mistakes to avoid.

30 April 20264 min readBy Julius Schoenfeld, Co-founder, Team Up Now
HR professional carefully writing a job description for an offshore customer support agent

A generic job description produces a generic hire. In offshore support hiring, that problem compounds: the candidate cannot walk into your office for a coffee chat and pick up cultural cues. The written document is the first real impression of your business.

Getting this right is not about writing more. It is about writing precisely.

Why the JD matters more for offshore roles

For a local hire, the interview process compensates for a vague JD. Body language, office environment, team dynamics — candidates fill in gaps unconsciously. For an offshore hire working remotely from the Philippines, the JD, the role brief, and the interview are all they have to understand whether they are the right fit for your specific business.

A poor JD attracts poorly matched candidates, extends the hiring timeline, and increases the chance of a misfire in the first 90 days.

Section 1: Business context (often omitted, always important)

Start with two to three sentences about your business: what you sell, who buys it, and approximately how large your customer base or transaction volume is.

Example: “We are a Sydney-based online homewares retailer with approximately 3,000 orders per month. Our customers are primarily Australian homeowners aged 25–55 who purchase via our Shopify store and expect fast, friendly service when things go wrong.”

This section takes two minutes to write and dramatically improves the quality of candidate understanding before the first interview.

Section 2: Day-to-day tasks (be specific, not aspirational)

List the actual tasks, not the ideal version of the tasks. Specificity matters:

Less useful: “Handle customer enquiries across multiple channels” More useful: “Respond to 30–50 email tickets per day via Gorgias, including order tracking queries, return requests, and shipping damage claims. Escalate technical product faults to the product team via Slack.”

Include:

  • Approximate ticket volume per day
  • Channel breakdown (email, live chat, phone)
  • Platforms used (name them)
  • Escalation paths (who do they go to when something is beyond their scope?)

Section 3: Tools and platforms

Name every tool they will use, even if it seems obvious. Include your helpdesk platform, e-commerce platform, communication tools (Slack, Teams), and any internal systems.

Candidates self-screen on tool familiarity. If you use a less common tool, note that training is provided.

Section 4: Communication requirements

This is the section most JDs get wrong.

Be explicit about:

  • Written English standard: “Customer-facing written communication without proofreading” is a higher bar than “good English” and attracts candidates who can actually meet it.
  • Video call expectations: Do you expect daily video standups? Weekly? Ad hoc? Filipino professionals vary in video call comfort — be upfront if it matters.
  • Async tools: If you use Loom for briefings or voice notes in Slack, mention it. Candidates who prefer structured written communication should know this is a multimedia async environment.

Section 5: Working hours

Specify in both Philippine time (PHT = UTC+8) and Australian time (AEST or AEDT). A standard AEST business hours role looks like:

“Working hours: 8am–5pm AEST (6am–3pm PHT), Monday to Friday.”

If you need after-hours or extended coverage, be explicit. See our guide on using Philippines time zones for after-hours coverage for how shift structures typically work.

Section 6: What success looks like

Add a “What good looks like at 30/60/90 days” section. This does two things: it helps candidates understand your expectations, and it forces you to articulate them before hiring.

“At 30 days: handling 80% of Tier 1 tickets independently. At 60 days: no supervisor review required on standard ticket types. At 90 days: contributing to process documentation and flagging recurring issues proactively.”

Common mistakes

Too vague on tasks: “Support customers across all touchpoints” describes every support role ever written.

Skills laundry list: Listing 15 software tools as “required experience” eliminates good candidates who could learn any three of them in a week.

Unrealistic English requirements: “Native-level English” is both inaccurate as a description and limiting as a filter. Test for the actual standard you need during the interview, not a label.

No context about the business: Candidates cannot self-select well if they don’t know what they’re supporting.

Once the JD is right, the onboarding plan is where the hire succeeds or fails. Read our 30-day onboarding plan for offshore support agents for what comes after placement.

Book a strategy call → | View customer support outsourcing →


Team Up Now places dedicated Filipino customer support professionals with Australian businesses. We guide clients through role scoping, JD development, and structured onboarding. How we work →

Ready to scale your operations?

Talk to us about building a dedicated offshore team that fits your business. No obligation, no pressure.