Ticketing Coordinator

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. Let's parse the posting. Job Details: Full Time / Part Time: Full Time, FLSA Classification: Non-Exempt, Business Unit: Corporate, Reports to: Operations Manager, Travel Requirement: No. That's metadata; we can fold into a short

or drop. Probably we can include a short paragraph summarizing these details. Job Description: "Select’s Ticketing Coordinator will be responsible for providing exceptional service from invoice creation to distribution. The Ticketing Coordinator will handle a high volume of transactions, working with internal and external customers ensuring billing needs are met. The essential job functions include, but are not limited to ..." Then list bullet points. We need to decide sections: About the role (maybe a short description), Responsibilities (list of duties), Requirements (education, skills), Qualifications (maybe same as requirements?), Skills (maybe separate), Benefits (list benefits), Pay (if present), Schedule (if present). The posting includes "Compensation Information: Compensation is competitive and commensurate with experience." That's vague; we should NOT create Pay section unless posting actually states them. It says "competitive and commensurate with experience." That's not specific; we should not include Pay section because it's not a concrete figure. 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. So we should not create Pay section. Schedule: "12 hour shift work, 7am - 7pm. Other start/stop times considered." That's schedule info. That's specific enough? It states shift times. So we can include a Schedule section with that info. Benefits: "Top Tier Benefits Medical, dental, vision, coverage in addition to life and disability insurance plans. Paid Vacation Days and Paid Holidays. Retirement and Savings (401K) Plan with Company match. Referral bonus with no cap on amount of referrals. Paid Training." That's specific benefits; we can include Benefits section. Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Possibly also "Qualifications" maybe overlapping with Requirements; but we can combine or separate. The instruction: Prefer a few substantive sections over many thin ones. So we might combine Requirements and Qualifications into one section? But they ask to use headings for those specific names if we include them. We could include Requirements (education, experience, skills) and Skills maybe separate? However the posting lists requirements: high school diploma/GED, competency in Microsoft apps, math ability, excellent communication, attention to detail, multitask, strong organizational, 10 key by touch. Also mentions Select Values and Guiding Principles (W, A, T, E, R) but that's maybe not a requirement. Could be considered "Qualifications". We could have Requirements (education, experience) and Skills (technical/soft skills). But to avoid many thin sections, maybe combine into Requirements (including skills). However they want separate headings if we have content. Let's think: The posting has a "Requirements" bullet list. It also mentions "Select Values and Guiding Principles" which could be considered "Qualifications". But we could treat that as part of Requirements as well. Better to have sections: About the role (short paragraph), Responsibilities (list), Requirements (list), Benefits (list), Schedule (paragraph). That's four sections. Avoid Qualifications and Skills separate to keep few sections. We must not repeat job title as heading. So no

Ticketing Coordinator

. Use

About the role

etc. We need to preserve all substantive information. Let's extract. About the role: Could be the first sentences: "Select’s Ticketing Coordinator will be responsible for providing exceptional service from invoice creation to distribution. The Ticketing Coordinator will handle a high volume of transactions, working with internal and external customers ensuring billing needs are met." That's about role. Responsibilities: The essential job functions list: - Perform review of ticket pricing daily and process for manager review. - Perform review of customer requirements/pricing before generating and posting tickets. - Process tickets per customer requirements in a timely manner. - Assist Credit and Collections with researching and resolving disputes. - Review/Process rejected/disputed tickets daily. - Submit tickets into customer ticketing portals/EDI. - Communicate with other departments to resolve discrepancies. - Assist with month-end closing. - Maintain and understand customer requirements to pay. - Practice open communication with Operations and team leaders to ensure everyone is aware of any customer requirements/pricing changes. - Practice open communication with AR teams to ensure emails and questions are being answered in a timely manner. - Run and monitor reports to identify ticketing issues daily to ensure ticket accuracy before sending to customer/invoicing. Also "Other Duties" note: "Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the employee for this job. Duties, responsibilities and activities may change at any time with or without notice." That's boilerplate; we should remove it as it's not substantive? It's a disclaimer; maybe we can drop as it's not specific duty. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This "Other Duties" note is likely boilerplate; we can drop. Requirements: list: - High school diploma /GED. - Competency in Microsoft applications including Excel, Word, and Outlook. - Ability to add, subtract, multiply, and divide in whole numbers, common fractions and decimals. - Excellent communication skills (verbal and written). - Attention to detail and ability to multitask. - Must have strong organizational skills. - 10 key by touch. Also "Select Values and Guiding Principles W: Working Safe A: Accountability T: Teamwork E: Excellence R: Respect" Might be considered qualifications but it's more cultural; we could include as part of Requirements or maybe as a separate "Qualifications" section. But to keep few sections, we could incorporate into Requirements as a bullet: "Adherence to Select Values: Working Safe, Accountability, Teamwork, Excellence, Respect." That's substantive. Benefits: list: - Medical, dental, vision coverage. - Life and disability insurance plans. - Paid Vacation Days and Paid Holidays. - Retirement and Savings (401K) Plan with Company match. - Referral bonus with no cap on amount of referrals. - Paid Training. Schedule: "12 hour shift work, 7am - 7pm. Other start/stop times considered." Also FLSA Classification: Non-Exempt, Business Unit: Corporate, Reports to: Operations Manager, Travel Requirement: No. Could be included in About the role paragraph or a short metadata paragraph. We could add a short

