Supervisor, Contact Center

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

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

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

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

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - A summary/overview paragraph - "Essential Duties And Responsibilities" - a long list of duties - "Supervisory Responsibilities" - a paragraph - "Core Competencies" - a list of competencies with descriptions - "Qualifications/Experience" - a list of qualifications - "Education" - a paragraph - "Computer Skills" - a paragraph - "Language Skills" - a paragraph - "Mathematical Skills" - a paragraph - "Reasoning Ability" - a paragraph - "Certificates, Licenses, Registrations" - a paragraph - "Physical Demands" - a paragraph - "Work Environment" - a paragraph - "Contacts with Individuals/Organizations inside/outside the Garden" - a paragraph - "Supervisor" - a line Also mentions "Must have the ability to work evenings, weekends and holidays" at the top. I need to organize this into appropriate sections. The rules say to use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But only include sections that have real content. Let me map: - Summary/overview -> "About the role" or "Summary" - Essential Duties And Responsibilities -> "Responsibilities" - Supervisory Responsibilities -> could be part of Responsibilities or separate - Core Competencies -> "Skills" or "Competencies" - Qualifications/Experience -> "Qualifications" or "Requirements" - Education, Computer Skills, Language Skills, Mathematical Skills, Reasoning Ability, Certificates/Licenses/Registrations -> these could be grouped under "Qualifications" or "Requirements" - Physical Demands, Work Environment -> could be "Physical Requirements" or "Work Environment" - Contacts -> maybe not needed as separate section - Supervisor -> reporting line, could be in a "Reporting" or "About the role" section The posting doesn't have explicit Pay, Benefits, Schedule sections (though schedule is mentioned in qualifications). The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting mentions "Must have the ability to work evenings, weekends and holidays" and "Must be willing to work nights, weekends, and some holidays in addition to regular business hours." That's schedule information, but not a formal schedule section. I could include a "Schedule" section if there's substantive content. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule requirements. However, it's not a formal schedule description like "Monday-Friday 9-5". It's a requirement. I think it's better to include it in Qualifications or a separate "Schedule" section? The rule says "include a section ONLY when the posting has real, specific content for it". The posting has specific content about schedule requirements. But the example headings include "Schedule". I'll consider adding a "Schedule" section with the schedule requirements. Similarly, Benefits: not mentioned. Pay: not mentioned. So no Pay or Benefits sections. I'll structure as: - About the role (summary, supervisory responsibilities, reporting line) - Responsibilities (essential duties) - Qualifications (qualifications/experience, education, computer skills, language skills, mathematical skills, reasoning ability, certificates/licenses) - Skills (core competencies) - Physical Requirements (physical demands, work environment) - Schedule (schedule requirements) But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine some. Let me think: The core competencies are skills. The qualifications/experience, education, computer skills, etc. are all qualifications. Physical demands and work environment are physical requirements. Schedule is schedule. I'll create: 1. About the role (summary, supervisory responsibilities, reporting) 2. Responsibilities (essential duties) 3. Qualifications (qualifications/experience, education, computer skills, language skills, mathematical skills, reasoning ability, certificates/licenses) 4. Skills (core competencies) 5. Physical Requirements (physical demands, work environment) 6. Schedule (schedule requirements) But the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Requirements" and "Qualifications" are both example headings. I could use "Requirements" for the qualifications section. Or "Qualifications". I'll use "Qualifications" for the qualifications/experience/education/etc. and "Skills" for core competencies. Now, I need to output HTML fragment with

  and

  • for lists,

    for prose. Let me parse the content and convert. First, the summary paragraph: "The Contact Center Supervisor leads the integrated customer service team responsible for providing exemplary service to patrons on the phone and through email with ticket transactions, memberships, donations, event registrations, and visitor information at the Missouri Botanical Garden, Sophia M. Sachs Butterfly House, and Shaw Nature Reserve. The supervisor implements strategies to increase membership conversion, cross selling, and revenue generated by the Contact Center team. The supervisor develops user-friendly, up-to-date procedures and documentation to prepare staff for new promotions, events, and programs across all sites. The Contact Center Supervisor builds relationships with a variety of staff across the Garden’s three locations and reports to the Director of Membership and Development Operations within the Institutional Advancement Division." Also "Must have the ability to work evenings, weekends and holidays." at top. Supervisory Responsibilities: "This position supervises 3 full-time and 4 part-time regular Membership and Contact Center Assistants, the Garden receptionist, and temporary part-time staff." Reporting: "Supervisor Director, Membership and Development Operations" I'll put these in About the role. Essential Duties And Responsibilities: a long list of bullet points (though in the text they are separated by periods, but they are distinct duties). I'll make each a list item. Core Competencies: each competency with description. I'll make each a list item with the competency name and description. Qualifications/Experience: list of qualifications. Education: paragraph. Computer Skills: paragraph. Language Skills: paragraph. Mathematical Skills: paragraph. Reasoning Ability: paragraph. Certificates, Licenses, Registrations: paragraph. Physical Demands: paragraph. Work Environment: paragraph. Contacts: paragraph. Schedule: the two mentions. I'll combine Education, Computer Skills, Language Skills, Mathematical Skills, Reasoning Ability, Certificates/Licenses/Registrations into Qualifications section as sub-lists or separate paragraphs. Since they are distinct categories, I could make them subheadings? But the rule says only use

    for section headings. No subheadings. So I'll include them as paragraphs or list items under Qualifications. Better to make a list of qualifications, each as a list item. But some are paragraphs. I'll convert each category into a list item with the category name and content. For example: - Minimum of two (2) years of experience in non-profit, arts/culture, box office, customer service, phone center, or sales environment required. - Prior supervisory experience required, including scheduling, managing, and motivating a customer-facing team. - Fundraising or membership experience strongly preferred. - Experience working with Tessitura or a similar CRM, fundraising database, or ticketing system strongly preferred, with technology fluency and curiosity a must. - Demonstrated ability to communicate effectively at all levels; must enjoy and feel comfortable interacting with the general public. - Demonstrated ability to work effectively in a fast-paced, high-volume environment, to adapt on short notice, and to manage escalated customer service issues with resolve and sensitivity. - Must be punctual, dependable, self-starter, and possess the ability to effectively multi-task and work under minimal supervision. - Must be willing to work nights, weekends, and some holidays in addition to regular business hours. - Enthusiastically supports the Garden, its mission, fundraising programs, vision, and leadership. - The Garden is committed to the safety and wellbeing of our employees, volunteers and guests. All staff are strongly encouraged to receive all vaccinations as recommended by your healthcare provider prior to hire date. The Garden reserves the right to require future proof of current vaccination status, based on local health department guidelines. - When international travel is necessary for Garden business, staff must be able to obtain required travel clearances, driving permits, and vaccinations for all countries where travel is required. - The requirements and duties listed are representative and not exhaustive of the knowledge, skill, and/or abilities required. - Bachelor’s degree in Business, Communications, Nonprofit Management, or relevant field required. An equivalent combination of skills, education and experience may be considered. - Proficiency with Microsoft Office Word, Excel, PowerPoint, Outlook, and Teams required. Experience with Tessitura or similar constituent database strongly preferred. Experience in a call center or with phone systems a plus. Experience using social media platforms in a professional setting preferred. - Ability to communicate effectively in English (verbal and written). - Proficient basic math skills; requires ability to perform addition, subtraction, multiplication and division; calculate percentages and decimals, etc. - Requires ability to exercise independent judgment and to accurately assess other divisions’ needs and considerations in making decisions related to membership event program support, and effective problem solving skills. - Must possess and maintain a valid driver’s license. Must have the ability to pass a background screening and motor vehicle report (MVR) to meet minimum insurance underwriting criteria. That's a long list. But it's all qualifications. Physical Demands and Work Environment can be separate section "Physical Requirements". Schedule: "Must have the ability to work evenings, weekends and holidays." and "Must be willing to work nights, weekends, and some holidays in addition to regular business hours." I'll put in Schedule section. Now, I need to ensure I don't include boilerplate. The posting includes "The requirements and duties listed are representative and not exhaustive of the knowledge, skill, and/or abilities required." That's boilerplate but it's part of qualifications. I'll keep it as it's in the qualifications section. Also "The Garden is committed to the safety and wellbeing..." is about vaccinations, which is a requirement. Now, write HTML. I'll start with

    About the role

    then

    for summary, supervisory responsibilities, reporting. Then

    Responsibilities

    then
    with each duty as
    • . Then

      Qualifications

      then
      with each qualification as
      • . Then

        Skills

        then
        with each core competency as
        • (including description). Then

          Physical Requirements

          then

          for physical demands and work environment (maybe two paragraphs). Then

          Schedule

          then

          for schedule requirements. But the rule says "