Service Coordinator

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "APPLY NOW — Precision Coordinators Wanted. Hit Apply..." etc. Also remove "About DuraServ" maybe? That's company description; is that substantive? It's about company, not role. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About DuraServ" is not explicitly listed but could be considered company overview; maybe keep? It's not about the role specifics. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview could be considered substantive? But they didn't say to remove company description. However they said "Prefer a few substantive sections over many thin ones." Might be okay to include an "About the company" but not listed as allowed heading. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About the role" can include description of role, mission, etc. "Responsibilities" includes What You'll Do bullet points. "Requirements" includes Required (must have). "Qualifications" maybe includes Preferred? Could combine. "Skills" maybe include Microsoft Office proficiency etc. "Benefits" includes What's In It For You bullet points (benefits). "Pay" includes compensation range. "Schedule" maybe not present; they mention On-site presence required, but not schedule details like full-time, hours. Could we infer? They didn't give schedule specifics. Should not create Schedule section unless posting actually states them. So we omit Schedule. We must not include filler like "commensurate with experience" as heading content? Actually they said 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. For Pay, they have compensation range, so we can include Pay section with that info. For Benefits, they have bullet list, so include Benefits. We must not include "commensurate with experience" as filler inside Pay? It's part of the sentence: "Competitive compensation commensurate with experience". That's not filler; it's actual phrase. It's okay. We need to remove duplicated lines, application instructions, EEO boilerplate, etc. Also remove "NOTE TO EXTERNAL RECRUITING AGENCIES..." etc. We need to keep location: Santa Fe Springs, CA (On-Site). Where to put? Could be in About the role paragraph. We need to preserve all substantive info: role description, responsibilities, requirements, preferred, benefits, compensation, note about on-site, etc. Let's extract sections. About the role: The introductory paragraphs: "WHERE DETAILS MAKE A MISSION-CRITICAL IMPACT. The Technician Shows Up Ready.... This Role Is the Operational Nerve Center of the Branch...." plus maybe location. We'll combine into a paragraph. Responsibilities: The "What You'll Do" bullet points grouped under categories: Customer & Communication, Dispatch & Coordination, Administration & Accuracy. We'll output as a single

