Leisure Air Desk Travel Consultant - Remote

We need to output HTML fragment with sections: Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have: - Job Type: Full time Exempt/Non Exempt Hourly (metadata, maybe drop) - Location Details: Remote Position - Schedule / Shift: Monday – Friday, 9:00 a.m. to 6:00 p.m. EST - Position Summary: paragraph. - Key Responsibilities: list of duties. - Required Qualifications: list (some repeated) - Compensation: salary range $17.76/hour to $27.62/hour with annual bonus potential. - Benefits: detailed list. - Job Posting Period: maybe drop as metadata. - Who We Are: description of company (maybe About the role? Actually "About the role" is not present; we could use "About the role" heading for Position Summary? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: Position Summary paragraph. - Responsibilities: Key Responsibilities list. - Requirements: maybe Required Qualifications? Could be Requirements heading. - Qualifications: maybe also Required Qualifications? But we shouldn't duplicate. We could treat Requirements as Required Qualifications. Qualifications maybe not needed if same. But we could include both if distinct content; but they are same. Better to have one section: Requirements (or Qualifications). Since we need to avoid thin sections, we can combine. - Benefits: Benefits section. - Pay: Compensation section. - Schedule: Schedule section. We also have location remote; could be included in About the role or maybe a short p. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, legal, etc. Remove duplicated lines. We need to preserve all substantive information. Let's extract content. Position Summary paragraph: "The Leisure Travel Consultant provides consultative travel planning and sales support for members, customers, executive management, board members, and internal partners through an inbound service environment. This role is responsible for identifying traveler’s needs, recommending and booking domestic and international travel arrangements, promoting membership and preferred vendor offerings, and delivering an exceptional end-to-end customer experience." Key Responsibilities: It's a long paragraph with sentences separated by periods but seems like a list. We need to convert to

• . Let's split by sentences (but careful not to split abbreviations). We'll produce list items each sentence. Sentences: 1. Service and sell domestic and international airline tickets, car rental, hotel and travel insurance to Leisure Travel Clients, Customers, Executive Management, Board Members, Field and Call Center Agents through an in-bound telephone environment. 2. Determine member, customer, executive client needs based on individual consultation and emphasizes preferred vendors as appropriate. 3. Cross sell membership to align with the ACG Connected Member Vision 4. Consummate sales by making necessary travel arrangements and advises Leisure travelers/arrangers of various travel information including cancellation/change penalties, schedules and fares. 5. Receive, investigate, and provide timely resolution to travel problems and issues. 6. Plan and book Western Hemisphere and European international airline reservations on the Computer Reservation System (CRS) 7. Plan and book complex international and domestic itineraries, hotel, car and rail reservations 8. Meet or exceed established performance, production and quality standards 9. Learn and use a variety of travel related information including geography and travel resource material 10. Work independently with minimal supervision 11. Arrange travel itineraries for small groups 12. Work with the Travel Group Department to procure airline agreements and book air for incentive and leisure groups 13. Offer advice on the destination and be knowledgeable about making transportation and accommodation requests 14. Keep abreast of developments in foreign countries that may influence travel arrangements or make a destination unsafe 15. Review all fare options, including Agentware, and provide enhancements to the basic travel purchase, including hotels and cars We'll output as
  • each. Required Qualifications: It repeats same line twice. Content: "High school diploma or equivalentExtensive travel agent experience with emphasis on domestic and international airline transactions done through the Computer Reservation System (CRS) and auto faring of transactions. Car, Hotel and Insurance knowledgeExtensive travel agent experience with emphasis on domestic and international airline transactions done through the Computer Reservation System (CRS) and auto faring of transactions. Car, Hotel and Insurance knowledge" It seems duplicated. We need to preserve substantive info but not duplicate. So we can list: - High school diploma or equivalent - Extensive travel agent experience with emphasis on domestic and international airline transactions done through the Computer Reservation System (CRS) and auto faring of transactions. - Car, Hotel and Insurance knowledge We could also note that experience emphasis appears twice but we keep once. Compensation: "Leisure Travel Consultants earn a competitive salary between $17.76/hour to $27.62/hour with annual bonus potential based on performance." Benefits: large list. We'll need to format as
    • for each benefit item. The benefits section includes headings like Health & Wellness, Financial Protection & Insurance, Retirement & Savings, Time Off & Leave, Career Growth & Education, Additional Perks. We could keep those as subheadings? The instruction only mentions using

      for section headings like Benefits etc. It didn't forbid using other headings inside? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use

      for those top-level sections. Inside benefits we can use

      or

      • . We could keep the benefit categories as or just plain text within

        . Probably better to keep as

        with bold headings? But we must not invent headings not allowed. Using is okay. We'll just output as

        with lines. But we need to preserve all substantive information. We'll output as

        • for each benefit bullet, preserving the details. Let's extract benefits: Health & Wellness: - Medical plans with multiple coverage options, including HSA eligibility. - Prescription drug coverage. - Dental and vision benefits. - Employee Assistance Program (confidential support services). Financial Protection & Insurance: - Company-paid basic life insurance. - Optional supplemental life insurance and dependent coverage. - Short-term and long-term disability coverage. - Critical illness, accident, and pet insurance options. Retirement & Savings: - 401(k) plan to support long-term financial goals. - 3% automatic deferral upon eligibility; may contribute 1% to 50% of eligible earnings, either pre or post tax. - Company match of 50% paid on employee contributions up to 6% of pay, payable to employees following the end of the year; immediate vesting. - Additional company contribution of 4% of pay each pay day into your account; 100% vested after three (3) years of service. - Health Savings Account (HSA) and Flexible Spending Accounts (FSA) options. Time Off & Leave: - Paid Time Off (PTO): Accrual-based, increases with tenure, eligible at 90 days of employment. Full-time new employees will receive up to 12 PTO days annually; accrual based on start date and may include additional PTO based on role and/or state & local requirements. Part-time employee PTO hours are calculated based upon the standard weekly hours the employee is scheduled to work and will accrue at a minimum of 3 hours per month. - Paid Holidays: Full-time employees are eligible for 10 company-paid holidays annually, in addition to 1 mental health day, 2 floating holidays and 1 volunteer day. Holidays vary by business unit schedules. Part-time employees are eligible for 8 company-paid holidays annually, in addition to 1 mental health day and 2 floating holidays. Holidays vary by business unit schedules. - Paid leave programs, including parental, bereavement, jury duty, and military leave. Career Growth & Education: - Tuition assistance (up to $5,250 annually; 80% covered by ACG). - Professional certification support with 100% reimbursement for eligible programs. - Opportunities for career development and advancement. Additional Perks: - Complimentary AAA membership with roadside assistance and travel discounts. - Adoption assistance program. We'll output as
          • each. Schedule: "Monday – Friday, 9:00 a.m. to 6:00 p.m. EST" Location: Remote Position (maybe include in About the role paragraph or separate

            ). Could add a

            under About the role: "Location: Remote". But we shouldn't invent headings. We'll just add a short paragraph after the summary. We must not include boilerplate like Job Posting Period, Who We Are, Important Note, etc. Those are boilerplate? "Who We Are" is company description; maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Who We Are" might be considered boilerplate but it's substantive about company. However it's not about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description? It's not about the role but it's substantive. However the sections we can output are limited to those headings. We could include "About the role" to incorporate company description? But "About the role" is supposed to be about the role, not company. However we could put company description under a paragraph within About the role? Might be okay. But we also have "Important Note" about compensation philosophy etc. That's also substantive but maybe considered boilerplate? It's about compensation philosophy; we already have Pay section. Could incorporate details into Pay section? The instruction: Prefer a few substantive sections over many thin ones. So we could merge compensation philosophy into Pay section as a paragraph. Similarly "Job Posting Period" is metadata, can drop. "Who We Are" could be placed as a paragraph under About the role? Might be okay. But we need to avoid creating sections with filler. We'll keep sections: About the role (includes Position Summary + location remote + company description maybe), Responsibilities, Requirements (Qualifications), Benefits, Pay, Schedule. We must not include Skills section if no specific skills listed besides qualifications; we could omit. Now craft HTML. We'll start with

            About the role

            then

            containing summary, location, and company description. We need to ensure we don't duplicate content. Let's write summary paragraph as given. Then add a sentence: "Location: Remote Position." Then add company description: "The Auto Club Group (ACG) provides membership, travel, insurance, and financial service offerings to approximately 14+ million members and customers across 14 states and 2 U.S. territories through AAA, Meemic, and Fremont brands. ACG belongs to the national AAA federation and is the second largest AAA club in North America. By continuing to invest in more advanced technology, pursuing innovative products, and hiring a highly skilled workforce, AAA continues to build upon its heritage of providing quality service and helping our members enjoy life’s journey through insurance, travel, financial services, and roadside assistance." We could also include the line about inclusive environment etc. That's also part of Who We Are. Let's include: "AAA prides itself on creating an inclusive and welcoming environment of diverse backgrounds, experiences, and viewpoints, realizing our differences make us stronger." Now Responsibilities

            Responsibilities

            with list items. Requirements

            Requirements

            with list items