Greeter-(Paoli Hospital)

We need to output HTML fragment with sections: About the role? Actually posting includes "About Towne Towne is an exceptional arrival..." That's company description. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings where appropriate. We have: - Company description: maybe "About the role"? Actually "About the role" would be description of the job. Could use "About the role" for summary of role. We have a Summary section: "The Greeter Service Ambassador is responsible for welcoming..." That's essentially responsibilities. Could put under Responsibilities. We have "Essential Functions" with bullet points and percentages. That's responsibilities/duties. So we can put under Responsibilities as a list. We have "Qualifications" section with Education, Licensure, Work Experience, Knowledge, Skills. So we can have Qualifications heading and inside maybe subpoints? But we only allowed

• for any list of duties/requirements/benefits. For qualifications we can list as
  • each item. We have "Skills" separate list; could be under Skills heading. We have Benefits: described. So Benefits heading. We have Pay: Compensation: hourly base pay $18 per hour. So Pay heading. We have Schedule: Work Schedule: Part time M-F 5pm-9pm weekend availability. So Schedule heading. We also have "About Towne" company description; could be placed under About the role? Or maybe we can omit as not required? The instruction: include a section ONLY when the posting has real, specific content for it. The company description is not about the role but about the company. Could we put under About the role? Might be okay but it's not exactly role. However we could create a section "About the role" and put the summary of role there, and maybe include company description as a short paragraph before? But we must not repeat job title as heading. We can have a

    for company description before sections? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid stray

    outside sections. But they said use

    for section headings,

    • for any list,

      for prose. So we can have a

      for company description, then headings for sections. We must remove boilerplate: cookie/navigation/legal/EEO etc. At end there is "Click here for important notices..." etc. Remove. Also remove duplicated lines. We need to preserve all substantive information. Let's extract: Company description: "About Towne Towne is an exceptional arrival through departure experience company. With its best-in-class parking and hospitality solutions and its fully integrated technology platform, we deliver seamless parking and mobility experiences in the places where people live, learn, work, play, rejuvenate, and recover. Towne’s 14,000 team members create smiles by delivering exceptional experiences for the millions of people we proudly serve each year. For nearly 40 years, Towne has been committed to providing the best experience, delivered by the best team, powered by innovative technology, enhancing lives and communities. For more information, visit www.towne.com and follow us on LinkedIn." We can keep that as a

      . Then we have "Job Details" heading but we ignore as not needed. Compensation: "Compensation: Towne Park is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location. The hourly base pay is $18 per hour" We need Pay section: include that info. We should not include filler like "commensurate with experience" etc? Actually they said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "competitive, fair, and commensurate compensation" is somewhat filler but it's part of the sentence. However we can keep the substantive: hourly base pay is $18 per hour. The rest maybe considered filler but we can keep as it's not placeholder. It's okay. Work Schedule: "The work schedule for this position is Part time M-F 5pm-9pm weekend availability" Schedule section. Benefits: "Employees are eligible to enroll in accident insurance, critical illness insurance, hospital indemnity insurance, and telemedicine benefits. Employees are also able to enroll in the company’s 401k retirement savings plan. Eligibility requirements depend on your job classification, length of employment and number of hours worked. Benefits are subject to change and may be subject to a specific plan or program terms. Seasonal and temporary roles are not eligible for benefits outlined above." We keep that. Summary: "The Greeter Service Ambassador is responsible for welcoming and greeting patients to the facility in a friendly, efficient and courteous manner. The Greeter Service Ambassador is also responsible for assisting with patient and guest inquiries, directions, and initial questions regarding the facility or services. The Greeter Service Ambassador is also responsible for entering patient information into the hospital database accurately and protects patient privacy through following HIPAA standards. Computer skills and data entry are critical skills for this role." That's responsibilities; we can put under Responsibilities. Essential Functions: list with percentages. We'll turn into

      • each item. Qualifications: Education, Licensure, Work Experience, Knowledge, Skills. We can break into sub-sections? But we only allowed headings from list; we could keep Qualifications heading and inside have
        • for each bullet: Education: High school diploma or GED. Required Licensure... etc. But we also have Skills list separate; we could put Skills under Skills heading. Better: Qualifications heading includes Education, Licensure, Work Experience, Knowledge. Then Skills heading includes the skills list. Let's extract Qualifications items: - Education: High school diploma or general education degree (GED). - Required Licensure, Certification, Etc.: Must be at least 18 years of age and be able to pass a criminal background and drug screen. - Work Experience: One to three month(s) related experience and/or training; OR equivalent combination of education and experience. - Knowledge: Knowledge of equipment including telephones, codes and alarms, two-way radios, disaster phone, fire panel and surveillance system We'll put each as
        • . Skills list: many items separated by ability. We'll put each as
        • under Skills heading. Also there is "SCOPE Authority To Act", "Budget Responsibility", "WORKING CONDITIONS & PHYSICAL DEMANDS". Those could be considered Requirements? But we already have Qualifications and Skills. Could we put them under Requirements? The instruction: use headings like Requirements, Qualifications, Skills. We have Qualifications and Skills already. We could add a Requirements heading for scope, budget, working conditions. But we must only include if real specific content. There is content. So we can add Requirements heading and include those paragraphs as

          or

          ? They are prose. We'll use

          . But we must not create thin sections; we already have many sections. Might be okay. Let's list sections we will output: -

          company description (prose) -

          About the role

          maybe we can put the Summary here? Actually we have Summary separate. Could combine Summary under About the role. But we already have Responsibilities heading for duties. The instruction examples include About the role as a heading. So we can put the Summary under About the role. Then Responsibilities heading for Essential Functions list. Thus:

          About the role

          The Greeter Service Ambassador is responsible for welcoming and greeting patients to the facility in a friendly, efficient and courteous manner. The Greeter Service Ambassador is also responsible for assisting with patient and guest inquiries, directions, and initial questions regarding the facility or services. The Greeter Service Ambassador is also responsible for entering patient information into the hospital database accurately and protects patient privacy through following HIPAA standards. Computer skills and data entry are critical skills for this role.

          Responsibilities

          • Maintains pleasant, friendly and professional demeanor with all Guest/Patients, co-workers, and clients. Acknowledges and greets Guest/Patients with a professional and friendly demeanor. - 25%
          • Demonstrates a willingness and ability to assist others. Monitors and responds to emergencies on a priority basis. Assists visitors with directions, information and other inquiries. - 25%
          • Enters confidential personal patient information into hospital database in order to register them for their service. Delivers messages, items and/or amenities as requested. Ensures that patient and business confidentiality is maintained at all times. - 25%
          • Helps to ensure a healthy and safe environment through the sanitization and light cleaning of personal work area using materials provided as needed. - 10%
          • Reports all accidents and incidents observed on shift to Manager immediately. Uses only equipment trained to use and operates all equipment in a safe manner. Is knowledgeable of hospital disaster codes and response plans. Follows client standard operating procedures for disaster codes and response plans. - 10%
          • Transports patients via wheelchair within the facility. - 5%

          Qualifications

          • Education: High school diploma or general education degree (GED).
          • Required Licensure, Certification, Etc.: Must be at least 18 years of age and be able to pass a criminal background and drug screen.
          • Work Experience: One to three month(s) related experience and/or training; OR equivalent combination of education and experience.
          • Knowledge: Knowledge of equipment including telephones, codes and alarms, two-way radios, disaster phone, fire panel and surveillance system.

          Skills

          • Ability to read, speak and write standard English language
          • Ability to read and comprehend simple instructions, short correspondence and memos
          • Ability to write simple correspondence
          • Ability to understand 24 hour and military time systems
          • Ability to perform general typing and and/or basic computer skills
          • Ability to prioritize tasks and remain calm in stressful situations
          • Must have strong communication skills
          • Must have familiarity with data entry
          • Must understand phone etiquette
          • Must understand HIPPA requirements as they pertain to handling sensitive patient information
          • Customer service experience preferred

          Benefits

          Employees are eligible to enroll in accident insurance, critical illness insurance, hospital indemnity insurance, and telemedicine benefits. Employees are also able to enroll in the company’s 401k retirement savings plan. Eligibility requirements depend on your job classification, length of employment and number of hours worked. Benefits are subject to change and may be subject to a specific plan or program terms. Seasonal and temporary roles are not eligible for benefits outlined above.

          Pay

          Compensation: Towne Park is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location. The hourly base pay is $18 per hour.

          Schedule

          The work schedule for this position is Part time M-F 5pm-9pm weekend availability.

          Requirements

          Scope Authority To Act: Job is fairly routine. Incumbent follows established practices and procedures. Duties are performed with specific directions given and work is checked or verified on a frequent basis. Decisions are made within specific operational instructions and departmental guidelines. Errors in judgment could affect the smooth and efficient operation of the department.