Customer Service Representative

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. No job title heading. No Job ID. Remove boilerplate (EEO, equal opportunity, etc). Also remove application instructions (none present). Keep all substantive info. We need to parse the posting. Sections present: - About QuikStor (company description) maybe fits "About the role"? Actually "About QuikStor" is company overview. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include role overview and maybe company description? The role overview is present: "Role Overview ...". Also "About QuikStor" is company description. Could be part of About the role? Might be okay. - Responsibilities: there is "Key Responsibilities" with subheadings: Client Service, Triage and Handoff, Product Knowledge and Documentation, Schedule and Coverage, How Success Is Measured. Actually "How Success Is Measured" could be separate but maybe part of Responsibilities? The instruction: we can include sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to put where. We have "Required Qualifications" and "Preferred Qualifications". Those could go under Requirements (required) and Qualifications (preferred) or Skills? The instruction list includes Requirements, Qualifications, Skills. We can map: - Requirements: Required Qualifications (2+ years experience, ticketing system, communication, queue management, learning software). - Qualifications: Preferred Qualifications (software product support, self-storage experience, Intercom experience, writing help center content). - Skills: maybe we could extract skills from responsibilities? But we could also leave Skills section omitted if no explicit skills list. The instruction: prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they said we can use those headings. We'll include both if they have content. - Benefits: clearly listed. - Pay: not mentioned. So omit Pay section. - Schedule: mention "Work Pacific Time business hours on-site at HQ in El Segundo". Also "Participate in coverage planning for holidays and peak periods". That's schedule info. So we can include Schedule section. - About the role: include Role Overview and maybe About QuikStor. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we should list each duty as
• . For requirements list each qualification as
• . For benefits list each benefit as
• . For schedule maybe just prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them. Let's extract content. About QuikStor: "QuikStor is the leading SaaS facility management platform for the self-storage industry, delivering a purpose-built, scalable system that serves as the foundation for intelligent automation and modern facility operations. We are in rapid growth mode, backed by significant capital from self-storage industry veterans who share our vision to build the most advanced and scalable operating system for storage operators worldwide." Role Overview: "The Customer Service Representative is the first point of contact for QuikStor clients. Storage operators run their facilities on QuikStor, so when they reach out, a fast, friendly, and clear response matters. The Representative owns each conversation from the first reply, resolves everyday questions and common issues directly, and keeps the client informed until the issue is closed. Support runs in Intercom across chat, email, and phone, and Intercom routes each ticket to the right person. The Representative answers how-to and account questions, walks facility staff through common workflows, and resolves routine issues on the spot. The harder technical problems belong to the Technical Support team; the Representative recognizes them early, gathers the facts, and hands them off so the client never has to repeat themselves. This role keeps the queue moving and the client experience warm and responsive. This position is based on-site at HQ in El Segundo, California, working Pacific Time business hours. Success is measured by response times, how many conversations are resolved at first contact, client satisfaction, and the quality of handoffs to Technical Support." Key Responsibilities broken down: Client Service: - Respond to inbound client conversations in Intercom promptly and warmly, within the team response targets - Resolve everyday questions directly, including how-to questions, account and login help, navigating the platform, and common workflows such as move-ins, payments, and reports - Walk facility staff through common tasks step by step, in plain language, over chat, email, or phone - Keep clients updated at every step until the issue is resolved, including when another team is working on it - Recognize urgency and immediately flag anything that affects a facility's ability to operate Triage and Handoff: - Gather the facts on every issue: who is affected, which facility, what happened, what the client expected, and screenshots or examples - Identify issues that need Technical Support and hand them off with a complete, well-documented ticket so the client is never asked to repeat themselves - Route hardware and legacy product cases to the Hardware and Legacy support team - Stay the client's point of contact on handed-off cases, follow up on progress, and close the loop when the issue is resolved - Log every client feature request in Intercom so Product can triage it Product Knowledge and Documentation: - Learn the QuikStor platform through onboarding and the recurring feature training sessions, and stay current on each release - Use help center articles and macros to give consistent answers, and flag gaps and outdated content - Turn recurring questions into suggestions for new help center articles and macros Schedule and Coverage: - Work Pacific Time business hours on-site at HQ in El Segundo - Participate in coverage planning for holidays and peak periods How Success Is Measured: - First response time against the team targets - Share of conversations resolved at first contact, without escalation - Client satisfaction scores on closed conversations - Handoff quality, measured by how often Technical Support can act on a handed-off case without going back to the client - Follow-through, with no client left waiting on an update - Help center and macro contributions Required Qualifications: - 2 or more years in a customer service role with direct customer contact by chat, email, and phone - Hands-on experience with a ticketing or help desk system such as Intercom, Zendesk, Freshdesk, HubSpot Service Hub, or ServiceNow - Clear, friendly, and professional written communication and a calm, patient phone presence - Ability to manage a busy queue, prioritize, and follow through on every open conversation - Comfort learning new software quickly and explaining it to others in plain language Preferred Qualifications: - Experience supporting a software product, or experience in a technical support or help desk environment - Self-storage operations experience, or experience in property management or another operationally critical business - Intercom experience - Experience writing help center content or customer-facing instructions Benefits: - Medical, Dental, Vision, and Life Insurance - 401k Retirement Plan - Vacation and Sick Time - 20 Days of Remote Work - Annual Bonus - Employee Assistance Program - Education Assistance Program - Employee Discount Store - Equity Opportunities - Discounted Storage We need to output HTML fragment only, no markdown fences. We'll create sections:

  About the role

  maybe include About QuikStor and Role Overview as

  paragraphs. Then

  Responsibilities

  with
  • for each bullet across subcategories? Could group but still list. Then

    Requirements

    with Required Qualifications list. Then

    Qualifications

    with Preferred Qualifications list. Then

    Benefits

    with list. Then

    Schedule

    with schedule info (maybe as

    or

    ). Since schedule items are two bullets, we can list. We should not include Pay section. We must not repeat job title as heading. We must not include EEO boilerplate etc. Remove that. We need to preserve all substantive information: ensure we didn't miss any. Check if any other info: "Reports To: Technical Support Manager" maybe we could include under About the role? It's metadata but not job ID. Could be included as a short

    maybe under About the role? The instruction: fold minor metadata into a short

    or drop it. So we could include "Reports To: Technical Support Manager" and "Location: El Segundo, California, USA (HQ)" and "Role Type: Full-Time, On-Site, Hourly, Non-Exempt" as a short paragraph. We should include location maybe in About the role? Already role overview mentions based on-site at HQ in El Segundo, California. So location is redundant but okay. We'll include a short

    with those metadata. Now produce HTML. Structure:

    Reports To: Technical Support Manager | Location: El Segundo, California, USA (HQ) | Role Type: Full-Time, On-Site, Hourly, Non-Exempt

    About the role

    QuikStor is the leading SaaS facility management platform for the self-storage industry, delivering a purpose-built, scalable system that serves as the foundation for intelligent automation and modern facility operations. We are in rapid growth mode, backed by significant capital from self-storage industry veterans who share our vision to build the most advanced and scalable operating system for storage operators worldwide.

    The Customer Service Representative is the first point of contact for QuikStor clients. Storage operators run their facilities on QuikStor, so when they reach out, a fast, friendly, and clear response matters. The Representative owns each conversation from the first reply, resolves everyday questions and common issues directly, and keeps the client informed until the issue is closed. Support runs in Intercom across chat, email, and phone, and Intercom routes each ticket to the right person. The Representative answers how-to and account questions, walks facility staff through common workflows, and resolves routine issues on the spot. The harder technical problems belong to the Technical Support team; the Representative recognizes them early, gathers the facts, and hands them off so the client never has to repeat themselves. This role keeps the queue moving and the client experience warm and responsive. This position is based on-site at HQ in El Segundo, California, working Pacific Time business hours. Success is measured by response times, how many conversations are resolved at first contact, client satisfaction, and the quality of handoffs to Technical Support.

    Responsibilities

    • Respond to inbound client conversations in Intercom promptly and warmly, within the team response targets
    • Resolve everyday questions directly, including how-to questions, account and login help, navigating the platform, and common workflows such as move-ins, payments, and reports
    • Walk facility staff through common tasks step by step, in plain language, over chat, email, or phone
    • Keep clients updated at every step until the issue is resolved, including when another team is working on it
    • Recognize urgency and immediately flag anything that affects a facility's ability to operate
    • Gather the facts on every issue: who is affected, which facility, what happened, what the client expected, and screenshots or examples
    • Identify issues that need Technical Support and hand them off with a complete, well-documented ticket so the client is never asked to repeat themselves
    • Route hardware and legacy product cases to the Hardware and Legacy support team
    • Stay the client's point of contact on handed-off cases, follow up on progress, and close the loop when the issue is resolved
    • Log every client feature