Customer Service Representatives Job Description Template (Offshore Ready)

A customer service representatives job description is the first filter in your hiring process. It either attracts candidates who can do the actual job, or it pulls in everyone who has ever answered a phone. The difference between those two outcomes usually comes down to specificity. How clearly did you describe the channel mix? Did you name the CRM? Did you state the English proficiency standard or just write “excellent communication skills”? For offshore CSR hiring in particular, the words you use in the JD signal to candidates whether you understand offshore work environments, and signal to staffing agencies exactly what profile to source for.

The template below is built for offshore CSR roles with India and Philippines candidates in mind, but it adapts to any channel type with minor edits. Read the customization sections below the template before using it for a voice-specific or email-only role.

Why Your JD Is the First Screening Tool

Hiring managers routinely underinvest in the job description because it feels like a formality. The real brief happens in the interview, right? Not when you’re hiring offshore at volume. At Kore BPO, the JD is the document we use to align sourcing parameters. If the JD says “strong communicator,” that tells us nothing useful. If it says “CEFR B2 English, Zendesk fluency, 80+ tickets per day, US EST hours overlap,” we can source and pre-screen against that before the first candidate reaches you.

Three things a strong offshore CSR JD accomplishes:

• Filters by channel literacy. Candidates who have only done phone support but apply to a live chat role need to be identified before screening, not during it.
• Sets shift expectations up front. Offshore roles almost always require US or UK hours overlap. If that isn’t in the JD, you’ll spend time on candidates whose availability doesn’t match.
• Signals process maturity. Candidates in Manila and Bangalore who have BPO experience can read a JD and know whether this company has hired offshore before. A well-written JD attracts more experienced applicants.

Customer Service Representatives Job Description Template (Full Example)

Copy this template directly. Brackets indicate fields you must replace with your specifics. Delete or add bullet points as the actual role requires. See the customization sections below for channel-specific adjustments.

Customizing the Template: Voice and Phone Support Roles

Voice roles have higher language requirements than any other channel. When adapting this template for a phone-heavy position, make these four changes:

• Upgrade the English proficiency requirement to CEFR C1. B2 is a practical minimum, but if your customers are US-based and easily frustrated, C1 sets a more defensible bar. For context, the EF English Proficiency Index ranks the Philippines 28th globally and India 52nd, but top BPO hubs in both countries (Metro Manila, Cebu, Hyderabad, Pune) produce candidates who comfortably clear CEFR B2 to C1.
• Add a live mock call requirement to the JD. Explicitly stating “shortlisted candidates will complete a 5-minute mock call as part of screening” filters out candidates who are strong writers but weak phone communicators before you spend time on them.
• Specify de-escalation experience. Add “demonstrated experience handling irate or escalation-risk callers” to required qualifications. This is not standard on generic CSR JDs but it changes who applies.
• Be explicit about noise environment. “Candidates must have a quiet, dedicated workspace with no background noise audible during calls” sounds obvious but is often omitted. It prevents a common early-tenure failure point.

Customizing the Template: Email and Ticket Queue Roles

Email and ticket-only roles open the candidate pool significantly. The language and screening bar shift, and a few sections of the template need adjustment.

• Lower the English standard to B1 CEFR but add a written test. Email mistakes are visible in every ticket and can damage brand voice. Require a short writing sample during screening: ask candidates to respond to a sample customer complaint in 3 to 5 sentences. Assess tone, clarity, and grammar without a Versant call.
• Increase the ticket volume expectation. Email CSRs at a well-run BPO handle 80 to 120 tickets per day. If your current team is at 40, your JD should state a ramp target of 70 by Day 45. Setting this expectation in the JD filters out candidates from slower-paced environments.
• Add categorization and tagging accuracy. Misrouted tickets waste time across the chain. “Accurate ticket categorization and tagging per team protocol” should be a listed responsibility.
• Remove the noise/workspace requirement from the required section. It can stay in preferred, but it’s a lower bar for email roles where no one is listening to background audio in real time.

Skills and Qualifications Block: What Each Line Actually Signals

