I've written the resume using only what you told me. I left out metrics you didn't give me, and the bracketed placeholders are where you can add real numbers.
[YOUR NAME]
[City, State/Country] | [Email] | [Phone] | [LinkedIn, optional]
PROFESSIONAL SUMMARY
Customer Support Specialist with 3 years of customer-facing support experience resolving customer inquiries by email and live chat. Skilled in Zendesk ticketing, clear and professional written communication, and learning new software quickly. Bilingual in English and Spanish (conversational), with a hospitality management background that supports a service-first approach to every customer interaction.
CORE SKILLS
- Support Tools: Zendesk (ticketing), email support, live chat support
- Communication: Clear written communication, customer-focused problem solving, professional tone
- Languages: English (fluent), Spanish (conversational)
- Strengths: Quick learner of new software, customer service, issue resolution
PROFESSIONAL EXPERIENCE
Customer Support Agent | [Online Shop Name] | 2022 – 2025
- Provided customer-facing support to customers via email and live chat, delivering clear, courteous written responses
- Managed and resolved customer tickets in Zendesk, tracking inquiries from first contact through resolution
- Adapted quickly to the company's support tools and processes while working in a small-team environment
- [Add if true: handled roughly X tickets or chats per day/week]
- [Add if true: customer satisfaction score, response time, or other result]
- [Add if true: used Spanish to assist Spanish-speaking customers]
EDUCATION
[Degree], Hospitality Management
[School Name] | [Graduation Year]
Notes on the tailoring
How you match the requirements
- 2+ years of customer-facing support: Your 2022–2025 role covers about 3 years, so I put "3 years" in the summary.
- Zendesk: It's named in the summary, the skills section and the job bullets.
- Clear written communication: Your email and chat work is the evidence, and the bullets say so directly.
- Learning software quickly: This is the weakest match, because you didn't give me an example. Add one if you have it, such as a tool you picked up or a process you improved.
- Spanish (nice to have): It's listed in both the summary and the skills section. I wrote "conversational" because you said "some Spanish". Change it if that undersells or overstates your level.
What I'd add to make it stronger
- Numbers. Ticket volume, response time and satisfaction scores help most in support roles. Even rough figures are fine if they're accurate.
- A SaaS angle. If you ever helped with software, account, billing or troubleshooting issues, mention it. This role is at a SaaS company and your experience is in e-commerce.
- Any other tools. Examples are a help center or knowledge base, macros, a CRM, or Shopify.
Cover letter opener
"For three years I've helped customers by email and chat in Zendesk, and I'm excited to bring that experience to [Company]'s support team."
Send me your name, the company name, and any numbers or details you want included, and I'll finalize it. I can also make a plain-text version for ATS uploads.
Real run recorded with claude-code / claude-sonnet-5-5. The prompt deliberately contained no numeric achievements, to test whether it would invent any. It did not; it left bracketed placeholders. The model output is unmodified.
What it does
Takes a job description and your background and produces a resume aimed at that role, with ATS-friendly wording.
How it works
- Analyses the job description for must-have requirements, key skills and keywords.
- Maps your real experience to each requirement and notes the gaps.
- Writes a summary, skills, experience and education in a clean format, using strong action verbs and exact terms from the posting.
- Adds strengths and gap analysis, interview talking points and cover-letter openers, and can make versions for other roles.
Good for
Applying for a specific job, changing careers and creating several versions of a resume.
Worth knowing
The skill's own example output invents figures such as percentage improvements. In our trial we deliberately gave it no numbers: it used bracketed placeholders for them and wrote only what we had told it, such as three years of experience from the dates.
Pure instruction file: no scripts. You paste in personal details such as your name and work history, so treat the conversation accordingly. Its own sample output contains invented metrics even though it says never to fabricate; our test did not do this, but always check that every number and claim in the result is true before you send it. It cannot promise interviews. The skill folder has no licence file of its own. The licence basis is the source repository's README, which declares the whole repository Apache-2.0 and notes that individual skills may differ. The package also contains LICENSE (the full Apache-2.0 text) and SOURCE.txt (a source and licence-basis note added by AIBars).