Customer Service Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Please note this is an onsite role Mon-Fri at our Draper, Utah office." Then description of company. Then "The Customer Service Specialist is an essential member..." Then "What You Will Do" list. Then "Who You Are" list. Then "What You Have" list. Then "What NEOGOV Offers" list. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to map content to appropriate headings. We have: - About the role: includes onsite note and company overview. So we can have

About the role

with paragraphs. - Responsibilities: corresponds to "What You Will Do". Use

Responsibilities

with

• items. - Requirements: maybe "What You Have" (education/experience). Could be Requirements. Also "Who You Are" could be Qualifications or Skills. We need to decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: yes. - Responsibilities: yes (What You Will Do). - Requirements: maybe "What You Have" (Bachelor’s Degree or 1+ years’ experience...). That's requirements. - Qualifications: maybe "Who You Are" (attributes). Could be Qualifications. - Skills: maybe also part of "What You Have" includes decision-making, analytical, time management, technically savvy. Could be Skills. But we must not create thin sections; prefer few substantive sections. We could combine Qualifications and Skills into one? But we need to follow headings only if we have real specific content. We could make sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. That covers all. We have Benefits: "What NEOGOV Offers" includes competitive wages, benefits, PTO, 401K matching, parental leave, autonomy, lunches, inclusive environment. So we can have Benefits. We have no explicit Pay or Schedule specifics beyond "Competitive Wages" (pay) and "onsite role Mon-Fri" (schedule). The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Competitive Wages" (pay) and "onsite role Mon-Fri" (schedule). So we could include Pay and Schedule sections. However we must avoid filler like "commensurate with experience". "Competitive Wages" is somewhat vague but it's stated. Should we include? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Competitive Wages (pay) and onsite Mon-Fri (schedule). So we could include them. But we also have Benefits section already. Could we combine Pay into Benefits? Probably better to keep separate as per headings. We need to avoid repeating job title as heading. Not needed. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment. Let's extract content precisely. About the role: The text starts: "About Please note this is an onsite role Mon-Fri at our Draper, Utah office. For over 25 years, NEOGOV has been at the forefront..." So we need to keep that sentence. Probably we should rephrase? No, preserve all substantive information. So we keep exactly as given? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the text verbatim, but we can format into

  . However the phrase "About Please note" seems odd; maybe it's a heading "About" then sentence. We'll keep as is. Thus

  About the role

  Please note this is an onsite role Mon-Fri at our Draper, Utah office. For over 25 years, NEOGOV has been at the forefront of public-sector innovation, building technology that helps government and education organizations work smarter, move faster, and better serve their communities. We are a team of cutting-edge technologists, operators, and problem-solvers with top-tier skills and a shared ambition: to build the most efficient operating model in GovTech. We combine deep public-sector expertise with modern SaaS practices, AI-enabled workflows, and a relentless focus on execution. At our core, we are a people-first company. We empower our customers to support the public servants they employ, the communities they serve, and the talented teams that bring our platform to life. Our solutions support the entire employee journey, from hire to retire. By transforming complex HR and compliance workflows into simple, intuitive experiences, we help public-sector organizations reduce friction, improve efficiency, and focus on what matters most: making a difference. The Customer Service Specialist is an essential member of the Customer Support team, which is our front line serving the people who serve the people! You are the voice of NEOGOV providing world-class product support to all NEOGOV customers via phone calls, virtual meetings, and emails. You also collaborate with and support other departments to create high quality experiences for our customers. If you are passionate about excellence and helping others, you’ll fit right in! This posting is for an existing vacancy.

  But note that some of that belongs to Responsibilities etc. Actually the paragraph includes description of role and some responsibilities. However we have a separate Responsibilities section for "What You Will Do". To avoid duplication, we might split: About the role should include company overview and maybe the role description but not the list of duties. The instruction: preserve all substantive information; we can keep the role description in About the role and then list duties in Responsibilities. That's okay; some overlap but we keep all info. Now Responsibilities: list from "What You Will Do". Each bullet starts with a bold phrase? We'll keep as list items. Let's extract bullet points: - Listen attentively to customers to understand what they are trying to accomplish with our products (Active Listening & Effective Questioning) - Provide guidance, training, and troubleshooting services to resolve issues and/or empower customers to be effective and efficient in using our products - Provide service in written form and/or speak with the customer to help resolve issues, answer questions, and/or provide guidance on how best to use our products for customers contacting us via email or other digital channels, - Provide on-going service and follow-up communication for situations which require more than one contact with a customer - Keep your knowledge up to date about changes to our products so you understand the changes before they are released to our customers - Continue learning and practicing with our products to grow your product knowledge to the advanced or expert level - Further investigate, execute standard operating procedures which may include replicating the issue in a test environment, researching solutions, and/or documenting the scenario for escalating to the next level of support - Create and update cases in our case management software (currently Salesforce) with details about each interaction with a customer, including documenting a synopsis of the situation, the category of situation, and the ultimate resolution - Learn and execute new and existing standard operating procedures to provide effective, efficient, and high-quality service - Engage with your team members and in our team activities – fun & work combined! - Contribute to our positive work environment - Provide constructive feedback to help our team continue being successful - Grow with NEOGOV as we keep growing We need to keep punctuation as is. Now Requirements: "What You Have" includes: - Bachelor’s Degree or 1+ years’ experience in a customer support / training / implementation role – bonus points for experience supporting a Software As A Service (SaaS) product – extra bonus points for HR and/or Public Safety software - Effective decision-making skills - Solid analytical skills - Time management skills - Technically savvy We could treat first as requirement (education/experience) and the rest as skills. But we have separate Skills heading. Let's put Requirements for education/experience, and Skills for the rest. Thus Requirements:

  Requirements

  • Bachelor’s Degree or 1+ years’ experience in a customer support / training / implementation role – bonus points for experience supporting a Software As A Service (SaaS) product – extra bonus points for HR and/or Public Safety software
  Skills:

  Skills

  • Effective decision-making skills
  • Solid analytical skills
  • Time management skills
  • Technically savvy
  Now Benefits: "What NEOGOV Offers" includes: - Competitive Wages - Comprehensive Benefits package (medical, dental, vision, etc.) for full-time employees effective Day 1 - Generous PTO to support work-life balance - 401K Matching - 12-week Paid Parental Leave - Autonomy to grow and find your career path with supportive leadership - Company provided lunches and a kitchen fully stocked with snacks and drinks in the Draper office. - Inclusive and diverse work environment We also have EEO statement which we must remove. Thus Benefits section:

  Benefits

  ...
  Now Pay: we have "Competitive Wages" already in Benefits. But we could also create Pay section with that line. However to avoid duplication, we could keep Pay separate and Benefits exclude that line. But the instruction: "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits may be thin. However we have substantive content for both: Pay (Competitive Wages) and Benefits (the rest). Could combine Pay into Benefits? But we have a Benefits heading already; we could include Competitive Wages as first item in Benefits list. That would satisfy Pay info without separate section. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Competitive Wages, so we could include Pay section. But we could also include it under Benefits; but then we would not have a Pay section, which is okay because we are not required to have Pay section if we include the info elsewhere. The rule only prohibits creating a section if the posting does NOT state it. It does not require us to create a section if it does state it. So we can choose to not create Pay section and put the info in Benefits. That reduces number of sections. Similarly Schedule: posting says "onsite role Mon-Fri". That's schedule info. We could include that in About the role paragraph (already there) or create a Schedule section. Since we already have the note in About the role, we can keep it there. So we don't need separate Schedule section. Thus final sections: About the role, Responsibilities, Requirements, Skills, Benefits. Check if we need Qualifications? We have "Who You Are" which could be Qualifications. We omitted that. We should include that content somewhere. "Who You Are" includes attributes: Engaged team player..., Effective communicator..., Self-starter..., Continuous learner..., Authentic and passionate..., Hard worker... That's qualitative. Could be Qualifications. We should include that as a section. So we need Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Now we need to extract "Who You Are" content: - Engaged team player with a positive and helpful attitude - Effective communicator, verbally, non-verbally, and in writing - Self-starter who takes the initiative to learn, practice, and improve - A continuous learner and an empathetic problem-solver - Authentic and passionate about high-quality service - Hard worker capable of smoothly riding the ebbs and flows of fluctuating volumes of customer requests Make list. Now ensure we haven't missed any substantive info: The line "This posting is for an existing vacancy." we included in About the