Role resumes
Customer service resume: name the tools and the numbers you have
Write a customer service resume from the queue you actually sat: tickets per shift, CSAT or quality score you saw, and the tools in the posting (Zendesk, Salesforce, POS). Put those nouns under Skills and again in Experience so Workday and Greenhouse can store them. Do not invent a CSAT.
Written by EnhanceCV Editorial Team·Editorial review: CPRW
Published August 27, 2026·Last updated August 27, 2026
Key takeaways
- · Name the channel and the tool: Zendesk, Salesforce Service Cloud, Shopify inbox, POS, phone ACD — not “people person.”
- · Use volume you held: tickets per shift, calls per hour, chats concurrent, retail transactions per hour.
- · CSAT, QA, FCR, AHT belong on the page only if you can say which dashboard and which period.
- · Workday stores Skills plus Experience text. A sidebar of soft skills will not map. Greenhouse search hits Zendesk, not “excellent communicator.”
- · Flatten to one column, then check the parse and rebuild in the Enhance CV builder if contact or dates vanish.
Start from the queue, not from “people person”
Key takeaway: Hiring managers already know the job is talking to people. They need channel, tool, volume, and what “good” looked like on your floor.
Customer service postings in 2026 still read like a personality contest in the first paragraph and like a systems list in the requirements. Greenhouse search and Workday skills matching run on the requirements: Zendesk, Salesforce, Talkdesk, Intercom, Shopify, Kustomer, Genesys, NetSuite cases, or a named POS. If those words are only implied by “handled customer issues,” you will not surface when a recruiter filters the requisition.
Write the last seat first. Retail floor is not the same as a BPO nest or an in-house SaaS tier-1 queue. Retail: transactions per hour, fitting-room coverage, BOPIS exceptions, the POS name. BPO: client name if you may publish it, campaign, AHT target you were measured on, languages, night shift. In-house: product area, ticket types (billing vs bugs), SLA, who you escalated to. Mixing all three in one summary makes the parser’s skills bucket look unfocused and the human assume you cannot pick a lane.
Match the title only when it is true. “Customer Success” is not a synonym for “cashier” or “call center agent.” If the posting says Customer Support Specialist and your badge said Associate, you can write “Associate (customer support / omnichannel)” — you cannot invent CS. Workday stores the title field; the recruiter still reads employer and dates. Honesty plus shared nouns beats a slogan. For the writing sequence that sits under this, use how to write a resume and tailor a resume to a job.
Nouns to steal from the posting — when you have them
- Tools: Zendesk, Salesforce Service Cloud, HubSpot Service, Gorgias, Freshdesk, Five9, Avaya, Lightspeed, Square.
- Metrics the floor already posted: CSAT, NPS (only if support-owned), QA percent, FCR, AHT, occupancy, abandon rate — with period.
- Channels: phone, chat, email, social, in-store, curbside. Name the mix you actually worked.
- Languages and hours: bilingual queues and overnight coverage are searchable and believable.
Soft skills can stay in one short clause if they are proven by the line above them. “De-escalated billing disputes” is better than “empathetic communicator.” The second phrase is what every template already printed. Line patterns: resume bullet points.
Skills, tools, and what Greenhouse actually searches
Key takeaway: Put systems under a Skills heading parsers already map. Repeat the same nouns inside the job that used them.
Workday’s skills bucket fills from a heading it recognizes: Skills, Competencies, Technical Skills. It does not fill from a left-rail word cloud or from icons of headsets. Greenhouse keyword search is closer to grep: Zendesk in a bullet counts; a headset PNG does not. Taleo is hostile to text boxes. Keep one column. See ATS resume and two-column resume ATS.
Group the skills line the way a support manager scans: platforms, channels, languages, methods (QA rubrics, macros, help-center edits). Do not rate yourself 5/5 in Empathy. Do not list Microsoft Office as your headline skill if the posting is Zendesk + Salesforce. Office can sit at the end if the ad names it. Keyword craft without stuffing: resume keywords and resume skills.
Contact still dies in designed headers. Phone and email in the body. Dates month–year beside each employer so the employment graph in Workday does not look like a gap between seasonal gigs. If you bounced across BPO clients, put the vendor and the client in the same block: “Concentrix — Client: telecom billing (on-site / WFH mix).” Otherwise the parser creates five jobs and a suspicious timeline.
Retail vs BPO vs in-house in the Skills block
- Retail: POS name, omnichannel (BOPIS, ship-from-store), cash office, returns policy, maybe Shopify POS.
- BPO: ACD/dialer, CRM the client mandated, languages, security training (PCI, HIPAA) as text not a badge image.
- In-house SaaS: ticketing plus the product admin you actually touched (billing portal, feature flags — only if true).
Upload selectable text. A screenshot of your Zendesk leaderboard is a picture. Type the weekly ticket range instead. File type notes: resume PDF vs Word. After export, check ATS so the tool names still highlight.
Rewrite weak CS lines: three before-and-after transforms
Key takeaway: Tickets, CSAT, and a named tool beat “provided excellent service.” Steal the pattern. Keep your own numbers.
Three floors we edit constantly: retail returns, BPO phone, in-house chat. If you do not have CSAT, the volume-and-tool version is still a finished bullet.
Before
Provided excellent customer service and helped customers with questions and complaints.
After
Resolved 35–50 Zendesk tickets per shift (email + chat) with a 92% CSAT on the weekly WFM report; escalated only billing defects to Tier 2.
Before
Answered phones in a busy call center and met all team goals.
After
Ran outbound and inbound on Five9 for a utilities billing campaign, 55–65 calls per shift, AHT 4:20 against a 5:00 cap on the client scorecard (Apr–Sep 2025).
Before
Worked the sales floor and handled returns in a fast-paced environment.
After
Processed 18–25 POS transactions per hour on Lightspeed, including BOPIS exceptions; cut same-day return restocks from 40 minutes to 15 with a two-step backroom check.
No CSAT in the system? Use QA percent, FCR, or scope: “weekend lead on a 12-person nest,” “Spanish queue coverage 4 nights a week.” Scope is an achievement. Invented 98% is not. More on honest metrics: resume achievements.
Stop at three to five bullets on the most relevant seat. Older retail holidays can collapse to one line with dates so the graph stays honest. How to list experience covers date formats Taleo can sort.
A 12-step playbook for retail, BPO, and support
Key takeaway: Same sequence. Different nouns. Do not paste a SaaS template onto a shop floor file.
Two hours, job ad, last schedule, any QA email you still have. Type in the Enhance CV builder if you want headings Workday already maps.
- Circle the posting’s tools, channels, languages, and any metric (CSAT, AHT, sales per hour).
- New file. Name, city/region, phone, email, LinkedIn in the body — not in a headset-themed header.
- Headline or first summary line: the title they used, if true, plus one volume or tool.
- Jobs reverse-chronological. Vendor and client in one block for BPO. Store number or banner for retail if it helps this ad.
- Eight messy bullets under the most relevant seat: what you actually closed, not the handbook.
- Delete personality adjectives. Keep channel, tool, volume, escalation, language, shift.
- Rewrite remaining lines verb + object + number or tool. If CSAT appears, add the report name in a clause.
- Skills line from posting nouns you can defend. Group: platforms, channels, languages. No stars.
- Education and certificates as text (CPR, PCI, product certs). No badge images.
- Drop “references on request,” photos (US), and a hobbies line unless it proves a language or a tool.
- Export selectable PDF or .docx. Phone-check that the email is tappable.
- Paste resume + ad into the ATS checker. Fix gaps, upload to Workday or Greenhouse, read autofill.
Step 3 last if you stall. Proof under the job first, then a 3-line summary that sounds like a supervisor repeating you: title, years, channel, one number. Professional summary examples for shape, not for someone else’s 92%.
Two very different targets — luxury retail and enterprise SaaS support — mean two files. LinkedIn can be broader. The Workday upload cannot. The recruiter should not guess which queue you want this week.
Do this, skip that
Key takeaway: Support templates fail when they optimize warmth. Parsers and team leads optimize tools and volume.
Desk filter. If the choice is not in the table: will Workday store it, and will a nest manager believe it at 7 a.m.?
Parser-friendly support proof vs. template warmth
| Topic | Do | Don’t |
|---|---|---|
| Tools | Zendesk, Salesforce, POS, dialer — in Skills and in bullets. | “CRM” with no product name when the ad named Zendesk. |
| Metrics | Tickets, CSAT, AHT, QA — with period and source. | A 99% satisfaction you never saw on a wallboard. |
| Title | True badge, plus a parenthetical if the posting’s language matches. | Customer Success as a rebrand of cashier work. |
| BPO | Vendor + client in one job block. | Five client names as five unrelated employers. |
| Design | One column, selectable text. | Headset watermarks, skill bars, two columns. |
| Soft skills | One clause proved by a de-escalation or language line. | A row of adjectives under a smiling headshot. |
Career change out of service into ops or CS can keep chronology and add a short projects line for macros you built or help-center articles you shipped. Do not hide dates in a functional cloud. See career change resume.
Edge cases: no CSAT, bilingual queues, nights, promotions
Key takeaway: The queue still leads. You only change which proof is legal and which title you show.
No CSAT access. Many retail systems never showed you a personal score. Write transactions, channels, tools, and any time change you caused (returns, BOPIS). That is enough for a Workday first pass.
Bilingual. Put the languages in Skills and in a bullet: “Spanish queue 30% of tickets, no interpreter.” Do not bury language only in a header flag icon Greenhouse cannot read.
Overnight and weekends. Shift is a noun managers search. “Overnight Tier 1, Fri–Sun” belongs next to dates. It also explains a “gap” that was a schedule, not unemployment.
Promoted from cashier to supervisor. Show both titles with dates at the same employer so Workday does not look like a hop. One or two bullets on the junior seat, more on the lead seat if this posting is a lead role.
Night coverage, bilingual queues, and seasonal hours are searchable nouns, not personality color. Put them next to the employer dates so Workday’s graph does not look like unemployment. A recruiter filtering Greenhouse for “Spanish” or “overnight” will not find a flag icon in the header. They will find a bullet that says the mix you actually held.
If you bounced across retail banners or BPO clients, keep one employer block and name the site or campaign in the first line. Five micro-jobs with the same vendor make the parse look unstable even when you never left payroll. Ticket volume belongs under that one block, with the period you can defend from WFM or the POS close.
When the posting is SaaS support and your last seat was a store, do not invent Zendesk. Name Lightspeed, BOPIS, and the returns time change you caused. Apply to the retail requisition with that file, and keep a second file if you truly ran a help desk. Mixing both in one summary is how Greenhouse files you as neither.
What to do today: pick one posting, rewrite three bullets with ticket or POS volume, run the checker, upload and read fields. Enhance CV returns you to builder and checker.
FAQ
What metrics belong on a customer service resume?
Volume you held (tickets, calls, chats, transactions) and any quality number you actually saw: CSAT, QA, FCR, AHT. Name the tool and the period. If you never saw a score, skip it and keep volume plus channel.
Should I list Zendesk if I only used it for six months?
Yes if you can defend it in a screen. Put it under Skills and in the job dates that match. Do not list five ticketing products you clicked once in training.
Is customer service the same as customer success on a resume?
No. Success is usually accounts, renewals, and health scores. Service is tickets and queues. Use the badge you held. A parenthetical is fine when the posting’s language overlaps and the work did.
How do I show BPO client work without breaking Workday dates?
One employer block for the vendor, client named in the title or first bullet, dates for the vendor assignment. Listing each client as a new job creates a false hop graph.
Do I need a resume objective for support jobs?
Almost never if you already worked a queue. A three-line summary with title, channel, and one volume is enough. See objective vs summary.
Can I use a two-column support template?
Not for Workday or Greenhouse uploads. Sidebars eat email and tool names. One column, then a designed file only if a human asked. See two-column resume ATS.
What if I only have retail with no ticketing tool?
Name the POS, omnichannel tasks, volumes per hour, and languages. Those nouns still search. Do not paste a Zendesk line you cannot defend.
How do I check the file before I apply?
Select-all in the PDF, then the Enhance CV ATS checker against the ad. Upload to Workday or Greenhouse and read autofilled employer, dates, and skills. Fix blanks before Submit.
Write the next support draft in a layout parsers already map
Open the Enhance CV builder, keep your true queue numbers, and cut the personality adjectives. Score the file against the posting, then upload to Workday or Greenhouse.