Payments Support Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Quilt Software" then "Payment Support Specialist Role". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have content: About Quilt Software (company description) - could be "About the role"? Actually "About Quilt Software" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have "Payment Support Specialist Role" description: includes responsibilities list. Also "Requirements Qualifications:" includes education, experience, technical skills, etc. Also "Benefits What We Offer:" includes benefits list. Also "Base Salary Range: $45000-50000" => Pay. Also location info maybe not needed. Also schedule not mentioned, so omit Schedule. We need to avoid boilerplate: remove cookie/navigation/legal/EEO etc. The "Notice - Employment Scams" etc is boilerplate, remove. Also "Applicants must be authorized to work..." maybe keep? It's not boilerplate? It's a requirement but could be considered minor metadata; but we can fold into a short p or drop. Probably drop as not essential? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." This is about minor metadata like location, work auth. Could be placed in a short p under maybe "About the role"? But we can drop. We need to preserve all substantive information. So we need to keep company description, responsibilities list, requirements/qualifications list, benefits list, pay range. We must not invent or summarize away detail. So we need to keep each bullet. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need headings

  for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have content for About the role? Could be the company description and role overview. We'll put that under

  About the role

  with a

  containing the description. Responsibilities: we have list under "Key Responsibilities:" with bullet points. We'll put under

  Responsibilities

  with
  . Requirements: we have "Requirements Qualifications:" includes education, experience, technical skills, etc. Could split into Requirements and Qualifications? The instruction gives separate headings for Requirements and Qualifications. We could put education/experience under Requirements, and technical skills etc under Qualifications? But we need to follow content. The posting says "Requirements Qualifications:" then bullet list: Education: BA or BS degree (not required) Experience: 1-2 years ... Technical Skills: ... Task Management: ... Proactivity: ... Communication Skills: ... Organizational Skills: ... Attitude: ... Customer Focus: ... Team Player: ... We could treat all as Requirements (or Qualifications). Since we have both headings available, we could split: Requirements: Education, Experience. Qualifications: Technical Skills, Task Management, Proactivity, Communication Skills, Organizational Skills, Attitude, Customer Focus, Team Player. That seems reasonable. Skills: maybe we could also have a Skills section for technical skills? But we already used Qualifications for technical skills. Could also have Skills heading for technical skills. But we need to avoid thin sections. Perhaps we combine technical skills under Qualifications and not create separate Skills. Benefits: we have list under "Benefits What We Offer:" with bullet points. We'll put under

  Benefits

  with
  . Pay: we have Base Salary Range: $45000-50000. We'll put under

  Pay

  with

  . Schedule: not present, omit. We must not include headings with filler. So we will not include Schedule. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine company description and role overview. Company description: "About Quilt Software Ever wondered how your favorite local shops compete with the big guys? That's where we come in. We're Quilt Software, providing Main Street's unsung heroes - from quirky cheese shops to family-run jewelry stores - with the tools they need to compete. Last year, we helped 14,000+ shops make over $2 billion in sales with our family of industry-specific software solutions. If you get a kick out of supporting local businesses, love great software, and want to be part of a company that's powering Main Street, we'd love to chat. Come join us in our quest to keep local retail not just alive, but thriving!" Role overview: "Quilt is looking for an experienced Payment Support Specialist to join our growing CX team! In this role, you will serve on a team of support specialists and act as an internal advocate for our customers. The Payment Support Specialist is vital in helping our new and existing customers troubleshoot and resolve issues around processing and payments." We can combine into a paragraph. Now Responsibilities list: items: - Customer Support: Respond to customer inquiries regarding payment issues through various channels (phone, email, chat). - Issue Resolution: Investigate and resolve payment discrepancies, failed transactions, and other payment-related issues. - Transaction Monitoring: Monitor payment processing systems to ensure transactions are completed successfully. - Documentation: Maintain accurate records of customer interactions, transactions, and issues resolved. - Payment Process Management: Handle inquiries and provide support for various payment processes, including Electronic Benefits Transfer (EBT) transactions, PCI compliance, rate adjustments, and batch processing inquiries. - SLA Compliance: Ensure adherence to Service Level Agreements (SLAs) to meet customer expectations and business requirements. - Inbound Phone Queue Management: Manage the inbound phone queue to ensure timely and effective response to customer calls. - Hardware Support: Provide support for payment processing hardware, including troubleshooting and resolving technical issues. - Bank Changes: Handle inquiries and processes related to bank account changes for payment processing. - Partner Collaboration: Work with payment partners to elevate or escalate ongoing issues and ensure timely resolution. Now Requirements (Education, Experience): - Education: BA or BS degree (not required) - Experience: 1-2 years of work experience in customer service, software implementation, or customer onboarding. Now Qualifications (Technical Skills, Task Management, Proactivity, Communication Skills, Organizational Skills, Attitude, Customer Focus, Team Player): - Technical Skills: Experience with Google Suite, outlook and Salesforce preferred but not required. - Task Management: Ability to manage multiple tasks. - Proactivity: Proactive and innovative approach to work. - Communication Skills: Superb written and verbal communication skills with an understanding of situational best practices. - Organizational Skills: Unmatched organizational skills. - Attitude: Positive attitude and empathetic demeanor. - Customer Focus: A strong commitment to providing excellent customer service. - Team Player: Ability to work collaboratively with cross-functional teams. Now Benefits list: - Clear performance standards and expectations - Opportunity to influence your career path within the organization - Comprehensive benefits package including medical, dental, and vision coverage. - 401 (k) Opportunity with Company Match - Up to 3 weeks of paid time off - Paid Parental Leave - Opportunities for career growth and advancement within a rapidly growing company. - Fun and collaborative work environment with a focus on teamwork and innovation. Note: The original had "Paid Parental LeaveOpportunities" missing space; we need to keep as is? It says "Paid Parental LeaveOpportunities for career growth". Actually original: "Paid Parental LeaveOpportunities for career growth and advancement within a rapidly growing company." That seems a formatting error; we should preserve the text as is? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep exactly as given, but we can fix obvious missing space? That would be altering. Better to keep as is: "Paid Parental LeaveOpportunities for career growth and advancement within a rapidly growing company." That's weird but we must preserve. However we could split into two bullets? The original list: "Clear performance standards and expectations Opportunity to influence your career path within the organization Comprehensive benefits package including medical, dental, and vision coverage. 401 (k) Opportunity with Company Match Up to 3 weeks of paid time off Paid Parental LeaveOpportunities for career growth and advancement within a rapidly growing company. Fun and collaborative work environment with a focus on teamwork and innovation." It seems they omitted punctuation. We should preserve the exact strings? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should not add punctuation that wasn't there. However readability may suffer but we must follow. We'll keep each bullet as a separate line but we need to decide where to split. The original seems to have missing periods between items. We could treat each sentence as separate bullet, but we need to infer where sentences end. That's adding interpretation. Might be okay to add periods? That's inventing detail. Safer to keep as one paragraph? But we need to use

  • for any list of benefits. So we need to split into items. The original list items are separated by capital letters at start of each new item (except after "Paid Parental LeaveOpportunities"). We can split based on capital letters after a period? There are no periods. This is tricky. Maybe we can keep the benefits as a single

    prose instead of list, because the list is not clearly delimited. The instruction: Use

    • for any list of duties/requirements/benefits. If the posting has a list, we should use list. The posting clearly intends a list but formatting is off. We could still create
    • for each item we can discern: "Clear performance standards and expectations", "Opportunity to influence your career path within the organization", "Comprehensive benefits package including medical, dental, and vision coverage.", "401 (k) Opportunity with Company Match", "Up to 3 weeks of paid time off", "Paid Parental LeaveOpportunities for career growth and advancement within a rapidly growing company.", "Fun and collaborative work environment with a focus on teamwork and innovation." We added periods where missing? Actually we added a period after coverage, after Match, after off, after company. That's adding punctuation not present. Might be considered inventing detail. Better to not add punctuation; keep as is without extra punctuation. So each
    • would contain the exact phrase as appears in the source, but we need to decide where each item ends. Since there is no punctuation, we could just treat the whole block as one
    • but that would lose list semantics. Given the ambiguity, maybe we can keep benefits as a

      prose, preserving the exact text as a paragraph. The instruction says use

      • for any list of duties/requirements/benefits. If we are uncertain about list boundaries, maybe safer to use

        to avoid misrepresenting. However we risk not following instruction. But we can argue that the posting does not provide a clear list due to missing punctuation, so it's not a list; it's a paragraph. I'd choose to output as

        preserving the exact benefits text. Let's extract benefits text exactly as appears after "Benefits What We Offer: ": "Clear performance standards and expectations Opportunity to influence your career path within the organization Comprehensive benefits package including medical, dental, and vision coverage. 401 (k) Opportunity with Company Match Up to 3 weeks of paid time off Paid Parental LeaveOpportunities for career growth and advancement within a rapidly growing company. Fun and collaborative work environment with a focus on teamwork and