RV Technical Support Specialist

We need to output HTML fragment with sections: About the role? The posting includes Overview, Key Responsibilities, Preferred Experience, Preferred Qualifications, Physical requirements, Benefits, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must not include Job ID etc. We must include only sections with real specific content. No filler like "commensurate with experience". Benefits are listed: Competitive salary based on experience (that's pay). Medical, dental, vision coverage, Life insurance, 401(k) with company match, Paid time off and holidays, Holiday Savings Plan. So we can have Benefits section with those items as list. Pay: "Competitive salary based on experience" is specific enough? It's not a number but it's a statement. The instruction: 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. "Competitive salary based on experience" might be considered vague but it's still a statement about pay. It's not a placeholder like "commensurate with experience" which is similar. However "competitive salary based on experience" is somewhat generic but still states that salary is competitive and based on experience. Might be acceptable. The instruction says never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salary based on experience" is similar to "commensurate with experience". It's vague but not exactly placeholder. Might be considered filler. Safer to not create Pay section if it's just that vague statement. However we could embed pay info within Benefits or Overview? The instruction: Prefer a few substantive sections over many thin ones. So we could combine Pay into Benefits? But Benefits section already exists. Could we add a

about competitive salary within Benefits? Probably better to have Benefits section only, and not separate Pay. Schedule: not mentioned. So omit Schedule. We need sections: About the role (maybe Overview), Responsibilities, Requirements (maybe Preferred Experience + Preferred Qualifications), Skills (maybe computer skills, communication), Benefits. Also maybe Physical requirements could be part of Requirements? But we have to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have Overview paragraph: "Overview: The RV Technical Support Specialist provides phone-based technical support..." That's about the role. So we can have

About the role

with that paragraph. Key Responsibilities: list. Preferred Experience and Preferred Qualifications: could be combined into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have Requirements (maybe Preferred Experience) and Qualifications (Preferred Qualifications). Or we could have Requirements covering both experience and qualifications. But better to separate: Requirements (Preferred Experience) and Qualifications (Preferred Qualifications). Also Skills: we have Advanced computer skills, Excellent communication and organizational skills, Comfortable working in fast-paced environment. Could be Skills section. Physical requirements: maybe could be part of Requirements? But we don't have a heading for Physical requirements. Could embed within Requirements as a list? Might be okay. Benefits: list. We must not include boilerplate like EEO, etc. We must preserve all substantive information. So we need to include all details from Overview, Responsibilities, Preferred Experience, Preferred Qualifications, Physical requirements, Benefits. We must not invent or summarize away detail. So we need to keep each bullet. Let's extract details. Overview paragraph: "The RV Technical Support Specialist provides phone-based technical support and troubleshooting assistance to customers experiencing issues with their RV. The primary goal of this position is to resolve customer concerns during the initial call whenever possible and reduce unnecessary transfers to dealership Service departments. This position will assist customers with common RV systems and concerns, including electrical systems, batteries, plumbing, water heaters, HVAC systems, refrigerators, appliances, slide-outs, leveling systems, solar systems, converters/inverters, and other RV components." Key Responsibilities bullet list: - Answer customer calls involving RV technical or operational concerns. - Diagnose issues by asking appropriate troubleshooting questions. - Guide customers through safe, approved troubleshooting steps. - Assist with common RV systems, components, and appliance concerns. - Determine whether an issue can be resolved remotely or requires Service, Parts, Warranty, or technician assistance. - Accurately document the customer's concern, troubleshooting performed, and resolution. - Provide clear documentation when escalating an issue to another department. - Follow up on unresolved technical concerns when needed. - Work with Service teams to identify common issues and develop troubleshooting resources. - Provide knowledgeable, professional, and customer-focused support. Preferred Experience bullet: - RV service, technician, service advisor, warranty, parts, or similar technical experience is preferred. Inbound Communication Management bullet list (under Preferred Experience? Actually it's a subheading but we can treat as part of Responsibilities? It's more about duties). The text: "Inbound Communication Management: Answer phone calls in a prompt, friendly, and professional manner. Conduct client interviews and verify information using the FTRV word track. Handle online chats as needed to support customers in real time." CRM & Task Management bullet list: - Locate or create company entities in the CRM by searching names or phone numbers. - Create and assign tasks based on customer needs and internal workflows. - Follow up on Priority 7 Tasks via the Task Command Center and alert users of overdue tasks. Call Routing & Support bullet list: - Hot transfer calls to the appropriate party or department efficiently. - Check phone lines each morning and report issues to the supervisor promptly. - Perform other duties as assigned by Management. Lead Monitoring bullet list: - Monitor the New Leads Report for Parts and Service to ensure timely response. - Use Interact to confirm lead parsing and assist with lead flow as needed. These are all responsibilities; we could combine them under Responsibilities as a single list, but we need to preserve all detail. We can keep them as sub-bullets? The instruction: Use

• for any list of duties/requirements/benefits. So we can have a single
  with all responsibility items, maybe grouping with
  • that contain multiple sentences. That's fine. Preferred Qualifications bullet list: - High school diploma or GED; or one to three months related experience and/or training; or an equivalent combination of education and experience. - Advanced computer skills with Google Mail, Sheets, Docs, Calendar, internet software, and Sys2K (Dealer Management Software). - Excellent communication and organizational skills. - Comfortable working in a fast-paced environment with frequent task switching. Physical requirements bullet list: - Regularly required to stand, walk, talk, hear, use hands to handle or feel, and reach with hands and arms. - Frequently required to sit, climb, balance, stoop, kneel, crouch, or crawl. - Must be able to regularly lift up to 10 lbs, frequently lift up to 15 lbs, and occasionally lift up to 25 lbs. - Specific vision requirements include close vision, peripheral vision, depth perception, and the ability to adjust focus. - The work environment has moderate noise levels. Benefits bullet list: - Competitive salary based on experience. - Medical, dental, and vision coverage. - Life insurance. - 401(k) with company match. - Paid time off and holidays. - Holiday Savings Plan. We also have a closing paragraph: "Join Our Growing Team! At Fun Town RV, we value our employees and provide opportunities for career advancement in an exciting, fast-growing industry. If you’re ready to be part of a company that values hard work and dedication, apply today!" This is promotional; we might consider it boilerplate? It's not EEO but it's a call to action. The instruction: Remove application instructions. This is like "apply today!" which is application instruction. So we should remove that. Also "Join Our Growing Team!" maybe considered fluff but it's substantive? It's about company culture. Might be okay to keep as part of About the role? But it's more like a closing. Safer to omit as it's akin to application encouragement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the "Join Our Growing Team!" and "apply today!" lines. Also remove the EEO paragraph at end. Now we need to output HTML fragment only. Structure:

    About the role

    Overview paragraph.

    Responsibilities

    • ... (list all responsibility items)

    Requirements

    • Preferred Experience: RV service, technician, service advisor, warranty, parts, or similar technical experience is preferred.
    • Inbound Communication Management: Answer phone calls in a prompt, friendly, and professional manner. Conduct client interviews and verify information using the FTRV word track. Handle online chats as needed to support customers in real time.
    • CRM & Task Management: Locate or create company entities in the CRM by searching names or phone numbers. Create and assign tasks based on customer needs and internal workflows. Follow up on Priority 7 Tasks via the Task Command Center and alert users of overdue tasks.
    • Call Routing & Support: Hot transfer calls to the appropriate party or department efficiently. Check phone lines each morning and report issues to the supervisor promptly. Perform other duties as assigned by Management.
    • Lead Monitoring: Monitor the New Leads Report for Parts and Service to ensure timely response. Use Interact to confirm lead parsing and assist with lead flow as needed.
    But maybe we should separate Requirements (Preferred Experience) and Qualifications (Preferred Qualifications). However we have many responsibility subheadings; maybe better to keep Responsibilities as a single list with all duty items (including Inbound Communication Management etc). Then Requirements could be just Preferred Experience. Qualifications could be Preferred Qualifications. Skills could be computer skills, communication, organizational, fast-paced environment. But we already have those in Qualifications. Could combine. Let's decide: - About the role: overview paragraph. - Responsibilities: list of duty items (Answer customer calls..., Diagnose issues..., Guide customers..., Assist with common RV systems..., Determine whether..., Accurately document..., Provide clear documentation..., Follow up..., Work with Service teams..., Provide knowledgeable..., plus Inbound Communication Management, CRM & Task Management, Call Routing & Support, Lead Monitoring). That's many items; we can keep them as separate
  • each. - Requirements: Preferred Experience bullet. - Qualifications: Preferred Qualifications bullet list (education, computer skills, communication/organizational, fast-paced environment). - Skills: maybe we could extract Advanced computer skills, Excellent communication and organizational skills, Comfortable working in fast-paced environment. But those are already in Qualifications. To avoid duplication, we could not have Skills section; we can put those under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Qualifications and Skills into one Qualifications section. But we need to follow headings list; we can still use Qualifications heading and include all qualification items. - Benefits: list. - Physical requirements: we haven't placed. Could be part of Requirements? But we already have Requirements as Preferred Experience. Could add another subsection under Requirements? Or we could create a separate section? There's no heading for Physical requirements; we could embed within Requirements as a list item. But that might be mixing. Perhaps better to add a Requirements section that includes both Preferred Experience and Physical requirements. But the instruction says use headings like Requirements, Qualifications, Skills, Benefits. So we can have