Inbound Call Admin

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. The posting includes: About M&D (company description) maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections like About the role (maybe summarizing position summary), Responsibilities (essential duties), Requirements (minimum qualifications), Qualifications (maybe key competencies?), Skills (maybe knowledge?), Benefits (none), Pay (none), Schedule (none). We should only include sections that have real specific content. The posting does not mention Benefits, Pay, Schedule specifics. So we should omit those sections. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the company description? It might be considered "About the role"? Actually "About the role" could be position summary. The company description "About M&D" maybe not required as a heading but could be included as prose under About the role? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings only if content exists. For company overview, we could put under "About the role" as a paragraph describing the role and maybe include company info? But "About the role" likely refers to role description, not company. However we can include company description as part of role summary? Might be okay. Better: Create sections: - About the role: include Position Summary paragraph. - Responsibilities: list essential duties as

• . - Requirements: include Minimum Qualifications (Knowledge, Skills, and Abilities) as
  • . - Qualifications: maybe include Key Competencies and Standards as
    • . - Skills: maybe include General Standards? Or we could combine. But we must not create thin sections with filler. Ensure each section has substantive content. Let's extract: Position Summary: "as an Inbound Call Administrator, you'll play a key role in supporting our company's success by following proven systems and delivering exceptional customer service. In this fast-paced role, you’ll handle inbound calls with professionalism, follow procedures to ensure smooth operations, and have the opportunity to grow within our sales department. If you're detail-oriented, eager to learn, and thrive in a dynamic environment, we’d love to hear from you!" That's substantive. Essential Duties And Responsibilities list: - Create Netsuite Prospects for new inbound call customers - Begin creating Estimates for the sales team to process - Answer phones - Check email - Ensure Customer Records are accurate - Assist with customer questions - Provide excellent customer service - Willingness to learn and grow within the company - Meet or exceed key performance indicators - Work the 5p - 6p shifts in rotation with other upper level sales staff - Transfer calls to a Tech or the parts department based on customer needs - Follow the HHP system and report any problems to management immediately We need to keep each as list items. Requirements: Minimum Qualifications (Knowledge, Skills, and Abilities): - Knowledge of Microsoft Office programs - Knowledge of typing, grammar, and basic written/verbal communication skills - Knowledge of basic customer service principles Key Competencies and Standards list: - Attention to detail and accuracy - Organizational skills - Information management - Problem analysis and problem solving skills - Teamwork - Adaptability - Persuasiveness - Competitive - Stress tolerance - Goal driven - Eager to learn General Standards list: - Perform all work to company policies, procedures and system standards to meet the company's strategic objective. - Follow dress code at all times per company policy - Be proficient in Job Tasks as well as Engine Training. - Maintain a positive and motivating attitude per company policy. - Manage attendance per company policy. Physical Demands and Work Environment: - Prolonged periods of sitting - Office environment. - Perform work at a workstation by Computer and Telephone. - Cubicle environment with exposure to noise throughout the shift. - Typing and entering data - Inbound and Outbound Calling - Ability to lift up to 15 pounds Also there is EEO statement etc which we should remove. We need to decide which sections to map to headings. We have: - About the role: position summary. - Responsibilities: essential duties. - Requirements: Minimum Qualifications. - Qualifications: Key Competencies and Standards (maybe also General Standards? but those are more like standards). Could put General Standards under Qualifications as well, but might be too much. - Skills: maybe we could put Knowledge of Microsoft Office etc under Skills? But those are already under Requirements. Could combine. Better to follow the instruction: Use headings as given; we can decide which content fits. Let's map: About the role: position summary paragraph. Responsibilities: essential duties list. Requirements: Minimum Qualifications list. Qualifications: Key Competencies and Standards list. Skills: General Standards list? Or maybe Skills: Knowledge of Microsoft Office etc? But that's already in Requirements. Could put Skills: Knowledge of Microsoft Office programs; typing, grammar; basic customer service principles. But that duplicates. We could omit Skills section if no distinct content beyond what's already covered. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one? But we need to follow headings only if real content. We could have Requirements include both minimum qualifications and key competencies. But then we would not have Qualifications heading. That's okay. But we need to preserve all substantive information; we can include them under Requirements as sublists? However we must use
      • for any list of duties/requirements/benefits. So we can have multiple
        under a section. Thus we can have:

        About the role

        Position summary...

        Responsibilities

        ...

        Requirements

        Minimum Qualifications...
        Key Competencies and Standards...
        General Standards...

        Physical Demands and Work Environment: ...

        maybe as
        as well. But we need to ensure we don't create empty sections. We should not include Benefits, Pay, Schedule. Now check for any boilerplate to remove: EEO statement, "This job posting does not state or imply that these are the only duties..." maybe we should keep? It's not boilerplate? It's a disclaimer about duties; could be considered boilerplate but it's substantive? It says the employee will be required to follow any other instructions and perform any other duties requested by their leader. That's generic; maybe we can remove as it's not specific. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That line is a legal disclaimer about duties; could be considered boilerplate. Safer to remove. Also remove "M&D provides equal employment opportunity..." EEO line. Also remove "The physical demands described here are representative..." maybe we keep as it's substantive about physical demands. We need to preserve all substantive information: physical demands list is substantive. Now produce HTML. Let's craft:

        About the role

        As an Inbound Call Administrator, you'll play a key role in supporting our company's success by following proven systems and delivering exceptional customer service. In this fast-paced role, you’ll handle inbound calls with professionalism, follow procedures to ensure smooth operations, and have the opportunity to grow within our sales department. If you're detail-oriented, eager to learn, and thrive in a dynamic environment, we’d love to hear from you!

        Responsibilities

        • Create Netsuite Prospects for new inbound call customers
        • Begin creating Estimates for the sales team to process
        • Answer phones
        • Check email
        • Ensure Customer Records are accurate
        • Assist with customer questions
        • Provide excellent customer service
        • Willingness to learn and grow within the company
        • Meet or exceed key performance indicators
        • Work the 5p - 6p shifts in rotation with other upper level sales staff
        • Transfer calls to a Tech or the parts department based on customer needs
        • Follow the HHP system and report any problems to management immediately

        Requirements

        • Knowledge of Microsoft Office programs
        • Knowledge of typing, grammar, and basic written/verbal communication skills
        • Knowledge of basic customer service principles
        • Attention to detail and accuracy
        • Organizational skills
        • Information management
        • Problem analysis and problem solving skills
        • Teamwork
        • Adaptability
        • Persuasiveness
        • Competitive
        • Stress tolerance
        • Goal driven
        • Eager to learn
        • Perform all work to company policies, procedures and system standards to meet the company's strategic objective.
        • Follow dress code at all times per company policy
        • Be proficient in Job Tasks as well as Engine Training.
        • Maintain a positive and motivating attitude per company policy.
        • Manage attendance per company policy.

        Physical Demands and Work Environment

        • Prolonged periods of sitting
        • Office environment
        • Perform work at a workstation by Computer and Telephone
        • Cubicle environment with exposure to noise throughout the shift
        • Typing and entering data
        • Inbound and Outbound Calling
        • Ability to lift up to 15 pounds
        But we used heading "Physical Demands and Work Environment" which is not in the list of allowed headings. 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, but suggests those as examples. However to be safe, we could map physical demands under Requirements or maybe under a separate section but not using a heading not in list? The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot use other headings, but better to stick to those. However physical demands is substantive; we could include it under Requirements as another list, but that may be mixing categories. Could add a subsection? But we cannot use headings other than those? The instruction may be interpreted as we should use those headings when we have content for those categories; if we have other content not fitting those, we could still use

        but with appropriate heading like "Physical Demands". The examples are not exhaustive. I'd say it's okay to use other headings if needed, but better to follow the spirit: use headings for sections; we can use Physical Demands and Work Environment as a heading. But to be safe, we could incorporate physical demands into Requirements as a list under a subheading? But we cannot use subheadings without

        . Could just add a

        preceding the list: "Physical Demands and Work Environment:" then list. That would be okay