Call Center Agent - IL - Full-Time - Monday, Tuesday, Thursday 11:30 am-8:00 pm, Friday 9:00 am- 4:30 pm, rotating Saturday 9:00 am-1:00 pm, OFF Wednesday and Sunday - Hybrid - In office 3 days a week

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. 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. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Intro about Versiti (company description). Could be "About the role"? Actually "About the role" maybe not present; but we could have "About the role" as a heading if we have description of role. The posting includes "Position Summary Call Center Agent – Aurora, IL In-Office And Remote Days Are Required (not Fully Remote) Stable Hours Bi-Weekly Pay Paid Training Growth Opportunities". That's a summary. - Then "What You’ll Do" list of duties. - Then "What We Offer": includes pay $16.39/hr + shift differentials, predictable schedules, paid training, supportive supervisors, benefits package (medical, dental, vision, PTO, 401K.) - Then "What We’re Looking For": bullet list of skills. - Then "Schedule Full and Part- Time Schedules Set shifts Schedules fall between 8am-8pm shifts Location: Aurora, IL - Position requires In-office" - Then "Total Rewards Package Compensation The target salary for this position is $16.00/hr. The target salary is based on internal averages. Versiti sets salary ranges aligned to local markets in which the job is performed. Compensation decisions take into account internal salary averages and differentiation based on education, experience, skills, and performance. Specific salary and benefits information is shared at the time of the phone screening based on your location and qualifications." - Then "Benefits Versiti provides a comprehensive benefits package based on your job classification. Full-time regular employes are eligible for Medical, Dental, and Vision Plans, Paid Time Off (PTO) and Holidays, Short- and Long-term disability, life insurance, 7% match dollar for dollar 401(k), voluntary programs, discount programs, others." - Then "Responsibilities" list (long list). - Then "Qualifications" with Education, Experience, Knowledge, Skills And Abilities, Tools and Technology. We need to decide sections: maybe "About the role" (position summary), "Responsibilities", "Qualifications", "Benefits", "Pay", "Schedule". Also maybe "Skills" but we can incorporate into Qualifications. We must not create sections with filler. So we need to ensure each heading has substantive content. We need to avoid duplication: there are two pay mentions: $16.39/hr + shift differentials (What We Offer) and target salary $16.00/hr (Compensation). Both are substantive; we can combine into Pay section. Schedule: "Full and Part- Time Schedules Set shifts Schedules fall between 8am-8pm shifts". Also earlier "Stable Hours Bi-Weekly Pay Paid Training Growth Opportunities". So schedule section. Benefits: we have benefits package details in What We Offer and later Benefits section. Combine. Responsibilities: we have "What You’ll Do" bullet list and also a long Responsibilities list later. We should combine? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include both lists? They may overlap but we should keep both as they are distinct. Could combine into one Responsibilities section with all items from both lists, but need to ensure we don't lose any. Safer to include both as separate lists under Responsibilities? But that would be duplicate heading? We could have one Responsibilities section with two

  lists, or we could merge items. The instruction: "Use
  • for any list of duties/requirements/benefits". It doesn't forbid multiple lists under same heading. So we can have one Responsibilities section containing two
    lists: one from "What You’ll Do" and another from the later "Responsibilities". That preserves all. Qualifications: we have Education, Experience, Knowledge, Skills And Abilities, Tools and Technology. Could be one section with subheadings? But we only allowed headings

    for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Qualifications heading and inside we can have

    for prose and maybe

    for lists. The Qualifications section includes Education, Experience, Knowledge, Skills And Abilities, Tools and Technology. We can format as

    with bold? Not allowed to add extra tags? Only allowed tags:

    ,

    • ,

      . We can use

      for prose and maybe include line breaks. For lists we can use

      • . So we can break qualifications into multiple
        lists each preceded by a

        heading? But we cannot add extra headings like "Education". Could we embed headings inside

        ? Not allowed. We could just make a single

        with all qualification items, but that would lose categorization. However the instruction says preserve ALL substantive information; we can still preserve the items even if not categorized. So we can list each qualification as a
        • . That's fine. Similarly Skills: we could have a Skills section but we already have Qualifications covering skills. The instruction says prefer few substantive sections over many thin ones. So we might not need a separate Skills section; we can incorporate skills into Qualifications. Thus sections: About the role (position summary), Responsibilities, Qualifications, Benefits, Pay, Schedule. Check each for substantive content. About the role: we have position summary paragraph: "Call Center Agent – Aurora, IL In-Office And Remote Days Are Required (not Fully Remote) Stable Hours Bi-Weekly Pay Paid Training Growth Opportunities If you’re looking for a stable job with predictable hours and a team that supports you, this could be a great fit. We’re hiring Call Center Agents in Aurora who want to build customer‑service skills, grow their careers, and work in a positive, team‑focused environment. If you want stability, support, and a place to grow, we’d love to talk with you. Apply today — we move quickly." That's substantive. Responsibilities: combine two lists. Qualifications: list all items. Benefits: combine details. Pay: combine $16.39/hr + shift differentials and target salary $16.00/hr plus note about compensation decisions. Schedule: mention full/part-time, set shifts, 8am-8pm, stable hours, bi-weekly pay? Actually bi-weekly pay is pay not schedule. So schedule: Full and Part-Time Schedules, Set shifts, Schedules fall between 8am-8pm shifts. Also mention In-office requirement? That's location not schedule. Could include location in About the role? Already there. We'll keep schedule as described. Now we need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must not include Job ID / requisition numbers as headings; we have "#AJ123 #Hybrid" at end. That's minor metadata; we can fold into a short

          or drop it. Probably drop it as not substantive? It could be considered metadata but we can include as a short

          maybe under About the role? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it. So we can include a

          containing "#AJ123 #Hybrid". Or drop it. Safer to drop as not substantive. Now produce HTML fragment. Structure:

          About the role

          ...

          Responsibilities

          • ... from What You’ll Do
          ...
          • ... from Responsibilities list
          ...
          But having two consecutive
          may be okay. Could wrap each in

          ? Not needed. Better to have one

          with all items combined, but we need to preserve all items; merging is fine as long as we don't lose any. Let's combine all items from both lists into one
          . Ensure we don't duplicate any identical items. Let's extract. First list (What You’ll Do): - Make outbound calls encouraging current blood donors to schedule appointments - Use computer systems to document information - Provide friendly, professional service on every call - Follow clear processes and training to support blood donor needs - Work with a supervisor who’s invested in your success Second list (Responsibilities): - Adheres to work schedule - Meets productivity, quality, and service level goals - Provides compelling messaging to donors to influence blood donation - Provides blood donation information and convert donor into appropriate donation type based on donor eligibility - Answers donor questions, requests and concerns via phone and text - Recruits new donors by asking existing donors for family/friend referral (pledge) - Educates and motivates donors to schedule their next donation appointment - Attends training and implements techniques/tactics taught into workflow - Maintains accurate donor information in profile - Ensures donor requests are carried out (opt out of calling list, don’t contact for a period of time, prefers to only receive text messages, etc.) by making the appropriate request and following up to ensure completion - Participates on team projects, as assigned - Demonstrates Versiti’s core values daily - Executes service recovery techniques in order to address donor concerns/complaints - Provides excellent customer service by always doing what is right for the donor - Advocates Versiti’s mission in the community - Performs other duties as required or assigned which are reasonably within the scope of the duties in this job classification - Understands and performs in accordance with all applicable regulatory and compliance requirements - Complies with all standard operating policies and procedures We should keep both sets; there is some overlap (e.g., "Provides compelling messaging to donors to influence blood donation" similar to "Make outbound calls encouraging current blood donors to schedule appointments"? Not exactly same but related. We'll keep both. Now Qualifications items: Education: - High School Diploma required (typo: "requiredequivalent required" but we interpret as High School Diploma or equivalent required) Experience: - 1-3 years customer service experience, preferably in a contact center environment required Knowledge, Skills And Abilities: - Excellent verbal and written communication skills required - Ability to demonstrate sales techniques and overcome objections required - Good attention to detail and accurate data entry skills required - Results-oriented / collaborates with management to meet individual goals required - Ability to multi-task and proactively communicate progress/obstacles required - Ability to perform in a team-oriented environment required - Proficient computer skills (Microsoft Office) and ability to learn job-specific applications required - Moderate to high level of experience working within a multi-channel contact center (social media, chat, email, text) – helpful in order to advance to an Agent II role required Tools and Technology: - Personal Computer (desk top, lap top, tablet) required - Microsoft Office products required - Must learn contact center-specific programs (HemaTerra) required We'll list each as
          • . Benefits: combine from What We Offer and Benefits section. What We Offer benefits: "Benefits package (medical, dental, vision, PTO, 401K.)" Benefits section: "Vers