• list? Could keep subheadings? Not allowed headings besides those; we could embed subheadings as plain text inside
• ? Probably better to just list each duty as
• . We'll preserve the bullet points exactly. Requirements: The "Required" bullet list: High School diploma or equivalent, Proficiency with Microsoft Office — Word, Excel, and Outlook are daily tools in this role, Strong organizational and communication skills — you manage multiple priorities simultaneously without losing quality on any of them, Ability to work in a fast-paced, high-volume environment where responsiveness and accuracy are equally non-negotiable. Qualifications/Skills: The "Preferred" bullet list: 1–3 years of experience in a service coordination, dispatch, administrative, or operations support role, Experience with work order management, invoicing, or service administration in a field service or similar environment, Background in the commercial dock and door, mechanical services, or industrial services industry is a meaningful advantage. Also maybe "Administratively fluent — you know your way around Microsoft Office (Word, Excel, Outlook), pick up new systems quickly, and maintain records that hold up to scrutiny" is under Who You Are (skills). Actually "Who You Are" includes many skill traits: Organized by instinct..., Responsive and professional..., Detail-oriented..., Comfortable in a fast-paced environment..., Administratively fluent..., A team anchor... Those are more like skills/attributes. Could go under Skills section. We'll decide: Skills section can include those traits plus Microsoft Office proficiency. Requirements already includes Microsoft Office proficiency; but we can keep it there. To avoid duplication, we can keep Microsoft Office under Requirements (as required). Skills can include the personal attributes: organized, responsive, detail-oriented, comfortable fast-paced, administratively fluent, team anchor. Also maybe "Ability to work in a fast-paced, high-volume environment" is already in Requirements. We'll avoid duplication. Better: Use Requirements for mandatory qualifications (education, experience, skills). Use Preferred for preferred qualifications. Use Skills for personal attributes/soft skills. But the instruction says we can use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications and Skills. We'll allocate: - Requirements: Hard requirements (HS diploma, Microsoft Office proficiency, strong organizational/communication skills, ability to work fast-paced high-volume). - Qualifications: Preferred qualifications (1-3 years experience, work order management experience, industry background). - Skills: Personal attributes (organized by instinct, responsive/professional, detail-oriented, comfortable fast-paced, administratively fluent, team anchor). Also maybe "Ability to work in a fast-paced, high-volume environment" is already in Requirements; we won't duplicate. Benefits: The "What's In It For You" bullet list: Competitive compensation commensurate with experience, Full benefits package: medical, dental, vision, and 401K with company match, Company-provided life insurance, short-term and long-term disability, A role where your work has immediate, visible impact on the branch and the customers it serves, A stable, office-based environment at a company that invests in the people who keep operations running, A path to growth within branch operations for high performers who want to take on more responsibility. Pay: Compensation range: $53,000 to $72,000, plus note about salary/hourly: Salary, plus mention of eligibility for medical etc (but that's benefits). We'll include the range and note that it's salary. We must not include boilerplate like "Compensation This compensation information is a good faith estimate..." etc. That's somewhat explanatory; maybe we can keep the range but drop the explanatory sentence? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The explanatory sentence about good faith estimate is substantive? It's about the compensation info. Might be considered part of compensation section. However it's somewhat generic; but it's part of the posting. I'd keep it? It's not boilerplate like EEO; it's specific to compensation disclosure. Might be okay to keep. But we need to avoid too much fluff. The instruction says "Prefer a few substantive sections over many thin ones." Including that sentence adds a thin line. Could drop? But it's substantive info about the compensation being a good faith estimate. I'd keep it briefly. Also we need to remove "Equal Opportunity Employment" etc. Remove that. Also remove "Accommodation" etc. Also remove "NOTICE TO EXTERNAL RECRUITING AGENCIES & SEARCH FIRMS". Also remove "About DuraServ" maybe? It's company overview; not required heading; could be omitted as not under allowed headings. But it's substantive about company. However we have no heading for company description; we could fold into About the role? Might be okay to include a short paragraph about DuraServ under About the role? But the role description already includes some. The "About DuraServ" paragraph is separate; we could incorporate it into About the role as additional context. But we must not invent or summarize away detail; we can keep it as part of About the role paragraph. Thus About the role will include: the initial mission-critical impact paragraph, the role as operational nerve center, location Santa Fe Springs, CA (On-Site), and maybe the DuraServ overview. Let's craft. We must output only HTML fragment, no /, no markdown fences. We'll produce:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ...

  We must not include Schedule. Now let's extract exact phrasing, preserving details. About the role paragraph: Combine: "WHERE DETAILS MAKE A MISSION-CRITICAL IMPACT. The Technician Shows Up Ready. That's because of the work you did before they left. DuraServ is looking for a Service Coordinator who dispatches with precision, invoices without error, and keeps every customer call, service order, and parts request moving without a missed beat. Santa Fe Springs, CA (On-Site) This Role Is the Operational Nerve Center of the Branch. DuraServ's field technicians keep commercial dock and door systems running for warehouses, distribution centers, and industrial facilities across the country. But before a technician ever arrives on site, a Service Coordinator has already taken the call, created the service order, confirmed the parts, dispatched the right person, and set the customer's expectation correctly. After the call closes, the Service Coordinator has invoiced accurately and filed every record clean. This is not a passive administrative role. It's an active coordination function that connects customers, technicians, parts suppliers, and management into a single, seamless service experience. Every missed detail has a downstream consequence. Every detail handled correctly keeps the branch running the way it's supposed to. If you thrive in a fast-paced environment where accuracy matters and no two days look the same — this is your kind of role." Also add DuraServ overview: "DuraServ is a national leader in commercial dock and door solutions, operating across the U.S. and Canada since 2001. Our field technicians are not an afterthought — they are the standard by which DuraServ is measured in every market we serve." We'll combine into one or two paragraphs. Probably one paragraph is fine. Now Responsibilities: list each bullet from "What You'll Do". Let's extract exactly: - Answer inbound calls and email communications — providing responsive, professional support and direction on customer inquiries, returning calls promptly without letting anything fall through - Review incoming sales and service leads, coordinating delegation to the appropriate person efficiently and without delay - Serve as a professional point of contact for internal and external customers across every interaction — your tone, your accuracy, and your follow-through represent DuraServ - Schedule and dispatch service calls effectively — matching the right technician to the right job with the right information at the right time