Sr. Care Center Support Specialist

We need to output HTML fragment with sections: About the role? Actually we have company description separate. The job description includes duties, qualifications, pay, schedule, benefits, technical requirements? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. Content: - Company Description: Could be "About the role"? Actually company description is about the company, not role. Could be "About the role" maybe not. But we can include a section "About the Company" maybe not in list. The allowed headings list includes "About the role". We could use that for company description? Might be okay. But we could also not include a heading for company description and just put it in a

  . However we need to preserve all substantive info. The company description is substantive. Could put under

  About the role

  but that seems odd. Perhaps better to not add a heading and just put a

  for company description. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

  for section headings (e.g. ...). Likely they expect those headings only. So we should use those headings where appropriate. We have: - Responsibilities (Primary Job Duties) -> list. - Qualifications -> list. - Pay -> hourly range $21-23/hr, annual bonus 10%, base pay determined by factors. - Benefits -> medical, dental, vision, life, pet insurance, 401K, paid time off, other wellness programs. - Schedule -> Must be available to work any 8 hour shift between 8am-6pm EST, remotely. - Technical Requirements -> internet speed, private quiet workspace, high-speed internet, expense reimbursement. - Skills? Could include familiarity with AthenaNet, Salesforce, etc. Could be under Skills or Qualifications. We have Qualifications already includes those. Could combine. We need to avoid thin sections. Could combine Pay and Benefits into one "Compensation and Benefits"? But headings list includes Pay and Benefits separate. We could keep both if they have content. They do. Schedule: we have content. Technical Requirements: not in allowed headings list but we could treat as "Requirements"? Actually Requirements heading could cover qualifications and technical requirements. But we already have Qualifications. Could make a "Requirements" section for technical and maybe other requirements. However we have Qualifications already covering education, experience, certifications. Technical requirements (internet speed, workspace) could be under Requirements. We must not create sections with filler. All sections we create must have real content. Thus possible sections: - About the role (maybe company description) - but we could skip and just put company description in a

  without heading. However instruction says use

  for section headings (e.g. About the role, ...). It doesn't say we must use those headings, just that if we use headings they should be

  . So we could omit heading for company description and just put a

  . That seems fine. - Responsibilities (

  Responsibilities

  ) with
  • list. - Qualifications (

    Qualifications

    ) with
    • list. - Pay (

      Pay

      ) with

      describing hourly range, bonus, base pay determination. - Benefits (

      Benefits

      ) with
      • list. - Schedule (

        Schedule

        ) with

        . - Requirements (

        Requirements

        ) for technical requirements (internet speed, workspace, expense reimbursement). Could also include "Must provide accessibility to private, quiet work space with high-speed internet to effectively work remotely" which is already in Qualifications but also technical. Might duplicate. We'll keep it under Requirements. We need to ensure we don't repeat info. The Qualifications already includes "Must provide accessibility to private, quiet work space with high-speed internet to effectively work remotely". That's a requirement. So we could keep that in Qualifications and not duplicate in Requirements. Then Requirements could be just about technical specs: internet speed minimums, expense reimbursement. But we could also combine. Better: Keep Qualifications as education, experience, certifications, familiarity with software, and the private workspace requirement. Then Requirements heading for technical specs: internet speed, expense reimbursement. However the instruction says prefer few substantive sections over many thin ones. Having both Qualifications and Requirements may be okay. Alternatively, we could merge technical specs into Qualifications as additional bullet. That would reduce sections. Let's see: Qualifications currently includes: High School Diploma preferred, advance certification a plus; Familiar with healthcare billing and claim resolution preferred; Experience with AthenaNet, Salesforce a plus; 2+ years of full time experience in a call center customer service environment; Familiarity using software such as Salesforce, Word, Excel, Web Browsers and cloud-based web applications; Must provide accessibility to private, quiet work space with high-speed internet to effectively work remotely. We could add bullet about internet speed minimums and expense reimbursement under Qualifications as well. That would keep only Qualifications section. Thus sections: Responsibilities, Qualifications, Pay, Benefits, Schedule. That's five sections. Check if we need About the role? Could omit. Now we need to extract all substantive info and format. Responsibilities list items: - Responding to high volume inquiries via email/phone - Assist with triaging case volumes - Providing resolution guidance/support to care center staff on complex claims/billing inquiries; claim holds, overrides, take backs, corrected claim workflows, coding assistance - Critically analyze a situation and escalate issues to the appropriate internal team; meticulously following up to ensure that the customer is served in a timely fashion - Identify issues that occur on a repeated basis and provide feedback to management - Act as a subject matter expert for all current and updated resources, ensuring to communicate updates to fellow team members and ensuring understanding - Provide support in team chat with questions from team members - Remain flexible to take on other duties as assigned Qualifications list items: - High School Diploma preferred, advance certification a plus - Familiar with healthcare billing and claim resolution preferred - Experience with AthenaNet, Salesforce a plus - 2+ years of full time experience in a call center customer service environment - Familiarity using software such as Salesforce, Word, Excel, Web Browsers and cloud-based web applications - Must provide accessibility to private, quiet work space with high-speed internet to effectively work remotely - Minimum of 5 MBPS download speed and 3 MBPS upload speed (technical requirement) - Employees who regularly work from home offices are eligible for expense reimbursement to offset this cost (maybe could be under Benefits? but it's about remote work expense. Could be under Qualifications as well. But maybe better under Benefits? Actually it's about expense reimbursement for internet cost. Could be under Benefits. But we already have Benefits section for medical etc. Could add this as a bullet under Benefits? It's not typical benefit but still a perk. However instruction says Benefits section only if posting actually states them. It does state expense reimbursement. So we could include it under Benefits. But we already have Benefits list: medical, dental, vision, life, pet insurance, 401K, paid time off, other wellness programs. We could add expense reimbursement as another bullet. That seems okay. Thus Qualifications bullets exclude the internet speed and expense reimbursement; we will put those under Benefits? Actually expense reimbursement is a benefit, but internet speed is a requirement. Let's keep internet speed under Qualifications as a requirement (technical). Expense reimbursement under Benefits. Thus Qualifications bullets: - High School Diploma preferred, advance certification a plus - Familiar with healthcare billing and claim resolution preferred - Experience with AthenaNet, Salesforce a plus - 2+ years of full time experience in a call center customer service environment - Familiarity using software such as Salesforce, Word, Excel, Web Browsers and cloud-based web applications - Must provide accessibility to private, quiet work space with high-speed internet to effectively work remotely - Minimum of 5 MBPS download speed and 3 MBPS upload speed Pay section: hourly range $21-23/hr, exclusive of any bonuses or benefits; eligible for annual bonus targeted at 10%; base pay determined based on relevant factors such as experience, education, geographic location. Benefits section: medical, dental, vision, life, and pet insurance, 401K, paid time off, other wellness programs; expense reimbursement for home office internet costs. Schedule section: Must be available to work any 8 hour shift between the hours of 8am-6pm EST, remotely. Now we need to output HTML fragment with

        headings and

        • for lists,

          for prose. We must not include any boilerplate like EEO, confidentiality, etc. Remove those. Also remove duplicated lines. Ensure we preserve all substantive info. Check if any other info: "The Sr. Care Center Support Billing Specialist supports our growing physician network." That's a description of role; could be included under About the role? But we omitted About the role. Could we include a short paragraph under Responsibilities? Actually it's a general description. Could be placed as a

          before Responsibilities heading? The instruction says use

          for prose. We could include a brief

          summarizing the role before the Responsibilities list. That would preserve that info. Let's add a

          after maybe a heading "About the role"? But we decided not to use About the role heading. Could just put a

          before Responsibilities: "The Sr. Care Center Support Billing Specialist supports our growing physician network." That's substantive. Also "This person will assist customers with all questions around billing/claims resolution, via current email technology platforms and incoming calls." That's also part of duties; we have that covered in first bullet maybe. But we could keep it as part of responsibilities. Also "The role operates within a customer service oriented high-volume call center environment." Could be a

          as well. We need to preserve all substantive info; not invent or summarize away detail. So we should include those statements as prose. Thus we could have:

          The Sr. Care Center Support Billing Specialist supports our growing physician network.

          This person will assist customers with all questions around billing/claims resolution, via current email technology platforms and incoming calls.

          The role operates within a customer service oriented high-volume call center environment.

          Then

          Responsibilities

          with list. But note that some of those sentences are similar to bullet items. However we must not duplicate. The bullet list includes "Responding to high volume inquiries via email/phone". The prose sentences are more general. It's okay to keep