Area Reservation Sales Supervisor
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. Company description: not needed? It's part of description but not a section heading. We can include maybe as a
before sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones."
Thus we need to extract sections: About the role (maybe from Job Description?), Responsibilities (list of duties), Requirements/Qualifications (list), Skills (maybe separate?), Benefits (if any), Pay (if any), Schedule (if any). The posting includes: "Must be willing to work a flexible schedule, including weekends, and holidays." That's schedule info. Also "PLEASE NOTE: This is a remote position. Must live in the following states to be considered: CT, FL, KY, ME, MD, MA, NJ, NM, NY, OH, PA, RI, SC, UT, TN". That's location requirement, maybe part of Qualifications.
Benefits: Not mentioned. Pay: Not mentioned. So we should not create Benefits or Pay sections.
We have "About the role" maybe from the job description paragraph? The job description includes many duties. Could treat that as Responsibilities.
We also have Qualifications section: list of qualifications.
We could also have Skills: maybe combine with Qualifications? But we can separate if there is distinct skills list. The qualifications list includes many skill-like items: Strong computer skills, ability to work..., etc. Could treat as Skills.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one "Requirements" section. However instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide based on content.
The posting has a "Qualifications" heading explicitly: "Qualifications Strong computer skills, including Opera, Revinate, HMS, Synxis, Google & Microsoft Suites....". So we should create a
Qualifications
and list items.
Also there is a "Job Description" section with duties. Could treat as Responsibilities.
Also there is "Additional Information About Auberge Collection" and "About The Friedkin Group" etc. Those are boilerplate? They are company info but maybe not needed. The instruction says remove legal/EEO boilerplate, duplicated lines, and application instructions. The "Additional Information About Auberge Collection" and "About The Friedkin Group" are not EEO but are company description. Might be considered substantive? It describes the company. Could be included as a brief maybe under "About the role" or separate "About the company". But headings list does not include About the company. Could just include as a
before sections.
We need to preserve all substantive information. So we should keep the company description (first paragraph) maybe as a
before sections.
Also the "Follow White Barn Inn on Facebook and Instagram @WhiteBarnAuberge" is maybe social media, could be considered minor metadata; we could drop or include as short
. Probably drop as not essential.
We need to output only HTML fragment.
Let's structure:
Company description paragraph(s).
About the role
maybe not needed if we have Responsibilities. But we could include a brief summary: The role is Reservations Agent? Actually job title not given but likely Reservations Agent. We could omit About the role if we have Responsibilities.
Better to follow typical pattern: About the role (short paragraph), Responsibilities (list), Qualifications (list). We'll include About the role as a short paragraph summarizing the role: handling calls, emails, quotes, revenue goals, etc. But we must not invent details; we can derive from responsibilities.
But we could just make About the role be the first paragraph of job description before the list. However the job description is a list of duties; there is no separate prose. So we could create About the role as a short paragraph summarizing the role: "The Reservations Agent handles incoming calls, manages email inquiries, processes reservations, meets revenue targets, and collaborates with teams to ensure guest satisfaction." This is derived but not invented? It's a summary; risk of summarizing away detail. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should not create a summary that omits details. Better to not have About the role if we don't have a distinct prose section. Instead we can put the duties under Responsibilities as a list.
Thus we will have:
Responsibilities
- ...
...
Qualifications
- ...
...
We also have schedule info: "Must be willing to work a flexible schedule, including weekends, and holidays." That could be placed under Responsibilities or Qualifications? It's a requirement about schedule. Could be a separate Schedule
but instruction says only create Schedule section if posting actually states them. It does state schedule requirement. So we can include a Schedule section with that statement.
But we also have location requirement: "Must live in the following states to be considered: CT, FL, KY, ME, MD, MA, NJ, NM, NY, OH, PA, RI, SC, UT, TN". That's also a requirement; could be part of Qualifications.
Thus we will have:
Responsibilities
(list of duties)
Qualifications
(list of skills, experience, location, schedule maybe separate)
Schedule
(flexible schedule including weekends and holidays)
We should not create Benefits or Pay.
Now we need to extract the duties list from the job description.
Job Description text:
"Answer all incoming calls in less than three rings in a professional and friendly demeanor following Auberge Collection call quality and brand standards.
Supports the team’s shared Email Inboxes by sending professional, customized quotes for guests and following up to ensure bookings are curated appropriately.
Achieves & exceeds monthly individual & team conversion and revenue goals.
Ensures Hub occupancy coverage to maintain a call abandonment of 4% or less.
Resolve guest challenges and special requests in a timely manner by coordinating efforts with other departments and Reservations Leadership.
Pursues outbound revenue opportunities through our lead management system.
Stays up to date with all communication and hotel information
Ensures that appropriate guest follow-up takes place in a timely and proper fashion.
Provides detailed notes and comments in the lead management system and PMS regarding guest requests to ensure a quality guest experience.
Maintains rate integrity under revenue management strategies, also with Agents.
Collaborates with Leisure Sales Specialist in responding to Leisure inquiries in their absence and shared oversight of the Email Inboxes.
Assists with manual entry of VIP and Marketing reservations as needed.
Completes month-end and Deposit Ledger reconciliations as needed.
Strives to maintain a standard of 80% or higher on shop calls as well as instill best practices and learnings with the team of Reservation Agents.
Assists in maximizing hotel room revenue and occupancy numbers.
Participates in reservations sales training, familiarization trips to all hotels as scheduled.
Participates in department meetings as scheduled.
Oversees daily tasks and participates on the completion of the Reservations Checklist.
Must be willing to work a flexible schedule, including weekends, and holidays.
Must be a cultural ambassador and participate positively in a sales team environment.
All other duties as assigned by Reservations Leadership."
We need to turn each line into - . Some lines have multiple sentences; we keep as is.
Now Qualifications:
"Strong computer skills, including Opera, Revinate, HMS, Synxis, Google & Microsoft Suites.
Ability to work midweek, weekends, and holidays with the ability to thrive and succeed in a fast-paced, demanding work environment, and flexibility to changes in direction, routine, and scheduling.
Preferably two years in a hospitality or reservations position at a luxury resort.
Ability to work cohesively with other departments and co-workers as part of a team, as a team player, and receive assignments from different leaders.
Ability to ascertain the caller's needs and comply to ensure caller's satisfaction.
Ability to process written requests for all manner of reservations.
Ability to maintain discretion and confidentiality of all guest and resort information.
Ability to be well organized, maintain concentration, think clearly, and follow up while handling multiple tasks.
Ability to focus attention on details, remain calm under pressure, and process requests quickly and accurately.
Strong verbal and written communication skills.
Ability to work in a remote environment with a quiet, dedicated space, free of distractions, and access to high-speed internet.
PLEASE NOTE: This is a remote position. Must live in the following states to be considered: CT, FL, KY, ME, MD, MA, NJ, NM, NY, OH, PA, RI, SC, UT, TN"
We need to treat the "PLEASE NOTE:" line as part of qualifications (location requirement). Could be separate but we can include as a
- .
Now Schedule: "Must be willing to work a flexible schedule, including weekends, and holidays." This appears also in Qualifications list (second bullet). But we also have it as a separate line in Responsibilities (near end). To avoid duplication, we should include it only once. The instruction says remove duplicated lines. So we need to deduplicate. The schedule line appears both in Responsibilities (near end) and in Qualifications (second bullet). We should keep only one occurrence. Where to place? Probably under Qualifications as it's a requirement. But we also have a separate Schedule section; we could keep schedule line there and remove from Qualifications. However the Qualifications bullet also includes other aspects: ability to work midweek, weekends, holidays with ability to thrive in fast-paced environment, flexibility to changes. That's more than just schedule. So we could keep that bullet but remove the schedule phrase? That would be editing content. Better to keep the bullet as is, and not create a separate Schedule section, because the schedule info is already present in Qualifications. The instruction says only create Schedule section if posting actually states them. It does state schedule, but we already have it in Qualifications; we could still create a Schedule section but would duplicate. To avoid duplication, we could either not create Schedule section and keep schedule within Qualifications, or we could create Schedule section and remove the schedule phrase from Qualifications (but that would be altering content). Safer to not create Schedule section and keep schedule within Qualifications.
Thus we will have only Responsibilities and Qualifications sections.
Now we need to include company description as a
before sections.
Company Description paragraph(s):
"Company Description A beloved local landmark for over 150 years, White Barn Inn, Auberge Collection is synonymous with warm New England hospitality, rustic charm, and uncompromising attention to detail. Just a 90-minute drive north of Boston in the charming coastal town of Kennebunk, Maine, the 28-room property is renowned as one of the country’s most distinctive getaways offering supreme levels of quality, luxury, and gracious service. The hotel's four waterfront
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones." Thus we need to extract sections: About the role (maybe from Job Description?), Responsibilities (list of duties), Requirements/Qualifications (list), Skills (maybe separate?), Benefits (if any), Pay (if any), Schedule (if any). The posting includes: "Must be willing to work a flexible schedule, including weekends, and holidays." That's schedule info. Also "PLEASE NOTE: This is a remote position. Must live in the following states to be considered: CT, FL, KY, ME, MD, MA, NJ, NM, NY, OH, PA, RI, SC, UT, TN". That's location requirement, maybe part of Qualifications. Benefits: Not mentioned. Pay: Not mentioned. So we should not create Benefits or Pay sections. We have "About the role" maybe from the job description paragraph? The job description includes many duties. Could treat that as Responsibilities. We also have Qualifications section: list of qualifications. We could also have Skills: maybe combine with Qualifications? But we can separate if there is distinct skills list. The qualifications list includes many skill-like items: Strong computer skills, ability to work..., etc. Could treat as Skills. But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one "Requirements" section. However instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide based on content. The posting has a "Qualifications" heading explicitly: "Qualifications Strong computer skills, including Opera, Revinate, HMS, Synxis, Google & Microsoft Suites....". So we should create a
Qualifications
and list items. Also there is a "Job Description" section with duties. Could treat as Responsibilities. Also there is "Additional Information About Auberge Collection" and "About The Friedkin Group" etc. Those are boilerplate? They are company info but maybe not needed. The instruction says remove legal/EEO boilerplate, duplicated lines, and application instructions. The "Additional Information About Auberge Collection" and "About The Friedkin Group" are not EEO but are company description. Might be considered substantive? It describes the company. Could be included as a briefmaybe under "About the role" or separate "About the company". But headings list does not include About the company. Could just include as a
before sections. We need to preserve all substantive information. So we should keep the company description (first paragraph) maybe as a
before sections. Also the "Follow White Barn Inn on Facebook and Instagram @WhiteBarnAuberge" is maybe social media, could be considered minor metadata; we could drop or include as short
. Probably drop as not essential. We need to output only HTML fragment. Let's structure:
Company description paragraph(s).
About the role
maybe not needed if we have Responsibilities. But we could include a brief summary: The role is Reservations Agent? Actually job title not given but likely Reservations Agent. We could omit About the role if we have Responsibilities. Better to follow typical pattern: About the role (short paragraph), Responsibilities (list), Qualifications (list). We'll include About the role as a short paragraph summarizing the role: handling calls, emails, quotes, revenue goals, etc. But we must not invent details; we can derive from responsibilities. But we could just make About the role be the first paragraph of job description before the list. However the job description is a list of duties; there is no separate prose. So we could create About the role as a short paragraph summarizing the role: "The Reservations Agent handles incoming calls, manages email inquiries, processes reservations, meets revenue targets, and collaborates with teams to ensure guest satisfaction." This is derived but not invented? It's a summary; risk of summarizing away detail. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should not create a summary that omits details. Better to not have About the role if we don't have a distinct prose section. Instead we can put the duties under Responsibilities as a list. Thus we will have:Responsibilities
- ... ...
Qualifications
- ... ...
Schedule
but instruction says only create Schedule section if posting actually states them. It does state schedule requirement. So we can include a Schedule section with that statement. But we also have location requirement: "Must live in the following states to be considered: CT, FL, KY, ME, MD, MA, NJ, NM, NY, OH, PA, RI, SC, UT, TN". That's also a requirement; could be part of Qualifications. Thus we will have:Responsibilities
(list of duties)Qualifications
(list of skills, experience, location, schedule maybe separate)Schedule
(flexible schedule including weekends and holidays) We should not create Benefits or Pay. Now we need to extract the duties list from the job description. Job Description text: "Answer all incoming calls in less than three rings in a professional and friendly demeanor following Auberge Collection call quality and brand standards. Supports the team’s shared Email Inboxes by sending professional, customized quotes for guests and following up to ensure bookings are curated appropriately. Achieves & exceeds monthly individual & team conversion and revenue goals. Ensures Hub occupancy coverage to maintain a call abandonment of 4% or less. Resolve guest challenges and special requests in a timely manner by coordinating efforts with other departments and Reservations Leadership. Pursues outbound revenue opportunities through our lead management system. Stays up to date with all communication and hotel information Ensures that appropriate guest follow-up takes place in a timely and proper fashion. Provides detailed notes and comments in the lead management system and PMS regarding guest requests to ensure a quality guest experience. Maintains rate integrity under revenue management strategies, also with Agents. Collaborates with Leisure Sales Specialist in responding to Leisure inquiries in their absence and shared oversight of the Email Inboxes. Assists with manual entry of VIP and Marketing reservations as needed. Completes month-end and Deposit Ledger reconciliations as needed. Strives to maintain a standard of 80% or higher on shop calls as well as instill best practices and learnings with the team of Reservation Agents. Assists in maximizing hotel room revenue and occupancy numbers. Participates in reservations sales training, familiarization trips to all hotels as scheduled. Participates in department meetings as scheduled. Oversees daily tasks and participates on the completion of the Reservations Checklist. Must be willing to work a flexible schedule, including weekends, and holidays. Must be a cultural ambassador and participate positively in a sales team environment. All other duties as assigned by Reservations Leadership." We need to turn each line intobefore sections. Company Description paragraph(s): "Company Description A beloved local landmark for over 150 years, White Barn Inn, Auberge Collection is synonymous with warm New England hospitality, rustic charm, and uncompromising attention to detail. Just a 90-minute drive north of Boston in the charming coastal town of Kennebunk, Maine, the 28-room property is renowned as one of the country’s most distinctive getaways offering supreme levels of quality, luxury, and gracious service. The hotel's four waterfront