The required qualifications block is where most JDs get generic. Here’s what each standard line is actually filtering for, and how to make it more effective.

“2+ years of customer service experience” is the minimum bar but it’s almost meaningless without context. Better: “2+ years in a BPO, contact center, or dedicated offshore support role handling [volume].” That tells a candidate and a recruiter whether the experience is relevant.

“Excellent communication skills” is the most common phrase in CSR JDs and the least useful. It conveys nothing to a recruiter or a candidate in Manila or Hyderabad who has seen this phrase 200 times. Replace it with a specific: “CEFR B2 English (voice) or strong written English with a typing speed of 45 WPM or higher (email).”

“CRM experience” needs to name the platform. “Experience with Zendesk” filters candidates against a real skill. “CRM experience” could mean they once updated a spreadsheet. If you’re open to adjacent platforms, write “Zendesk or similar (Freshdesk, Gorgias, Salesforce Service Cloud accepted).”

“Team player” and equivalents should be removed. They occupy space that could be used for a real requirement. The offshore CSR role involves regular async communication with a US-based team lead. “Comfortable with async communication via Slack and email; attends scheduled syncs consistently” is a real requirement that filters for the actual skill.

Compensation Language for Offshore Roles

Compensation language in offshore JDs is genuinely tricky. Publishing a specific number in PHP or INR on a public job listing can work against you in negotiations, particularly when you’re hiring through a staffing partner who absorbs employer costs. The template above uses a deliberate placeholder for this reason.

What to include and what to leave vague:

• State the engagement model, not the number. “This is a full-time dedicated role managed through Kore BPO’s staffing model” tells candidates what they need to know about how they’ll be employed.
• Reference a benchmark source rather than quoting one. Linking to a salary guide like our CSR salary guide signals transparency without locking in a specific number that may be above or below your target range.
• Do mention benefits structure explicitly. “Includes HMO health coverage, paid Philippine / Indian national holidays, and 13th month pay (as applicable under local law)” is concrete and reassures candidates the role is structured legitimately.

For specific 2026 rate benchmarks by experience level, channel type, and country, the CSR salary guide has current data.

JD Mistakes That Attract the Wrong Candidates

These patterns show up consistently in offshore CSR JDs that generate high application volume but low-quality candidates.

Listing every possible channel as required. “Voice, email, chat, social media” in the required section signals to experienced candidates that this is an undefined role. Pick the primary channel. List secondary channels as preferred.

Writing for a US domestic hire. Phrases like “must be authorized to work in the United States” or “local travel required” directly in an offshore JD confuse candidates and signal that the job was repurposed from a domestic listing. Write the JD for the actual hire from the start.

Omitting the escalation path. Offshore CSRs need to know where they go when they can’t resolve an issue. “Escalate complex issues as appropriate” is vague. “Escalate unresolved billing disputes to the US-based accounts team within 4 hours via the Zendesk escalation queue” is specific and tells the candidate this is a real, supported process.

Not specifying async communication tools. Most offshore support roles involve Slack or Teams for coordination with a US-based manager. If this isn’t in the JD, candidates assume phone-based management, which may not match reality. Name the tools.

Skipping performance benchmarks entirely. A JD with no CSAT, AHT, or FCR benchmarks tells experienced BPO candidates that this company either doesn’t track performance or hasn’t decided what it expects. Both readings reduce quality applicants. Even rough targets (“CSAT target of 4.0 or higher”) signal that you run a real operation.

From JD to Hire: What Comes Next

A complete JD hands off cleanly to the interview and screening process. The CSR interview questions guide covers the full question bank organized by skill category: English proficiency, CRM fluency, de-escalation scenarios, and situational judgment. Each section maps directly to the requirements in the JD template above.

For the full hiring workflow including sourcing model decisions, scoring criteria, and onboarding timelines, see the how-to-hire guide. It picks up where the JD leaves off and takes you through sourcing, the screening call structure, the mock call format, and the 30-day onboarding frame.

If you’re ready to put the JD to work, our customer service outsourcing page covers the service model options including managed support teams versus dedicated offshore staffing.

Frequently Asked Questions