Sales Coordinator

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate (EEO, etc). Preserve all substantive information. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to parse the posting. The posting text: "Omni Providence Hotel The Omni Providence is a landmark hotel in Rhode Island. This hotel is located in the exciting city of Providence and is attached to the Rhode Island Convention Center, Amica Mutual Pavilion, as well as the Providence Place Mall. Guests find themselves in walking distance to everything the city has to offer from historical sights to amazing restaurants. The Omni Providence a beautiful Convention Hotel but our associates are what separate us from the rest of the hotels. Our culture provides an atmosphere that allows our associates to learn and grow in their professional development in a fun environment. We strongly encourage promotions from within our company, and as a result, our staff has a solid hospitality foundation. Our diverse staff comes from many different countries in the world and provides a fantastic atmosphere to develop both from a professional and personal level. Although we offer a complete benefit package for all of our full-time associates, all of our associates are provided the greatest benefit of all which is “opportunity”. Overview Handles all administrative duties required by the Sales and Marketing Divisions in order to provide superior services to our guests. Responsibilities Sell and detail wedding blocks (on Manager's behalf)Act as Convention Services contact for smaller group blocks (typically only individual call in, rooms only, no cancellation or attrition blocks to start)Turn over signed sales contracts and distribute them through the proper channelsRun and distribute daily reports (such as Change Log & Daily Events) and weekly reports (such as 10 Day BEO Distribution, Cutoff Reports, & Resumes)Take phone inquiries regarding potential group business and all other calls to the sales office (if the manager does not pick up their line within 3 rings, you will answer on their behalf and either assist the guest or transfer them to the manager’s voicemail)General tasks for sales managers and the CS team including setting up amenities/amenity cards, creating and updating reservations in Opera, etc.Answering phone calls and emails from clients (ex. answering general hotel questions, rooming list requests, etc.)Create BEOs for in-house events (ex. ASC events like the bimonthly Koffee Klatch, or departmental OST meetings)Manage the third party reservations inbox (basically just checking the inbox daily and making any new reservations that come through)Coordinating with Housekeeping to get show rooms when sales managers have a site visitAttend meetings such as BEO or staff meeting (if you have groups with resumes or events), and the weekly cutoff report callConduct site visits for wedding block clients who want to view guest roomsAssist MRC with rebates, commissions, end of month reporting, or pick up reports (on a backup basis)Build wedding room blocks if Group Coordinator is very busyCreate Delphi.FDC reports or merge documentsMake sales kits Qualifications Must be able to work alone as well as work well with others.Must have Associate's Degree or equivalent.Must have good communication skills.Must be extremely computer savvy (Microsoft Word, Publisher, Outlook, Express, Excel).Previous knowledge of Delphi, Opera and Synergy preferred.Must have good organizational skills. Omni Hotels & Resorts Is An Equal Opportunity/AA/Disability/Veteran Employer. The EEO Is The Law Poster Is Available Using The Following Link EEOC is the Law Poster. Omni Hotels & Resorts does not discriminate on the basis of any protected category with respect to the payment of wages. If you are interested in applying for employment with Omni Hotels & Resorts and need special assistance to apply for a posted position, please send an email to: applicationassistance@omnihotels.com." We need to extract sections: About the role (overview), Responsibilities, Qualifications (maybe also Requirements?), Skills, Benefits, Pay, Schedule. We have an "Overview" paragraph: "Handles all administrative duties required by the Sales and Marketing Divisions in order to provide superior services to our guests." That's the overview. Responsibilities: a long list of duties. Qualifications: list of qualifications. Skills: maybe we can extract from qualifications: "Must be able to work alone as well as work well with others." "Must have good communication skills." "Must be extremely computer savvy (Microsoft Word, Publisher, Outlook, Express, Excel)." "Previous knowledge of Delphi, Opera and Synergy preferred." "Must have good organizational skills." Also "Must have Associate's Degree or equivalent." That's more qualification than skill. But we can treat Skills as separate if there is explicit skill content. The posting didn't have a separate "Skills" heading; but we can create a Skills section if we have specific skill items. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Skills into one section? But they ask to use headings for those categories if content exists. We have qualifications content; we may not have separate skills beyond those listed. Could treat the qualifications as both qualifications and skills. But we need to decide. We also have Benefits: mention "Although we offer a complete benefit package for all of our full-time associates, all of our associates are provided the greatest benefit of all which is “opportunity”." That's a benefit statement. So we can include Benefits section with that sentence. Pay: No mention of pay/salary. So we should NOT include Pay section. Schedule: No mention of schedule. So omit. Requirements: Might be similar to qualifications; but we have qualifications already. Could treat Qualifications as Requirements. But we have both headings; we need to decide if we have content for Requirements separate from Qualifications. The posting only has "Qualifications". No separate "Requirements". So we should not create a Requirements heading unless we have specific content. We could treat the qualifications as requirements, but we already have Qualifications heading. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include Qualifications heading. Requirements maybe not needed. We'll omit Requirements if no specific content. About the role: we have overview paragraph. Could also include the introductory description about hotel? That's more about company, not role. But "About the role" could be the overview paragraph. We'll put that. Thus sections: About the role (overview), Responsibilities, Qualifications, Skills (maybe we can extract skills from qualifications), Benefits. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

  About the role

  Handles all administrative duties required by the Sales and Marketing Divisions in order to provide superior services to our guests.

  Responsibilities

  • Sell and detail wedding blocks (on Manager's behalf)
  • Act as Convention Services contact for smaller group blocks (typically only individual call in, rooms only, no cancellation or attrition blocks to start)
  • Turn over signed sales contracts and distribute them through the proper channels
  • Run and distribute daily reports (such as Change Log & Daily Events) and weekly reports (such as 10 Day BEO Distribution, Cutoff Reports, & Resumes)
  • Take phone inquiries regarding potential group business and all other calls to the sales office (if the manager does not pick up their line within 3 rings, you will answer on their behalf and either assist the guest or transfer them to the manager’s voicemail)
  • General tasks for sales managers and the CS team including setting up amenities/amenity cards, creating and updating reservations in Opera, etc.
  • Answering phone calls and emails from clients (ex. answering general hotel questions, rooming list requests, etc.)
  • Create BEOs for in-house events (ex. ASC events like the bimonthly Koffee Klatch, or departmental OST meetings)
  • Manage the third party reservations inbox (basically just checking the inbox daily and making any new reservations that come through)
  • Coordinating with Housekeeping to get show rooms when sales managers have a site visit
  • Attend meetings such as BEO or staff meeting (if you have groups with resumes or events), and the weekly cutoff report call
  • Conduct site visits for wedding block clients who want to view guest rooms
  • Assist MRC with rebates, commissions, end of month reporting, or pick up reports (on a backup basis)
  • Build wedding room blocks if Group Coordinator is very busy
  • Create Delphi.FDC reports or merge documents
  • Make sales kits

  Qualifications

  • Must be able to work alone as well as work well with others.
  • Must have Associate's Degree or equivalent.
  • Must have good communication skills.
  • Must be extremely computer savvy (Microsoft Word, Publisher, Outlook, Express, Excel).
  • Previous knowledge of Delphi, Opera and Synergy preferred.
  • Must have good organizational skills.
  We could also add Skills section: maybe extract computer skills etc. But we already have them in qualifications. To avoid thin sections, we could combine Qualifications and Skills into one heading "Qualifications". But the instruction allows us to use Skills heading if we have content. Since we have skill items, we could create Skills section separate from Qualifications (like education). However we risk thin sections. But we have enough skill items: computer savvy, communication, organizational, work alone/with others. Could be considered skills. Qualifications could be Associate's Degree or equivalent. But we have both. Better to follow the headings exactly: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Qualifications, Skills, Benefits. We don't have Requirements separate; we could treat Qualifications as Requirements and omit Qualifications? But we have both qualifications and skills content. Let's assign: - Requirements: maybe the "Must have Associate's Degree or equivalent." and "Must be able to work alone as well as work well with others." etc. But that's overlapping. Given the instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section called "Qualifications". But we need to decide. Let's read the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. Then: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include only those headings that have real content. Thus we need to decide what content maps to which heading. We have: - About the role: overview paragraph. - Responsibilities: list. - Qualifications: list of qualifications (education, experience, etc.) - Skills: list of skills (communication, computer savvy, organizational, etc.) - Benefits: benefit package statement. We don't have separate Requirements; but we could treat the qualifications as requirements. However we already have Qualifications heading; we could omit Requirements. Thus final sections: About the role, Responsibilities, Qualifications, Skills, Benefits. We need to ensure we don't include any boilerplate like EEO etc. Now format: each

  then content. For About the role: we could also include a bit more of