Hearing Ambassador (Patient Care Coordinator)
NationsBenefits · Flagstaff, AZ · 1 mo ago
HealthcareFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes: description about company (maybe About the role? Actually "About the role" could be the paragraph describing role? The posting includes a description of role: "Role: The Hearing Ambassador assists...". That's role description. Could be "About the role". Also responsibilities list. Requirements list. No explicit Benefits, Pay, Schedule. So we should not include those sections. Also maybe "Qualifications" could be same as Requirements? But we have Requirements section. Could also include "Skills" if there are skill mentions. The posting includes skills: strong customer service, sales, retail experience, experience with PC hardware/software, excellent oral/written communication, organizational, problem-solving, presentation skills, previous experience with appointment scheduling, proficiency with basic computer systems and scheduling software. Those could go under Skills. But we already have Requirements covering many of those. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for About the role (role description), Responsibilities (list), Requirements (list), Skills (list). Could also have Qualifications but that may duplicate Requirements. Better to separate: Requirements for education/experience, Skills for abilities. Let's parse.
About the role: paragraph describing role: "The Hearing Ambassador assists and helps the licensed dispenser meet their goals and fulfill their daily duties. This role is responsible for engaging customers, Support hearing health needs, educating individuals about hearing wellness, scheduling appointments, and supporting growth through community outreach and customer relationship building."
Responsibilities: bullet list given.
Requirements: bullet list given (high school diploma, experience, etc.)
Skills: maybe extract from requirements: strong customer service, sales, or retail experience; experience working with PC hardware and software including general computer and Internet knowledge; excellent oral and written communication skills, organizational, problem-solving/troubleshooting skills, and presentation skills; previous experience with patient/customer appointment scheduling; proficiency with basic computer systems and scheduling software.
We could also include "Qualifications" but not needed.
We must not repeat job title as heading. The job title is "Hearing Ambassador". Not to be used as heading.
We must not include Job ID etc.
We must remove boilerplate: The initial paragraph about NationsBenefits is company description; maybe that belongs to "About the company"? Not a heading we have. Could be part of About the role? Probably not. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not include a generic "About the company" heading unless we map to About the role? The company description is not about the role. But we could include it as part of About the role? Might be considered filler. However we need to preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive but not about the role. There's no heading for company overview. Could we put it under About the role? That would be inaccurate. Perhaps we can include a section "About the company" but not in allowed headings list? The instruction says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes: description about company (maybe About the role? Actually "About the role" could be the paragraph describing role? The posting includes a description of role: "Role: The Hearing Ambassador assists...". That's role description. Could be "About the role". Also responsibilities list. Requirements list. No explicit Benefits, Pay, Schedule. So we should not include those sections. Also maybe "Qualifications" could be same as Requirements? But we have Requirements section. Could also include "Skills" if there are skill mentions. The posting includes skills: strong customer service, sales, retail experience, experience with PC hardware/software, excellent oral/written communication, organizational, problem-solving, presentation skills, previous experience with appointment scheduling, proficiency with basic computer systems and scheduling software. Those could go under Skills. But we already have Requirements covering many of those. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for About the role (role description), Responsibilities (list), Requirements (list), Skills (list). Could also have Qualifications but that may duplicate Requirements. Better to separate: Requirements for education/experience, Skills for abilities. Let's parse.
About the role: paragraph describing role: "The Hearing Ambassador assists and helps the licensed dispenser meet their goals and fulfill their daily duties. This role is responsible for engaging customers, Support hearing health needs, educating individuals about hearing wellness, scheduling appointments, and supporting growth through community outreach and customer relationship building."
Responsibilities: bullet list given.
Requirements: bullet list given (high school diploma, experience, etc.)
Skills: maybe extract from requirements: strong customer service, sales, or retail experience; experience working with PC hardware and software including general computer and Internet knowledge; excellent oral and written communication skills, organizational, problem-solving/troubleshooting skills, and presentation skills; previous experience with patient/customer appointment scheduling; proficiency with basic computer systems and scheduling software.
We could also include "Qualifications" but not needed.
We must not repeat job title as heading. The job title is "Hearing Ambassador". Not to be used as heading.
We must not include Job ID etc.
We must remove boilerplate: The initial paragraph about NationsBenefits is company description; maybe that belongs to "About the company"? Not a heading we have. Could be part of About the role? Probably not. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not include a generic "About the company" heading unless we map to About the role? The company description is not about the role. But we could include it as part of About the role? Might be considered filler. However we need to preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive but not about the role. There's no heading for company overview. Could we put it under About the role? That would be inaccurate. Perhaps we can include a section "About the company" but not in allowed headings list? 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? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should fit company description somewhere, maybe as a paragraph before any heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid having a leading paragraph without heading. So we can include a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should fit company description somewhere, maybe as a paragraph before any heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid having a leading paragraph without heading. So we can include a
with company overview before sections. Thus structure:
NationsBenefits is recognized as one of the fastest-growing companies in America and a Healthcare Fintech provider of supplemental benefits, flex cards, and member engagement solutions. ... (the company description).
ThenAbout the role
with paragraph describing role. ThenResponsibilities
with- ... each bullet.
Then
Requirements
with- ... each bullet.
Then
Skills
with- ... each bullet.
We must not include Benefits, Pay, Schedule sections.
Check for any duplicated lines: The responsibilities list includes many items. We'll copy them exactly.
Responsibilities bullets:
- Have a working knowledge of all Hearing Aid Center (HAC) products and services
- Set the stage for full test, and full boat purchase when interacting with Members
- Complete 30-50 outbound calls daily to prospective and/or existing customers
- Secure a minimum of 4 immediate or scheduled full hearing tests daily for the hearing aid specialist or audiologist that works in the center
- Promote and sell non hearing aid products when Members with whom they engage do not have hearing loss
- A 50% increase in non-hearing aid product sales is expected
- Learn and use the handheld screener (when able per state regulations) and use as intercepting tool to get qualified leads
- Assist, when necessary, calling past tested Members, with or without sales, and medical referrals to schedule return visits
- Promote the HAC during Sam’s club events, Hearing Aid Center events, and possibly outside marketing events
- Will be based in HAC but will spend 95% of the time walking/working the club, intercepting, and setting tests
Check for duplicates: none.
Requirements bullets:
- High school diploma or equivalent
- Strong customer service, sales, or retail experience
- Experience working with PC hardware and software including general computer and Internet knowledge
- Excellent oral and written communication skills, organizational, problem-solving/troubleshooting skills, and presentation skills
- Previous experience with patient/customer appointment scheduling
- Proficiency with basic computer systems and scheduling software
Skills bullets: we can extract from requirements but maybe rephrase? The skills are essentially same as some requirements. To avoid duplication, we could list skills that are not already covered: strong customer service, sales, or retail experience (maybe also experience), experience with PC hardware/software, excellent oral/written communication, organizational, problem-solving/troubleshooting, presentation skills, previous experience with appointment scheduling, proficiency with basic computer systems and scheduling software. That's basically same as requirements minus education. Could still list.
But to avoid duplication, maybe we combine Requirements and Skills into one? But instruction says we can have both if content exists. It's okay if some overlap? Might be considered redundant but not prohibited. However they said "Prefer a few substantive sections over many thin ones." Overlap may be thin. But we can still include Skills as separate if we think it's substantive. However the skills list is essentially same as requirements except education. Might be considered thin. Could we instead put skills inside Requirements? But they asked to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements and Skills both. It's okay.
We'll output:
NationsBenefits is recognized as one of the fastest-growing companies in America and a Healthcare Fintech provider of supplemental benefits, flex cards, and member engagement solutions. We partner with managed care organizations to provide innovative healthcare solutions that drive growth, improve outcomes, reduce costs, and bring value to their members. Through our comprehensive suite of innovative supplemental benefits, fintech payment platforms, and member engagement solutions, we help health plans deliver high-quality benefits to their members that address the social determinants of health and improve member health outcomes and satisfaction. Our compliance-focused infrastructure, proprietary technology systems, and premier service delivery model allow our health plan partners to deliver high-quality, value-based care to millions of members. We offer a fulfilling work environment that attracts top talent and encourages all associates to contribute to delivering premier service to internal and external customers alike. Our goal is to transform the healthcare industry for the better! We provide career advancement opportunities from within the organization across multiple locations in the US, South America, and India.
About the role
The Hearing Ambassador assists and helps the licensed dispenser meet their goals and fulfill their daily duties. This role is responsible for engaging customers, Support hearing health needs, educating individuals about hearing wellness, scheduling appointments, and supporting growth through community outreach and customer relationship building.
Responsibilities
- Have a working knowledge of all Hearing Aid Center (HAC) products and services
- Set the stage for full test, and full boat purchase when interacting with Members
- Complete 30-50 outbound calls daily to prospective and/or existing customers
- Secure a minimum of 4 immediate or scheduled full hearing tests daily for the hearing aid specialist or audiologist that works in the center
- Promote and sell non hearing aid products when Members with whom they engage do not have hearing loss
- A 50% increase in non-hearing aid product sales is expected
- Learn and use the handheld screener (when able per state regulations) and use as intercepting tool to get qualified leads
- Assist, when necessary, calling past tested Members, with or without sales, and medical referrals to schedule return visits
- Promote the HAC during Sam’s club events, Hearing Aid Center events, and possibly outside marketing events
- Will be based in HAC but will spend 95% of the time walking/working the club, intercepting, and setting tests
Requirements
- High school diploma or equivalent
- Strong customer service, sales, or retail experience
- Experience working with PC hardware and software including general computer and Internet knowledge
- Excellent oral and written communication skills, organizational, problem-solving/troubleshooting skills, and presentation skills
- Previous experience with patient/customer appointment scheduling
- Proficiency with basic computer systems and scheduling software
Skills
- Strong customer service, sales, or retail experience
- Experience working with PC hardware and software including general computer and Internet knowledge
- Excellent oral and written communication skills
- Organizational, problem-solving/troubleshooting skills
- Presentation skills
- Previous experience with patient/customer appointment scheduling
- Proficiency with basic computer systems and scheduling software
after About the role or before Responsibilities. Since no specific heading, we can just add a paragraph. Similarly, there is a line: "Role: The Hearing Ambassador assists..." we already used that. The location line is separate. Thus after About the role paragraph, add a
Location: On-Site, Sam's Club Hearing Aid Center, Flagstaff, AZ.
Also there is a line: "We offer a fulfilling work environment..." already in company description. Check for any other substantive info: "We provide career advancement opportunities from within the organization across multiple locations in the US, South America, and India
- ... each bullet.
We must not include Benefits, Pay, Schedule sections.
Check for any duplicated lines: The responsibilities list includes many items. We'll copy them exactly.
Responsibilities bullets:
- Have a working knowledge of all Hearing Aid Center (HAC) products and services
- Set the stage for full test, and full boat purchase when interacting with Members
- Complete 30-50 outbound calls daily to prospective and/or existing customers
- Secure a minimum of 4 immediate or scheduled full hearing tests daily for the hearing aid specialist or audiologist that works in the center
- Promote and sell non hearing aid products when Members with whom they engage do not have hearing loss
- A 50% increase in non-hearing aid product sales is expected
- Learn and use the handheld screener (when able per state regulations) and use as intercepting tool to get qualified leads
- Assist, when necessary, calling past tested Members, with or without sales, and medical referrals to schedule return visits
- Promote the HAC during Sam’s club events, Hearing Aid Center events, and possibly outside marketing events
- Will be based in HAC but will spend 95% of the time walking/working the club, intercepting, and setting tests
Check for duplicates: none.
Requirements bullets:
- High school diploma or equivalent
- Strong customer service, sales, or retail experience
- Experience working with PC hardware and software including general computer and Internet knowledge
- Excellent oral and written communication skills, organizational, problem-solving/troubleshooting skills, and presentation skills
- Previous experience with patient/customer appointment scheduling
- Proficiency with basic computer systems and scheduling software
Skills bullets: we can extract from requirements but maybe rephrase? The skills are essentially same as some requirements. To avoid duplication, we could list skills that are not already covered: strong customer service, sales, or retail experience (maybe also experience), experience with PC hardware/software, excellent oral/written communication, organizational, problem-solving/troubleshooting, presentation skills, previous experience with appointment scheduling, proficiency with basic computer systems and scheduling software. That's basically same as requirements minus education. Could still list.
But to avoid duplication, maybe we combine Requirements and Skills into one? But instruction says we can have both if content exists. It's okay if some overlap? Might be considered redundant but not prohibited. However they said "Prefer a few substantive sections over many thin ones." Overlap may be thin. But we can still include Skills as separate if we think it's substantive. However the skills list is essentially same as requirements except education. Might be considered thin. Could we instead put skills inside Requirements? But they asked to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements and Skills both. It's okay.
We'll output:
- ... each bullet.
Then