Partner Operations Agent
Pursuit · Columbia Falls, MT · 1 mo ago
Full-time
We need to output HTML fragment with headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Intro paragraph about Pursuit and role description: "At Pursuit, we offer more than just a place to visit..." This is about the role? Could be "About the role" or maybe "About Us". The instruction: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Intro paragraph about Pursuit and role description: "At Pursuit, we offer more than just a place to visit..." This is about the role? Could be "About the role" or maybe "About Us". The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits (if present), Pay (if present), Schedule (if present). We need to decide which sections have content.
Let's extract:
About the role: The first paragraph(s) describing the role: "At Pursuit, we offer more than just a place to visit..." then "As a Partner Operations Agent, you will be part of the Global Partner Operations Team..." That's about the role. So we can put that in About the role
with paragraphs.
Responsibilities: There's a "Role & Responsibilities" heading in the posting with bullet list (though not bullet but sentences separated by periods). It lists many duties: Serve as primary point of contact..., Manage reservations..., Perform quality assurance..., Collect, maintain and process payment..., Assist with complaint resolution..., Collaborate with internal departments..., Work diligently to meet..., Assist with other reservation-related projects..., Identify and recommend opportunities... So we can put those as - items.
Qualifications & Experience: There's a "Skills Qualifications & Experience" heading (somewhat combined). It lists qualifications: Previous experience..., Familiarity..., Must be comfortable speaking..., Exceptional attention..., Excellent organizational..., Strong written..., Proven ability..., Self-motivated..., Strong organizational..., Ability to work..., Guest- and partner-focused..., Confidence to challenge..., Comfortable learning..., Demonstrate professionalism..., Must be computer literate... This seems like qualifications/skills. The instruction separates Skills and Qualifications sections. We need to decide what goes where. Usually Qualifications: experience, education, certifications. Skills: abilities. But we can split: Qualifications: Previous experience in reservations, hospitality, tourism, or customer service is preferred. Familiarity with reservation systems, booking engines, and CRM platforms such as Salesforce or Delphi is considered an asset; experience with OPERA PMS is a plus. Must be comfortable speaking with guests and partners on the phone. (maybe skill). Exceptional attention to detail and accuracy. Excellent organizational and time management abilities. Strong written and verbal communication skills in English; proficiency in a second language is an asset. Proven ability to manage high-volume data entry and correspondence with accuracy and efficiency. Self-motivated and proactive, with the ability to work effectively both independently and collaboratively in a team environment. Strong organizational and multitasking skills, with the ability to manage competing priorities in a fast-paced environment. Ability to work independently while collaborating effectively with cross-functional remote teams. Guest- and partner-focused mindset with a commitment to service excellence. Confidence to challenge the status quo and contribute new ideas for improvement. Comfortable learning new systems and troubleshooting technical issues. Demonstrate professionalism, flexibility, and a service-first approach in a fast-paced, dynamic, seasonal environment. Must be computer literate and be able to adapt to different software, including reservations and ticketing systems.
We could put all that under Qualifications (or Skills). The instruction says prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section? But they gave examples of separate headings. However we can decide to have Qualifications and Skills separate if content justifies. Let's see if we can separate: Qualifications: experience, familiarity, language proficiency, etc. Skills: attention to detail, organizational, communication, data entry, self-motivated, multitasking, ability to work independently, guest-focused, confidence to challenge, learning new systems, professionalism, computer literate. There's overlap. Might be better to have one "Qualifications & Skills" section. But the instruction says use headings like Skills, Qualifications etc. It didn't forbid combining but said "Prefer a few substantive sections over many thin ones." So we could have Qualifications and Skills combined into one heading like "Qualifications & Skills". However the examples list them separately; but we can still use a combined heading if it's more substantive. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. It says "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Skills into one section to avoid thin sections. But we need to decide if we have enough content for each separate. Let's see: Qualifications content: "Previous experience in reservations, hospitality, tourism, or customer service is preferred. Familiarity with reservation systems, booking engines, and CRM platforms such as Salesforce or Delphi is considered an asset; experience with OPERA PMS is a plus. Must be comfortable speaking with guests and partners on the phone." That's maybe 3 sentences. Skills content: many bullet-like sentences. That's substantial. So we could have Qualifications (short) and Skills (longer). That's two sections, both substantive enough. We'll do that.
Requirements: Not explicitly separate; maybe the qualifications cover requirements. There's no separate "Requirements" heading. Could we create a Requirements section from things like "Must be computer literate and be able to adapt to different software"? That's more skill. There's no explicit requirements like degree, etc. So we might omit Requirements section.
Benefits: The posting includes "PURSUIT PERKS" with bullet list: Join an inclusive, global team and make life-long connections; Enjoy free access to Pursuit attractions and 50% off for friends; Get discounts on hotel stays, dining, and retail; Access subsidized mental health and wellness resources. That's benefits. So we can have Benefits section.
Pay: Not mentioned. So omit Pay.
Schedule: Not mentioned. So omit Schedule.
Also there is "About Us" section describing company, locations, etc. That could be "About the company" but not in the list. Could we put under "About the role"? Probably not. The instruction only lists those headings; we could add other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they expect only those. The "About Us" could be considered part of "About the role" or maybe we could omit because it's not required? But we must preserve ALL substantive information. The About Us paragraph describes the company, locations, etc. That's substantive. We need to include it somewhere. Could we put it under a heading like "About the company"? Not in list but maybe acceptable. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can add other headings if needed, but better to stick to those. Could we incorporate About Us into About the role? The role description already includes some about Pursuit; but the About Us is more about company. Could we put it under "About the role" as additional paragraphs? That would be mixing but still okay. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding other headings. I'd include an "About the company" heading maybe as About Pursuit
. But the examples didn't list that. Might be okay. However to be safe, we could put the About Us content under a heading "About the role" as it's still about the role context. But the role description already includes some of that; we can just add more paragraphs.
Let's structure:
About the role
At Pursuit, we offer more than just a place to visit, we create opportunities for our guests to truly connect with iconic destinations. Our experiences include world-class attractions and distinctive lodges, all designed to highlight the unique beauty of each location. Beyond that, we offer thoughtfully crafted restaurants, retail, and transportation services that help our guests immerse themselves fully in the experience. What ties it all together are the friendly faces you’ll find along the way, the thoughtful amenities, and the delightful details that make every visit feel personal and unforgettable. As a Partner Operations Agent, you will be part of the Global Partner Operations Team, supporting Travel Trade (Group/FIT) partners across our hospitality, attractions, transportation, and F&B portfolio. As a Partner Operations agent, you'll accurately enter and manage reservations, apply critical thinking to catch and resolve issues, and serve as the key liaison between partners and internal teams; keeping operations seamless and partners confident in every interaction. The ideal candidate is detail-oriented, organized, collaborative, and comfortable adapting to multiple priorities in a fast-paced, seasonal environment. You will bring a service-first mindset, strong communication skills, confidence with reservation systems and high-volume data entry, and take pride in your work.
But note there is repetition: "As a Partner Operations Agent, you will be part of the Global Partner Operations Team..." and then later "As a Partner Operations agent, you'll accurately enter..." We can combine.
Better to rewrite but must preserve all info, not invent or summarize away detail. We can keep the sentences as is, maybe combine into a paragraph.
We'll need to ensure we don't lose any detail.
Let's extract the exact sentences:
From posting:
"At Pursuit, we offer more than just a place to visit, we create opportunities for our guests to truly connect with iconic destinations. Our experiences include world-class attractions and distinctive lodges, all designed to highlight the unique beauty of each location. Beyond that, we offer thoughtfully crafted restaurants, retail, and transportation services that help our guests immerse themselves fully in the experience. What ties it all together are the friendly faces you’ll find along the way, the thoughtful amenities, and the delightful details that make every visit feel personal and unforgettable. As a Partner Operations Agent, you will be part of the Global Partner Operations Team, supporting Travel Trade (Group/FIT) partners across our hospitality, attractions, transportation, and F&B portfolio. As a Partner Operations agent, you'll accurately enter and manage reservations, apply critical thinking to catch and resolve issues, and serve as the key liaison between partners and internal teams; keeping operations seamless and partners confident in every interaction. The ideal candidate is detail-oriented, organized, collaborative, and comfortable adapting to multiple priorities in a fast-paced, seasonal environment. You will bring a service-first mindset, strong communication skills, confidence with reservation systems and high-volume data entry, and take pride in your work."
We'll keep that as paragraph(s). Could split into two paragraphs for readability but not required.
Now Responsibilities: list each duty as - .
Duties:
- Serve as the primary point of contact for travel trade and MICE partners via phone and email.
- Manage reservations, including inventory, from initial inquiry to final touchpoint for your assigned revenue discipline (lodging, attractions, transportation and food & beverage).
- Perform quality assurance checks on reservations to maintain accuracy and partner satisfaction.
- Collect, maintain and process payment within reservation systems.
- Assist with complaint resolution promptly and professionally; knowing when to escalate if necessary.
- Collaborate with internal departments, including onsite operations teams, to ensure smooth execution of partner requirements.
- Work diligently to meet and exceed Pursuit Service Standard Level agreements and personal KPI’s.
- Assist with other reservation-related projects and administrative duties
About the role
with paragraphs. Responsibilities: There's a "Role & Responsibilities" heading in the posting with bullet list (though not bullet but sentences separated by periods). It lists many duties: Serve as primary point of contact..., Manage reservations..., Perform quality assurance..., Collect, maintain and process payment..., Assist with complaint resolution..., Collaborate with internal departments..., Work diligently to meet..., Assist with other reservation-related projects..., Identify and recommend opportunities... So we can put those as- items.
Qualifications & Experience: There's a "Skills Qualifications & Experience" heading (somewhat combined). It lists qualifications: Previous experience..., Familiarity..., Must be comfortable speaking..., Exceptional attention..., Excellent organizational..., Strong written..., Proven ability..., Self-motivated..., Strong organizational..., Ability to work..., Guest- and partner-focused..., Confidence to challenge..., Comfortable learning..., Demonstrate professionalism..., Must be computer literate... This seems like qualifications/skills. The instruction separates Skills and Qualifications sections. We need to decide what goes where. Usually Qualifications: experience, education, certifications. Skills: abilities. But we can split: Qualifications: Previous experience in reservations, hospitality, tourism, or customer service is preferred. Familiarity with reservation systems, booking engines, and CRM platforms such as Salesforce or Delphi is considered an asset; experience with OPERA PMS is a plus. Must be comfortable speaking with guests and partners on the phone. (maybe skill). Exceptional attention to detail and accuracy. Excellent organizational and time management abilities. Strong written and verbal communication skills in English; proficiency in a second language is an asset. Proven ability to manage high-volume data entry and correspondence with accuracy and efficiency. Self-motivated and proactive, with the ability to work effectively both independently and collaboratively in a team environment. Strong organizational and multitasking skills, with the ability to manage competing priorities in a fast-paced environment. Ability to work independently while collaborating effectively with cross-functional remote teams. Guest- and partner-focused mindset with a commitment to service excellence. Confidence to challenge the status quo and contribute new ideas for improvement. Comfortable learning new systems and troubleshooting technical issues. Demonstrate professionalism, flexibility, and a service-first approach in a fast-paced, dynamic, seasonal environment. Must be computer literate and be able to adapt to different software, including reservations and ticketing systems.
We could put all that under Qualifications (or Skills). The instruction says prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section? But they gave examples of separate headings. However we can decide to have Qualifications and Skills separate if content justifies. Let's see if we can separate: Qualifications: experience, familiarity, language proficiency, etc. Skills: attention to detail, organizational, communication, data entry, self-motivated, multitasking, ability to work independently, guest-focused, confidence to challenge, learning new systems, professionalism, computer literate. There's overlap. Might be better to have one "Qualifications & Skills" section. But the instruction says use headings like Skills, Qualifications etc. It didn't forbid combining but said "Prefer a few substantive sections over many thin ones." So we could have Qualifications and Skills combined into one heading like "Qualifications & Skills". However the examples list them separately; but we can still use a combined heading if it's more substantive. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. It says "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Skills into one section to avoid thin sections. But we need to decide if we have enough content for each separate. Let's see: Qualifications content: "Previous experience in reservations, hospitality, tourism, or customer service is preferred. Familiarity with reservation systems, booking engines, and CRM platforms such as Salesforce or Delphi is considered an asset; experience with OPERA PMS is a plus. Must be comfortable speaking with guests and partners on the phone." That's maybe 3 sentences. Skills content: many bullet-like sentences. That's substantial. So we could have Qualifications (short) and Skills (longer). That's two sections, both substantive enough. We'll do that. Requirements: Not explicitly separate; maybe the qualifications cover requirements. There's no separate "Requirements" heading. Could we create a Requirements section from things like "Must be computer literate and be able to adapt to different software"? That's more skill. There's no explicit requirements like degree, etc. So we might omit Requirements section. Benefits: The posting includes "PURSUIT PERKS" with bullet list: Join an inclusive, global team and make life-long connections; Enjoy free access to Pursuit attractions and 50% off for friends; Get discounts on hotel stays, dining, and retail; Access subsidized mental health and wellness resources. That's benefits. So we can have Benefits section. Pay: Not mentioned. So omit Pay. Schedule: Not mentioned. So omit Schedule. Also there is "About Us" section describing company, locations, etc. That could be "About the company" but not in the list. Could we put under "About the role"? Probably not. The instruction only lists those headings; we could add other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they expect only those. The "About Us" could be considered part of "About the role" or maybe we could omit because it's not required? But we must preserve ALL substantive information. The About Us paragraph describes the company, locations, etc. That's substantive. We need to include it somewhere. Could we put it under a heading like "About the company"? Not in list but maybe acceptable. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can add other headings if needed, but better to stick to those. Could we incorporate About Us into About the role? The role description already includes some about Pursuit; but the About Us is more about company. Could we put it under "About the role" as additional paragraphs? That would be mixing but still okay. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding other headings. I'd include an "About the company" heading maybe as
About Pursuit
. But the examples didn't list that. Might be okay. However to be safe, we could put the About Us content under a heading "About the role" as it's still about the role context. But the role description already includes some of that; we can just add more paragraphs. Let's structure:About the role
At Pursuit, we offer more than just a place to visit, we create opportunities for our guests to truly connect with iconic destinations. Our experiences include world-class attractions and distinctive lodges, all designed to highlight the unique beauty of each location. Beyond that, we offer thoughtfully crafted restaurants, retail, and transportation services that help our guests immerse themselves fully in the experience. What ties it all together are the friendly faces you’ll find along the way, the thoughtful amenities, and the delightful details that make every visit feel personal and unforgettable. As a Partner Operations Agent, you will be part of the Global Partner Operations Team, supporting Travel Trade (Group/FIT) partners across our hospitality, attractions, transportation, and F&B portfolio. As a Partner Operations agent, you'll accurately enter and manage reservations, apply critical thinking to catch and resolve issues, and serve as the key liaison between partners and internal teams; keeping operations seamless and partners confident in every interaction. The ideal candidate is detail-oriented, organized, collaborative, and comfortable adapting to multiple priorities in a fast-paced, seasonal environment. You will bring a service-first mindset, strong communication skills, confidence with reservation systems and high-volume data entry, and take pride in your work.
But note there is repetition: "As a Partner Operations Agent, you will be part of the Global Partner Operations Team..." and then later "As a Partner Operations agent, you'll accurately enter..." We can combine. Better to rewrite but must preserve all info, not invent or summarize away detail. We can keep the sentences as is, maybe combine into a paragraph. We'll need to ensure we don't lose any detail. Let's extract the exact sentences: From posting: "At Pursuit, we offer more than just a place to visit, we create opportunities for our guests to truly connect with iconic destinations. Our experiences include world-class attractions and distinctive lodges, all designed to highlight the unique beauty of each location. Beyond that, we offer thoughtfully crafted restaurants, retail, and transportation services that help our guests immerse themselves fully in the experience. What ties it all together are the friendly faces you’ll find along the way, the thoughtful amenities, and the delightful details that make every visit feel personal and unforgettable. As a Partner Operations Agent, you will be part of the Global Partner Operations Team, supporting Travel Trade (Group/FIT) partners across our hospitality, attractions, transportation, and F&B portfolio. As a Partner Operations agent, you'll accurately enter and manage reservations, apply critical thinking to catch and resolve issues, and serve as the key liaison between partners and internal teams; keeping operations seamless and partners confident in every interaction. The ideal candidate is detail-oriented, organized, collaborative, and comfortable adapting to multiple priorities in a fast-paced, seasonal environment. You will bring a service-first mindset, strong communication skills, confidence with reservation systems and high-volume data entry, and take pride in your work." We'll keep that as paragraph(s). Could split into two paragraphs for readability but not required. Now Responsibilities: list each duty as - . Duties: - Serve as the primary point of contact for travel trade and MICE partners via phone and email. - Manage reservations, including inventory, from initial inquiry to final touchpoint for your assigned revenue discipline (lodging, attractions, transportation and food & beverage). - Perform quality assurance checks on reservations to maintain accuracy and partner satisfaction. - Collect, maintain and process payment within reservation systems. - Assist with complaint resolution promptly and professionally; knowing when to escalate if necessary. - Collaborate with internal departments, including onsite operations teams, to ensure smooth execution of partner requirements. - Work diligently to meet and exceed Pursuit Service Standard Level agreements and personal KPI’s. - Assist with other reservation-related projects and administrative duties