Regional Front Desk Operations Manager - 7 Locations, South Florida
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate like EEO etc. At end there is "Medstation Primary Care is an Equal Opportunity Employer..." that's boilerplate; remove.
We need to include sections only when posting has real specific content. So we will have sections: About Medstation (maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use similar headings. Probably we should use headings that match content: About Medstation, Role Summary, Key Responsibilities, Qualifications, Preferred Skills, What Success Looks Like in 90 Days. Those are not exactly the examples but likely acceptable. However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those exact headings when applicable. But we have content that doesn't map exactly: we have "About Medstation" not "About the role". Could we use "About the role" for the role summary? The role summary is separate. Maybe we can use "About the role" for the role summary paragraph. And "Responsibilities" for key responsibilities. "Requirements" for qualifications. "Skills" for preferred skills. "What Success Looks Like in 90 Days" maybe could be under "Responsibilities" or separate? Could be a separate section but not in list; maybe we can incorporate into Responsibilities? But it's distinct. The instruction says prefer a few substantive sections over many thin ones. Could combine "What Success Looks Like in 90 Days" into Responsibilities or maybe as a subsection under Responsibilities? But we need to preserve all info; we could add a
under Responsibilities that includes that. However the instruction says use
- for any list of duties/requirements/benefits. The success looks like is not a list but prose; we can put as
.
Thus sections: About the role (role summary), Responsibilities (key responsibilities + success look), Requirements (qualifications), Skills (preferred skills). Also maybe About Medstation as a separate section? Could be "About the company"? Not in list but we could include as a
before sections. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those headings. So we will have:
About the role
Role Summary paragraph.
Responsibilities
- ... list items from Key Responsibilities and also maybe the success look items? The success look is not a duty but outcome; we could still include as list items under Responsibilities? Might be okay. But we need to preserve all info; we could include success look as separate
after list.
Requirements
- ... qualifications list.
Skills
- ... preferred skills list.
We also need to include About Medstation description; maybe we can put that as a
before the first heading, as introductory prose.
We must not include boilerplate EEO etc.
Let's extract content.
About Medstation: "Medstation is a fast-growing, patient-centered primary care group with 7 clinics across South Florida. We provide same-week access, evening and Saturday hours, and high-touch bilingual care (English / Spanish / Portuguese). Our mission is simple: make quality primary care accessible, affordable, and human."
Role Summary: "The Regional Front Desk Operations Manager owns all front office operations across our 7 locations. You will lead, standardize, and optimize every patient touchpoint from first phone call to check-out. You will build SOPs, lead site leads, and travel regularly to audit, coach, and solve problems. This is a hands-on, multi-site operator role - not a desk job."
Key Responsibilities: bullet points:
- Multi-Site Front Office Leadership: Oversee daily front desk operations for 7 clinics. Standardize workflows for check-in, check-out, phones, scheduling, and patient flow. Conduct weekly site audits.
- Patient Access & Experience: Own KPIs: 3rd Next Available 95%, Google Review average >4.7. Lead service recovery and patient de-escalation.
- Staffing, Training & Performance: Hire, train, and manage 14-20 front office staff. Create onboarding checklists, phone scripts, and competency tests. Build float pool for PTO/call-out coverage. Run weekly huddles and monthly trainings.
- Front-End Revenue Cycle: Ensure 95%+ eligibility verified 48 hours prior. Ensure accurate demographic entry, referral status, and time-of-service collections. Partner with Billing Coordinator to keep front-end denial rate . Might need to split long sentences but okay.
Qualifications:
- 5+ years managing front office / patient services in healthcare, with 2+ years managing MULTIPLE sites required
- Proven experience leading 15+ staff across locations - primary care, urgent care, or multi-specialty preferred
- Expert in EHR/PM systems (eClinicalWorks, Athenahealth, Elation, or similar) + eligibility tools (Availity, Waystar)
- Strong knowledge of insurance verification, POS collections, and front-end denial prevention
- Bilingual English / Spanish REQUIRED - Portuguese a strong plus (per our patient population)
- Valid driver's license, reliable vehicle, and ability to travel daily across Broward, Miami-Dade, and Palm Beach
- Highly organized, hospitality-driven, and comfortable building SOPs from scratch
Preferred Skills:
- Experience with value-based care metrics: AWV, CCM, risk adjustment, referral closure
- Experience implementing phone systems / reminder systems (Weave, Klara, Phreesia, etc.)
- Comfortable with Excel/Sheets: staffing models, KPI dashboards, labor cost tracking
- Experience scaling from 3-5 to 7+ locations
What Success Looks Like in 90 Days:
- All 7 Medstation sites running the same check-in/out SOP with 95%+ eligibility verified 48hrs prior
- Phone abandon rate under 7% and collections at time of service over 95%
- Fully staffed front desk with trained float coverage and zero unplanned closures
- Live dashboard for daily visibility on no-show, collections, eligibility, and patient complaints
We can include these as list items under Responsibilities or as a separate section. Since they are outcomes, maybe better as a separate section "What Success Looks Like in 90 Days". But instruction says prefer few sections; we could add a fourth section "Success Metrics". However not in examples. Might be okay to add as a section with heading
Success Metrics
. But instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to incorporate success metrics into Responsibilities as additional list items.
Thus Responsibilities list will include all key responsibilities plus success metrics.
Now we need to ensure we don't repeat job title. Not needed.
Now produce HTML fragment.
We'll start with a
for About Medstation.
Then
About the role
Role Summary...
Then Responsibilities
...
Then Requirements
...
Then Skills
...
Make sure to preserve all details exactly.
Let's craft.
About Medstation paragraph: "Medstation is a fast-growing, patient-centered primary care group with 7 clinics across South Florida. We provide same-week access, evening and Saturday hours, and high-touch bilingual care (English / Spanish / Portuguese). Our mission is simple: make quality primary care accessible, affordable, and human."
Role Summary paragraph: "The Regional Front Desk Operations Manager owns all front office operations across our 7 locations. You will lead, standardize, and optimize every patient touchpoint from first phone call to check-out. You will build SOPs, lead site leads, and travel regularly to audit, coach, and solve problems. This is a hands-on, multi-site operator role - not a desk job."
Now Responsibilities list items:
We need to break each bullet into - . Let's list:
- Oversee daily front desk operations for 7 clinics. Standardize workflows for check-in, check-out, phones, scheduling, and patient flow. Conduct weekly site audits.
- Own KPIs: 3rd Next Available 95%, Google Review average >4.7. Lead service recovery and patient de-escalation.
- Hire, train, and manage 14-20 front office staff. Create onboarding checklists, phone scripts, and competency tests. Build float pool for PTO/call-out coverage. Run weekly huddles and monthly trainings.
- Ensure 95%+ eligibility verified 48 hours prior. Ensure accurate demographic entry, referral status, and time-of-service collections. Partner with Billing Coordinator to keep front-end denial rate <7%. Own daily cash reconciliation.
- Maintain HIPAA, OSHA, and front-office compliance. Maintain provider templates, closure calendars, and EHR scheduling rules. Own front desk dashboard and monthly reporting to leadership.
- Partner with Clinical Lead to support AWV, CCM, and TCM enrollment via front desk workflows and referral closure tracking.
- All 7 Medstation sites running the same check-in/out SOP with 95%+ eligibility verified 48hrs prior.
- Phone abandon rate under 7% and collections at time of service over 95%.
- Fully staffed front desk with trained float coverage and zero unplanned closures.
- Live dashboard for daily visibility on no-show, collections, eligibility, and patient complaints.
Check we didn't miss any: also "Lead service recovery and patient de-escalation" included. Good.
Now Requirements list items:
- 5+ years managing front office / patient services in healthcare, with 2+ years managing MULTIPLE sites required
- Proven experience leading 15+ staff across locations - primary care, urgent care, or multi-specialty preferred
- Expert in EHR/PM systems (e
for prose. We need to preserve all substantive information, remove boilerplate like EEO etc. At end there is "Medstation Primary Care is an Equal Opportunity Employer..." that's boilerplate; remove. We need to include sections only when posting has real specific content. So we will have sections: About Medstation (maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use similar headings. Probably we should use headings that match content: About Medstation, Role Summary, Key Responsibilities, Qualifications, Preferred Skills, What Success Looks Like in 90 Days. Those are not exactly the examples but likely acceptable. However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those exact headings when applicable. But we have content that doesn't map exactly: we have "About Medstation" not "About the role". Could we use "About the role" for the role summary? The role summary is separate. Maybe we can use "About the role" for the role summary paragraph. And "Responsibilities" for key responsibilities. "Requirements" for qualifications. "Skills" for preferred skills. "What Success Looks Like in 90 Days" maybe could be under "Responsibilities" or separate? Could be a separate section but not in list; maybe we can incorporate into Responsibilities? But it's distinct. The instruction says prefer a few substantive sections over many thin ones. Could combine "What Success Looks Like in 90 Days" into Responsibilities or maybe as a subsection under Responsibilities? But we need to preserve all info; we could add a
under Responsibilities that includes that. However the instruction says use
- for any list of duties/requirements/benefits. The success looks like is not a list but prose; we can put as
. Thus sections: About the role (role summary), Responsibilities (key responsibilities + success look), Requirements (qualifications), Skills (preferred skills). Also maybe About Medstation as a separate section? Could be "About the company"? Not in list but we could include as a
before sections. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those headings. So we will have:
About the role
Role Summary paragraph.
Responsibilities
- ... list items from Key Responsibilities and also maybe the success look items? The success look is not a duty but outcome; we could still include as list items under Responsibilities? Might be okay. But we need to preserve all info; we could include success look as separate
after list.
Requirements
- ... qualifications list.
Skills
- ... preferred skills list.
We also need to include About Medstation description; maybe we can put that as a
before the first heading, as introductory prose. We must not include boilerplate EEO etc. Let's extract content. About Medstation: "Medstation is a fast-growing, patient-centered primary care group with 7 clinics across South Florida. We provide same-week access, evening and Saturday hours, and high-touch bilingual care (English / Spanish / Portuguese). Our mission is simple: make quality primary care accessible, affordable, and human." Role Summary: "The Regional Front Desk Operations Manager owns all front office operations across our 7 locations. You will lead, standardize, and optimize every patient touchpoint from first phone call to check-out. You will build SOPs, lead site leads, and travel regularly to audit, coach, and solve problems. This is a hands-on, multi-site operator role - not a desk job." Key Responsibilities: bullet points: - Multi-Site Front Office Leadership: Oversee daily front desk operations for 7 clinics. Standardize workflows for check-in, check-out, phones, scheduling, and patient flow. Conduct weekly site audits. - Patient Access & Experience: Own KPIs: 3rd Next Available 95%, Google Review average >4.7. Lead service recovery and patient de-escalation. - Staffing, Training & Performance: Hire, train, and manage 14-20 front office staff. Create onboarding checklists, phone scripts, and competency tests. Build float pool for PTO/call-out coverage. Run weekly huddles and monthly trainings. - Front-End Revenue Cycle: Ensure 95%+ eligibility verified 48 hours prior. Ensure accurate demographic entry, referral status, and time-of-service collections. Partner with Billing Coordinator to keep front-end denial rate . Might need to split long sentences but okay. Qualifications: - 5+ years managing front office / patient services in healthcare, with 2+ years managing MULTIPLE sites required - Proven experience leading 15+ staff across locations - primary care, urgent care, or multi-specialty preferred - Expert in EHR/PM systems (eClinicalWorks, Athenahealth, Elation, or similar) + eligibility tools (Availity, Waystar) - Strong knowledge of insurance verification, POS collections, and front-end denial prevention - Bilingual English / Spanish REQUIRED - Portuguese a strong plus (per our patient population) - Valid driver's license, reliable vehicle, and ability to travel daily across Broward, Miami-Dade, and Palm Beach - Highly organized, hospitality-driven, and comfortable building SOPs from scratch Preferred Skills: - Experience with value-based care metrics: AWV, CCM, risk adjustment, referral closure - Experience implementing phone systems / reminder systems (Weave, Klara, Phreesia, etc.) - Comfortable with Excel/Sheets: staffing models, KPI dashboards, labor cost tracking - Experience scaling from 3-5 to 7+ locations What Success Looks Like in 90 Days: - All 7 Medstation sites running the same check-in/out SOP with 95%+ eligibility verified 48hrs prior - Phone abandon rate under 7% and collections at time of service over 95% - Fully staffed front desk with trained float coverage and zero unplanned closures - Live dashboard for daily visibility on no-show, collections, eligibility, and patient complaints We can include these as list items under Responsibilities or as a separate section. Since they are outcomes, maybe better as a separate section "What Success Looks Like in 90 Days". But instruction says prefer few sections; we could add a fourth section "Success Metrics". However not in examples. Might be okay to add as a section with heading
Success Metrics
. But instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to incorporate success metrics into Responsibilities as additional list items. Thus Responsibilities list will include all key responsibilities plus success metrics. Now we need to ensure we don't repeat job title. Not needed. Now produce HTML fragment. We'll start with a
for About Medstation. Then
About the role
Role Summary...
ThenResponsibilities
- ...
Requirements
- ...
Skills
- ...
- . Let's list: - Oversee daily front desk operations for 7 clinics. Standardize workflows for check-in, check-out, phones, scheduling, and patient flow. Conduct weekly site audits. - Own KPIs: 3rd Next Available 95%, Google Review average >4.7. Lead service recovery and patient de-escalation. - Hire, train, and manage 14-20 front office staff. Create onboarding checklists, phone scripts, and competency tests. Build float pool for PTO/call-out coverage. Run weekly huddles and monthly trainings. - Ensure 95%+ eligibility verified 48 hours prior. Ensure accurate demographic entry, referral status, and time-of-service collections. Partner with Billing Coordinator to keep front-end denial rate <7%. Own daily cash reconciliation. - Maintain HIPAA, OSHA, and front-office compliance. Maintain provider templates, closure calendars, and EHR scheduling rules. Own front desk dashboard and monthly reporting to leadership. - Partner with Clinical Lead to support AWV, CCM, and TCM enrollment via front desk workflows and referral closure tracking. - All 7 Medstation sites running the same check-in/out SOP with 95%+ eligibility verified 48hrs prior. - Phone abandon rate under 7% and collections at time of service over 95%. - Fully staffed front desk with trained float coverage and zero unplanned closures. - Live dashboard for daily visibility on no-show, collections, eligibility, and patient complaints. Check we didn't miss any: also "Lead service recovery and patient de-escalation" included. Good. Now Requirements list items: - 5+ years managing front office / patient services in healthcare, with 2+ years managing MULTIPLE sites required - Proven experience leading 15+ staff across locations - primary care, urgent care, or multi-specialty preferred - Expert in EHR/PM systems (e
- ... preferred skills list.
We also need to include About Medstation description; maybe we can put that as a
- ... qualifications list.
- ... list items from Key Responsibilities and also maybe the success look items? The success look is not a duty but outcome; we could still include as list items under Responsibilities? Might be okay. But we need to preserve all info; we could include success look as separate