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.
Qué hace
Toma una descripción de puesto y tu trayectoria y genera un currículum orientado a ese puesto, con una redacción compatible con ATS.
Cómo funciona
- Analiza la descripción del puesto para identificar los requisitos imprescindibles, las competencias clave y las palabras clave.
- Asocia tu experiencia real con cada requisito e indica las carencias.
- Redacta un resumen, las competencias, la experiencia y la formación en un formato claro, usando verbos de acción potentes y los términos exactos de la oferta.
- Añade puntos fuertes y análisis de brechas, puntos clave para entrevistas y frases de apertura para cartas de presentación, y puede crear versiones para otros puestos.
Ideal para
Solicitar un puesto concreto, cambiar de carrera y crear varias versiones de un currículum.
Conviene saber
La salida de ejemplo de la propia Skill inventa cifras, como mejoras porcentuales. En nuestra prueba, deliberadamente no le dimos ninguna cifra: usó marcadores de posición entre corchetes para ellas y escribió solo lo que le habíamos indicado, como tres años de experiencia a partir de las fechas.
Archivo de solo instrucciones: sin scripts. Pegas datos personales, como tu nombre y tu historial laboral, así que gestiona la conversación con la debida cautela. La salida de ejemplo de la propia Skill contiene métricas inventadas, aunque indica que nunca se deben inventar datos; en nuestra prueba no lo hizo, pero comprueba siempre que cada número y afirmación del resultado sea verdadero antes de enviarlo. No puede prometer entrevistas. La carpeta de la Skill no tiene un archivo de licencia propio. La base de la licencia es el README del repositorio de origen, que declara que todo el repositorio es Apache-2.0 y señala que cada Skill individual puede variar. El paquete también contiene LICENSE (el texto completo de Apache-2.0) y SOURCE.txt (una nota sobre la fuente y la base de la licencia añadida por AIBars).