after About the role maybe "Position details: Full-time, Non-Exempt, Corporate unit, reports to Operations Manager, no travel required." That's preserving info. We must not include Job ID/requisition numbers. Now produce HTML fragment: use

for each section heading. Use

• for lists. Use

  for prose. We must not output any extra text outside HTML. No markdown fences. Let's craft. Structure:

  About the role

  Select’s Ticketing Coordinator will be responsible for providing exceptional service from invoice creation to distribution, handling a high volume of transactions while working with internal and external customers to ensure billing needs are met. Position details: Full‑time, Non‑Exempt, Corporate business unit, reports to the Operations Manager, no travel required.

  Responsibilities

  • Perform review of ticket pricing daily and process for manager review.
  • Perform review of customer requirements/pricing before generating and posting tickets.
  • Process tickets per customer requirements in a timely manner.
  • Assist Credit and Collections with researching and resolving disputes.
  • Review/Process rejected/disputed tickets daily.
  • Submit tickets into customer ticketing portals/EDI.
  • Communicate with other departments to resolve discrepancies.
  • Assist with month‑end closing.
  • Maintain and understand customer requirements to pay.
  • Practice open communication with Operations and team leaders to ensure everyone is aware of any customer requirements/pricing changes.
  • Practice open communication with AR teams to ensure emails and questions are being answered in a timely manner.
  • Run and monitor reports to identify ticketing issues daily to ensure ticket accuracy before sending to customer/invoicing.

  Requirements

  • High school diploma or GED.
  • Competency in Microsoft applications including Excel, Word, and Outlook.
  • Ability to add, subtract, multiply, and divide in whole numbers, common fractions and decimals.
  • Excellent communication skills (verbal and written).
  • Attention to detail and ability to multitask.
  • Strong organizational skills.
  • 10‑key by touch.
  • Adherence to Select Values: Working Safe, Accountability, Teamwork, Excellence, Respect.

  Benefits

  • Medical, dental, and vision coverage.
  • Life and disability insurance plans.
  • Paid vacation days and paid holidays.
  • Retirement and savings (401K) plan with company match.
  • Referral bonus with no cap on the number of referrals.
  • Paid training.

  Schedule

  12‑hour shift work, 7 am – 7 pm; other start/stop times may be considered.

  Check for any boilerplate left: We removed "Other Duties" note, removed EEO, legal, etc. We kept all substantive info. Check for any repeated content: Not repeated. Check for any missing: We included FLSA, Business Unit, Reports to, Travel in About the role paragraph. Good. Check for any "Compensation Information": we omitted as per rule. Check for "Physical Demands and Exposures": That's substantive but not covered by any section headings we have. Should we include? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Physical demands is specific content. We could add a section for "Physical Demands" but the allowed headings list includes only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands is not in that list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might imply we should use those headings if we have those sections; but we could also use other headings? The examples suggest those are the expected headings. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings