Guest Service Agent
for section headings. Do not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive info.
We need to decide which sections to include: Only if posting has real specific content. The sections we can map:
- About the role: maybe the first paragraph describing duties? Could be "Opportunity: Guest Service Agent Greet, register and service guests..." That's description of role. Could be under About the role
with
. - Responsibilities: Could be the list under "Your Focus" (list of duties). Use
- .
- Requirements/Qualifications/Skills: "Your Background And Skills" includes High School diploma, previous customer service experience, knowledge of PMS systems. Could be under
Requirements
orSkills
. We need to decide. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate ones. We have Benefits listed. So we can have Benefits section. - Pay: Not specified (competitive wages). The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Competitive wages for full time and part time opportunities" - that's a statement about wages but not specific numbers. Is that enough to include Pay? It says "competitive wages". That's still stating they offer competitive wages. It's not a specific number but it's a statement. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive wages". So we could include Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might combine Pay with Benefits? But Benefits already separate. Could include Pay as a shortinside Benefits? But they said use heading for Benefits. Could have Benefits heading and include the competitive wages inside that
- maybe. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create Benefits section (they state benefits). Pay section maybe optional but we can include if we want. However they say prefer few substantive sections over many thin ones. So maybe we combine Pay into Benefits? But they said use heading Benefits for benefits. Pay is separate concept. Could we omit Pay section because it's not specific? The phrase "competitive wages" is vague but still a statement about pay. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive wages, so we could include Pay. But we risk creating a thin section. However we could include Pay as a
- for lists.
Let's craft HTML.
We need to output only HTML fragment, no /, no markdown.
We'll start with
About the role
thencontaining the description: "Greet, register and service guests in a friendly and courteous manner according to hotel/brand and sustainability standards." plus values and work environment. We need to include all substantive info from that section: The "Opportunity: Guest Service Agent Greet, register and service guests..." plus "Your Growth Path" maybe? Actually "Your Growth Path Front Desk Supervisor or Sales Coordinator – Front Office Manager or Sales Manager" is about career progression. That's also substantive. Should we include? It's under "Your Growth Path". That's not a duty but info about growth. Could be included in About the role as a sentence. Also "Your Focus" list is responsibilities; we already have that. Thus About the role paragraph should include: greeting, register, service guests per standards; growth path: Front Desk Supervisor or Sales Coordinator – Front Office Manager or Sales Manager; values: People Are Our Capability – Hearts That Serve – Only Excellence – Stay Nimble - Own It; work environment: physical demands (standing, walking, pushing, lifting up to 25 pounds, bending and reaching; stooping, kneeling, or crouching). Also maybe mention "Assist in the breakfast area or assist guests with luggage when staffing assistance is required or during peak periods." That's a duty, but could be in responsibilities. We need to ensure we don't duplicate. Let's extract all bullet points from "Your Focus": - Immediately greet guests and offer to assist with their needs. - Register and assign guests to hotel rooms. - Establish methods of payment and verify credit. - Make and confirm reservations. - Compute bills, collect payments, and make change for guests. - Transmit and receive messages, using telephones or the PMS system. - Respond to guest requests in a timely manner. - Receive and resolve guest complaints, elevating to supervisor if necessary. - Secure guests' valuables in hotel safe or safe-deposit boxes, if not available in guest rooms. - Perform bookkeeping activities, such as balancing accounts and conducting audits. - Be aware of guest satisfaction scores and work toward increasing departmental and overall guest satisfaction. - Practice safe work habits, wear protective safety equipment and follow MSDS and OSHA standards. - Assist in the breakfast area or assist guests with luggage when staffing assistance is required or during peak periods. - Ensure overall guest satisfaction. - Perform other duties as requested by management. We'll put these in
- .
Now "Your Background And Skills":
- High School diploma or equivalent preferred.
- Previous customer service experience or equivalent training required.
- Knowledge of PMS systems preferred.
We'll put in
- under Requirements.
Benefits list:
- Competitive wages for full time and part time opportunities
- Medical, Dental and Vision Health Insurance
- Paid Time Off
- 401k Company Match
- Daily Pay
- Free Basic Life Insurance
- 24/7 access to TELUS Health, a confidential work-life resource.
- Travel Discounts
- Commuter Transit and Commuter Parking Benefits
- Employee Assistance and Wellness Program
- Educational/Professional Development
- Referral Bonus Program
We'll put in
- under Benefits.
Schedule: "Work schedule varies and may include working on holidays, weekends and alternate shifts." We'll put in
under Schedule heading. Now About the role paragraph: Let's compose: "Greet, register and service guests in a friendly and courteous manner according to hotel/brand and sustainability standards. Career growth opportunities include advancement to Front Desk Supervisor, Sales Coordinator, Front Office Manager, or Sales Manager. The company values are: People Are Our Capability – Hearts That Serve – Only Excellence – Stay Nimble - Own It. Work environment requires standing for extended periods, walking, pushing, lifting up to 25 pounds, bending and reaching; stooping, kneeling, or crouching." We should also mention "Assist in the breakfast area or assist guests with luggage when staffing assistance is required or during peak periods." That's a duty but we already have in responsibilities; we can keep it there. Now ensure we didn't miss any substantive info: "Your Growth Path" we captured. "Your Focus" we captured as list. "Your Background And Skills" captured. "HHM Hotels Benefits And Perks" captured. "Work Environment and Context" captured physical demands. "What We Believe" captured values. Good. Now we need to output HTML with headings
and appropriate
or
- .
We must not include any extra text like explanations.
Let's craft:
About the role
Greet, register and service
- under Benefits.
Schedule: "Work schedule varies and may include working on holidays, weekends and alternate shifts." We'll put in
- under Requirements.
Benefits list:
- Competitive wages for full time and part time opportunities
- Medical, Dental and Vision Health Insurance
- Paid Time Off
- 401k Company Match
- Daily Pay
- Free Basic Life Insurance
- 24/7 access to TELUS Health, a confidential work-life resource.
- Travel Discounts
- Commuter Transit and Commuter Parking Benefits
- Employee Assistance and Wellness Program
- Educational/Professional Development
- Referral Bonus Program
We'll put in
- .
Now "Your Background And Skills":
- High School diploma or equivalent preferred.
- Previous customer service experience or equivalent training required.
- Knowledge of PMS systems preferred.
We'll put in
inside Benefits? Not following heading rule. Better to have Pay heading with a
stating competitive wages. That's still a section. Schedule: They state "Work schedule varies and may include working on holidays, weekends and alternate shifts." That's schedule info. So we can include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule, Work Environment and Context? Actually Work Environment and Context could be under Schedule? But we have separate schedule. Work Environment includes physical demands. Could be under "Work Environment". Not in the list of headings but we could still use heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could still use other headings if needed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. Work Environment and Context could be folded into Schedule or maybe omitted? But we must preserve ALL substantive information. So we need to include physical demands etc. Could be placed under Schedule? Not ideal. Could be under Responsibilities? Not really. Could be under Requirements? Not really. Could be under About the role? Could add a paragraph about work environment. But maybe we can create a heading "Work Environment" even though not in examples? The instruction says use
for section headings (e.g. ...). The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed, but they gave examples. Safer to stick to those examples. However we need to preserve all info; we could put physical demands under Schedule? Not accurate. Could put under Responsibilities? Not accurate. Could put under About the role as a paragraph describing work environment. That might be acceptable. Thus sections: - About the role: introductory paragraph describing greeting, registering, servicing guests per standards. - Responsibilities: list of duties from "Your Focus". - Requirements: list from "Your Background And Skills": High School diploma or equivalent preferred, previous customer service experience or equivalent training required, knowledge of PMS systems preferred. - Benefits: list from "HHM Hotels Benefits And Perks": Competitive wages for full time and part time opportunities, Medical, Dental and Vision Health Insurance, Paid Time Off, 401k Company Match, Daily Pay, Free Basic Life Insurance, 24/7 access to TELUS Health, Travel Discounts, Commuter Transit and Commuter Parking Benefits, Employee Assistance and Wellness Program, Educational/Professional Development, Referral Bonus Program. - Pay: maybe we already included competitive wages in Benefits; but we could separate Pay: "Competitive wages for full time and part time opportunities". However that duplicates. Could we avoid duplication? The instruction says preserve ALL substantive information; not to invent or summarize away detail. If we put competitive wages only in Benefits, we still preserve it. So we may not need separate Pay heading. But we need to decide if we need Pay heading. Since we already have competitive wages in Benefits, we can omit Pay heading to avoid thin section. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Pay. - Schedule: "Work schedule varies and may include working on holidays, weekends and alternate shifts." We also have "What We Believe" section: "People Are Our Capability – Hearts That Serve – Only Excellence – Stay Nimble - Own It". That's a values statement. Could be under About the role? Or maybe we could create a heading "Values" but not in examples. Could fold into About the role as a paragraph. That would preserve. Work Environment and Context: physical demands etc. Could be folded into Schedule? Not ideal. Could be folded into About the role as a paragraph about work environment. That would preserve. Thus final sections: About the role (includes intro description, values, work environment), Responsibilities (list), Requirements (list), Benefits (list), Schedule (list? just a paragraph). Use
- for lists.
Let's craft HTML.
We need to output only HTML fragment, no /, no markdown.
We'll start with