Front Desk Lead Receptionist
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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content. The posting includes: Who We Are (company description), Why Join Us? (benefits?), Position Summary (overview), Duties and Responsibilities (list), Education, Experience, Licenses, and Certifications (requirements). Also mention "Our company participates in E-Verify..." which is minor metadata; could be a short
maybe under a generic section? But we should not create sections for filler. Could include a short paragraph at end.
We need headings: maybe "About the Company" (but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not strict list; we can use those headings if appropriate. For company description, maybe "About the role" is not appropriate; maybe "About the Company"? But they didn't list that as example; but they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we can use those headings; but we can also use other headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical headings we might use; but we can also use other meaningful headings? Probably safer to stick to those given headings where applicable. However we have content like "Who We Are" which is about the company; maybe we can treat as "About the role"? Not exactly. Could treat as "About the role" but that's weird. Maybe we can omit that heading and just put the company description in a
without heading? But they said include a section ONLY when posting has real, specific content for it. Could we have a section without heading? No, sections need heading. Could we use "About the role" as heading for company description? Might be acceptable but not ideal. Another approach: Use "Responsibilities" for duties, "Requirements" for education/experience, "Skills" for skills, maybe "Benefits" for Why Join Us? (they mention competitive salaries, outstanding benefits). There's no explicit Pay or Schedule. So we can create sections: Responsibilities, Requirements, Skills, Benefits. Also maybe a brief intro paragraph about the role (Position Summary) could be under a heading like "About the role". That seems plausible: "About the role" heading for Position Summary. Then "Who We Are" and "Why Join Us?" could be combined into a brief intro? But they are substantive. Could we make a section "About the Company"? Not in list but maybe allowed. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests examples, not exhaustive. So we can use other headings as needed, as long as they are . Probably safe to use headings like "About the Company", "Why Join Us?", "Position Summary", "Responsibilities", "Requirements". But to be safe, we could map: "About the role" -> Position Summary; "Responsibilities" -> Duties and Responsibilities; "Requirements" -> Education, Experience, Licenses, and Certifications; "Skills" -> maybe we can extract skills from requirements (coaching, communication, etc.) but we already have them in requirements; maybe we can skip Skills. "Benefits" -> Why Join Us? (competitive salaries, outstanding benefits). Also we could include "About the Company" as a heading for Who We Are. That seems reasonable.
We must not include filler like "commensurate with experience". Not present.
We need to output only HTML fragment.
Let's extract content:
Who We Are: "As the largest and most comprehensive orthopaedic team in the state, we bring together the medical expertise of leading orthopaedic and musculoskeletal surgeons, specialists, and research pioneers. Every provider in our network shares a deep commitment to leadership in education, innovation, and research, as well as a dedicated focus on prioritizing patient care across the continuum of treatment."
Why Join Us?: "Interested in orthopaedics? Discover why it’s worth pursuing with us. Our career opportunities offer competitive salaries, outstanding benefits, and a platform to pursue your passion. As Michigan’s largest and most comprehensive orthopaedic team, we are actively seeking skilled and enthusiastic individuals to join us today."
Position Summary: "The Front Desk Lead is responsible for leading the daily operations of the front office while creating an exceptional experience for every patient who walks through our doors. This role serves as the frontline leader for Front Desk Receptionists, providing day-to-day coaching, operational oversight, and support to ensure efficient workflows, outstanding customer service, and consistent adherence to organizational standards. The ideal candidate is a hands-on leader who thrives in a fast-paced healthcare environment, enjoys developing others, leads with accountability, and is passionate about delivering an exceptional patient experience."
Duties and Responsibilities: list items:
- Leadership: Provide daily guidance, coaching, and support to Front Desk Receptionists while fostering a positive, accountable, and patient-focused team culture.
- Operational Oversight: Coordinate daily front office operations to ensure efficient patient flow, excellent customer service, and adherence to organizational standards.
- Staffing & Scheduling: Prepare weekly schedules and task assignments to maintain appropriate coverage and workflow.
- Customer Service: Deliver exceptional patient service while serving as the primary point of contact for patient concerns and service recovery.
- Front Desk Support: Perform Front Desk Receptionist duties as needed to support staffing and operational demands.
- Team Development: Assist the Clinic Coordinator with onboarding, training, performance coaching, and reinforcing policies and procedures.
- Financial Accountability: Oversee accurate collection of co-pays, balances, and applicable patient fees in accordance with organizational policy.
- Workflow Management: Monitor patient flow, communicate delays, and ensure Front Desk work queues, scanning, and administrative tasks are completed timely.
- Inventory & Organization: Maintain office supply inventory and ensure the front office remains clean, organized, and professional.
- Collaboration: Serve as the liaison between Front Desk staff, providers, and clinic leadership to promote effective communication and resolve operational concerns.
- Compliance: Ensure adherence to HIPAA, organizational policies, and Front Desk procedures while promoting accountability and consistency.
- Other Duties: Perform additional responsibilities as assigned.
Education, Experience, Licenses, and Certifications:
- High school diploma or general education degree (GED) required.
- Minimum of two (2) years of customer service experience required.
- Minimum of one (1) year of experience in a medical office or healthcare setting preferred.
- Previous leadership, team lead, or supervisory experience preferred.
- Demonstrated ability to coach, mentor, and support team performance while fostering a positive work environment.
- Strong interpersonal, communication, and conflict resolution skills.
- Excellent organizational skills with the ability to prioritize competing responsibilities in a fast-paced environment.
- Proficient in Microsoft Office and electronic health record (EHR) systems.
- Ability to maintain confidentiality and exercise sound judgment in accordance with HIPAA and organizational policies.
Additional note: "Our company participates in E-Verify to confirm the employment eligibility of all newly hired employees, as required by federal law." This is minor metadata; we can put as a short
at end maybe under a generic section? Could just include as a
after sections without heading? But they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This note is specific content, not filler. Could we put it under a heading like "Additional Information"? Not in examples but could be okay. However maybe we can just include it as a
after the last section without a heading; but then it's not a section. The instruction about sections may not prohibit stray
outside sections. It says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid stray paragraphs. But better to wrap it in a
maybe under a heading like "Additional Information". But that heading is not in the examples but could be okay. However to be safe, we could just add a
at the end without a heading; it's not a section, just a paragraph. The instruction didn't forbid that. I'd include it as a
after the sections.
Now decide headings:
- About the Company (for Who We Are)
- Why Join Us? (for Benefits)
- About the role (for Position Summary)
- Responsibilities (for Duties)
- Requirements (for Education/Experience)
- (Optional) Skills? Could combine with Requirements but we already have skills listed there; we could keep Requirements only.
We need to avoid thin sections. Each of these has substantive content.
Now produce HTML:
About the Company
As the largest and most comprehensive orthopaedic team in the state, we bring together the medical expertise of leading orthopaedic and musculoskeletal surgeons, specialists, and research pioneers. Every provider in our network shares a deep commitment to leadership in education, innovation, and research, as well as a dedicated focus on prioritizing patient care across the continuum of treatment.
Why Join Us?
Interested in orthopaedics? Discover why it’s worth pursuing with us. Our career opportunities offer competitive salaries, outstanding benefits, and a platform to pursue your passion. As Michigan’s largest and most comprehensive orthopaedic team, we are actively seeking skilled and enthusiastic individuals to join us today.
About the role
The Front Desk Lead is responsible for leading the daily operations of the front office while creating an exceptional experience for every patient who walks through our doors. This role serves as the frontline leader for Front Desk Receptionists, providing day-to-day coaching, operational oversight, and support to ensure efficient workflows, outstanding customer service, and consistent adherence to organizational standards. The ideal candidate is a hands-on leader who thrives in a fast-paced healthcare environment, enjoys developing others, leads with accountability, and is passionate about delivering an exceptional patient experience.
Responsibilities
- Leadership: Provide daily guidance, coaching, and support to Front Desk Receptionists while fostering a positive, accountable, and patient-focused team culture.
- Operational Oversight: Coordinate daily front office operations to ensure efficient patient flow, excellent customer service, and adherence to organizational standards.
- Staffing & Scheduling: Prepare weekly schedules and task assignments to maintain appropriate coverage and workflow.
- Customer Service: Deliver exceptional patient service while serving as the primary point of contact for patient concerns and service recovery.
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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. The posting includes: Who We Are (company description), Why Join Us? (benefits?), Position Summary (overview), Duties and Responsibilities (list), Education, Experience, Licenses, and Certifications (requirements). Also mention "Our company participates in E-Verify..." which is minor metadata; could be a short
maybe under a generic section? But we should not create sections for filler. Could include a short paragraph at end. We need headings: maybe "About the Company" (but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not strict list; we can use those headings if appropriate. For company description, maybe "About the role" is not appropriate; maybe "About the Company"? But they didn't list that as example; but they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we can use those headings; but we can also use other headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical headings we might use; but we can also use other meaningful headings? Probably safer to stick to those given headings where applicable. However we have content like "Who We Are" which is about the company; maybe we can treat as "About the role"? Not exactly. Could treat as "About the role" but that's weird. Maybe we can omit that heading and just put the company description in a
without heading? But they said include a section ONLY when posting has real, specific content for it. Could we have a section without heading? No, sections need heading. Could we use "About the role" as heading for company description? Might be acceptable but not ideal. Another approach: Use "Responsibilities" for duties, "Requirements" for education/experience, "Skills" for skills, maybe "Benefits" for Why Join Us? (they mention competitive salaries, outstanding benefits). There's no explicit Pay or Schedule. So we can create sections: Responsibilities, Requirements, Skills, Benefits. Also maybe a brief intro paragraph about the role (Position Summary) could be under a heading like "About the role". That seems plausible: "About the role" heading for Position Summary. Then "Who We Are" and "Why Join Us?" could be combined into a brief intro? But they are substantive. Could we make a section "About the Company"? Not in list but maybe allowed. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests examples, not exhaustive. So we can use other headings as needed, as long as they are . Probably safe to use headings like "About the Company", "Why Join Us?", "Position Summary", "Responsibilities", "Requirements". But to be safe, we could map: "About the role" -> Position Summary; "Responsibilities" -> Duties and Responsibilities; "Requirements" -> Education, Experience, Licenses, and Certifications; "Skills" -> maybe we can extract skills from requirements (coaching, communication, etc.) but we already have them in requirements; maybe we can skip Skills. "Benefits" -> Why Join Us? (competitive salaries, outstanding benefits). Also we could include "About the Company" as a heading for Who We Are. That seems reasonable.
We must not include filler like "commensurate with experience". Not present.
We need to output only HTML fragment.
Let's extract content:
Who We Are: "As the largest and most comprehensive orthopaedic team in the state, we bring together the medical expertise of leading orthopaedic and musculoskeletal surgeons, specialists, and research pioneers. Every provider in our network shares a deep commitment to leadership in education, innovation, and research, as well as a dedicated focus on prioritizing patient care across the continuum of treatment."
Why Join Us?: "Interested in orthopaedics? Discover why it’s worth pursuing with us. Our career opportunities offer competitive salaries, outstanding benefits, and a platform to pursue your passion. As Michigan’s largest and most comprehensive orthopaedic team, we are actively seeking skilled and enthusiastic individuals to join us today."
Position Summary: "The Front Desk Lead is responsible for leading the daily operations of the front office while creating an exceptional experience for every patient who walks through our doors. This role serves as the frontline leader for Front Desk Receptionists, providing day-to-day coaching, operational oversight, and support to ensure efficient workflows, outstanding customer service, and consistent adherence to organizational standards. The ideal candidate is a hands-on leader who thrives in a fast-paced healthcare environment, enjoys developing others, leads with accountability, and is passionate about delivering an exceptional patient experience."
Duties and Responsibilities: list items:
- Leadership: Provide daily guidance, coaching, and support to Front Desk Receptionists while fostering a positive, accountable, and patient-focused team culture.
- Operational Oversight: Coordinate daily front office operations to ensure efficient patient flow, excellent customer service, and adherence to organizational standards.
- Staffing & Scheduling: Prepare weekly schedules and task assignments to maintain appropriate coverage and workflow.
- Customer Service: Deliver exceptional patient service while serving as the primary point of contact for patient concerns and service recovery.
- Front Desk Support: Perform Front Desk Receptionist duties as needed to support staffing and operational demands.
- Team Development: Assist the Clinic Coordinator with onboarding, training, performance coaching, and reinforcing policies and procedures.
- Financial Accountability: Oversee accurate collection of co-pays, balances, and applicable patient fees in accordance with organizational policy.
- Workflow Management: Monitor patient flow, communicate delays, and ensure Front Desk work queues, scanning, and administrative tasks are completed timely.
- Inventory & Organization: Maintain office supply inventory and ensure the front office remains clean, organized, and professional.
- Collaboration: Serve as the liaison between Front Desk staff, providers, and clinic leadership to promote effective communication and resolve operational concerns.
- Compliance: Ensure adherence to HIPAA, organizational policies, and Front Desk procedures while promoting accountability and consistency.
- Other Duties: Perform additional responsibilities as assigned.
Education, Experience, Licenses, and Certifications:
- High school diploma or general education degree (GED) required.
- Minimum of two (2) years of customer service experience required.
- Minimum of one (1) year of experience in a medical office or healthcare setting preferred.
- Previous leadership, team lead, or supervisory experience preferred.
- Demonstrated ability to coach, mentor, and support team performance while fostering a positive work environment.
- Strong interpersonal, communication, and conflict resolution skills.
- Excellent organizational skills with the ability to prioritize competing responsibilities in a fast-paced environment.
- Proficient in Microsoft Office and electronic health record (EHR) systems.
- Ability to maintain confidentiality and exercise sound judgment in accordance with HIPAA and organizational policies.
Additional note: "Our company participates in E-Verify to confirm the employment eligibility of all newly hired employees, as required by federal law." This is minor metadata; we can put as a short
at end maybe under a generic section? Could just include as a
after sections without heading? But they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This note is specific content, not filler. Could we put it under a heading like "Additional Information"? Not in examples but could be okay. However maybe we can just include it as a
after the last section without a heading; but then it's not a section. The instruction about sections may not prohibit stray
outside sections. It says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid stray paragraphs. But better to wrap it in a
maybe under a heading like "Additional Information". But that heading is not in the examples but could be okay. However to be safe, we could just add a
at the end without a heading; it's not a section, just a paragraph. The instruction didn't forbid that. I'd include it as a
after the sections. Now decide headings: - About the Company (for Who We Are) - Why Join Us? (for Benefits) - About the role (for Position Summary) - Responsibilities (for Duties) - Requirements (for Education/Experience) - (Optional) Skills? Could combine with Requirements but we already have skills listed there; we could keep Requirements only. We need to avoid thin sections. Each of these has substantive content. Now produce HTML:
About the Company
As the largest and most comprehensive orthopaedic team in the state, we bring together the medical expertise of leading orthopaedic and musculoskeletal surgeons, specialists, and research pioneers. Every provider in our network shares a deep commitment to leadership in education, innovation, and research, as well as a dedicated focus on prioritizing patient care across the continuum of treatment.
Why Join Us?
Interested in orthopaedics? Discover why it’s worth pursuing with us. Our career opportunities offer competitive salaries, outstanding benefits, and a platform to pursue your passion. As Michigan’s largest and most comprehensive orthopaedic team, we are actively seeking skilled and enthusiastic individuals to join us today.
About the role
The Front Desk Lead is responsible for leading the daily operations of the front office while creating an exceptional experience for every patient who walks through our doors. This role serves as the frontline leader for Front Desk Receptionists, providing day-to-day coaching, operational oversight, and support to ensure efficient workflows, outstanding customer service, and consistent adherence to organizational standards. The ideal candidate is a hands-on leader who thrives in a fast-paced healthcare environment, enjoys developing others, leads with accountability, and is passionate about delivering an exceptional patient experience.
Responsibilities
- Leadership: Provide daily guidance, coaching, and support to Front Desk Receptionists while fostering a positive, accountable, and patient-focused team culture.
- Operational Oversight: Coordinate daily front office operations to ensure efficient patient flow, excellent customer service, and adherence to organizational standards.
- Staffing & Scheduling: Prepare weekly schedules and task assignments to maintain appropriate coverage and workflow.
- Customer Service: Deliver exceptional patient service while serving as the primary point of contact for patient concerns and service recovery.