Provider Support Coordinator

We need to output HTML fragment with sections: About the role? Actually we have Company Overview, Role Summary, Responsibilities, Qualifications, Why Join Us. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We have Company Overview (maybe "About the role"? Actually "Company Overview" is about the company, not role. Could be "About the role"? But we can use "About the role" heading for role summary? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings that match those examples if we have content. We have role summary, responsibilities, qualifications, why join us (maybe benefits?). There's no explicit pay or schedule. So we should not create those sections. We need to preserve all substantive info, remove boilerplate (EEO, equal opportunity, etc). Also remove application instructions (none). Remove duplicated lines. We need to format lists with

• . Use

  for prose. We need to include sections only when posting has real specific content. Thus sections: - About the role (maybe combine Company Overview + Role Summary? Actually "About the role" could be role summary. Company Overview could be separate? Not in list but we could still include as a heading? The instruction says use those headings as examples, not limited to them? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. We can also add other headings if needed? Probably better to stick to those. So we need to map content to those headings. We have: - About the role: could include Company Overview and Role Summary? Might be okay. - Responsibilities: list. - Qualifications: required and preferred. - Skills? Not explicitly listed but could be derived from qualifications? Might be better to not create Skills if no explicit. - Benefits: we have "Why Join Us" which describes benefits/impact. Could be Benefits section. - Pay, Schedule: not present, so omit. Thus output:

  About the role

  Company overview paragraph + role summary paragraph.

  Then

  Responsibilities

  • ...
  Then

  Qualifications

  Required: ...

  Preferred: ...

  Then

  Benefits

  Why Join Us paragraph.

  Make sure to preserve all details. Let's extract content. Company Overview: "Blink Health is the fastest growing healthcare technology company that builds products to make prescriptions accessible and affordable to everybody. Our two primary products – BlinkRx and Quick Save – remove traditional roadblocks within the current prescription supply chain, resulting in better access to critical medications and improved health outcomes for patients. BlinkRx is the world’s first pharma-to-patient cloud that offers a digital concierge service for patients who are prescribed branded medications. Patients benefit from transparent low prices, free home delivery, and world-class support on this first-of-its-kind centralized platform. With BlinkRx, never again will a patient show up at the pharmacy only to discover that they can’t afford their medication, their doctor needs to fill out a form for them, or the pharmacy doesn’t have the medication in stock. We are a highly collaborative team of builders and operators who invent new ways of working in an industry that historically has resisted innovation. Join us!" Role Summary: "The Provider Support Coordinator supports the Practice Access Management (PAM) team at the intersection of data quality and provider engagement. This role is equally operational and customer-facing: Provider Support Coordinators execute data and administrative workflows in Salesforce in addition to conducting structured outbound outreach to provider offices on behalf of BlinkRx.PSCs are often the first point of contact a provider office has with BlinkRx, and play a critical role in establishing the foundation for PAM-led growth. The ideal candidate is detail-oriented and process-driven, with strong communication skills and confidence engaging professionally with provider offices." We can combine these into About the role paragraph(s). Probably two paragraphs. Responsibilities list: bullet points from responsibilities section. Let's list them: - Create, update, and maintain provider accounts and contacts in Salesforce following standardized processes to keep practice records accurate and complete. - Clean up records by fixing duplicate accounts and contacts, correcting associations, reassigning holding-account contacts, and ensuring proper account hierarchy. - Complete and validate required account and contact fields so downstream workflows and automation function as expected. - Monitor automated workflows and alerts; investigate and resolve issues flagged by systems or the PAM team. - Flag recurring issues, data inconsistencies, or process gaps and share them with the appropriate partners for follow-up. - Make outbound calls to provider offices to support marketing opt-ins, confirm communication consent, and verify key practice and contact details. - Conduct introductory outreach to new accounts — introduce BlinkRx, gather key office and workflow information needed for PA processes, and lay the groundwork for PAM-led growth efforts. - Recognize when a provider shows interest or requires follow-up during outreach and document relevant context. - Ensure clear, timely handoffs to the PAM team with accurate notes to support successful engagement. - Reach out to existing accounts at key points in the relationship lifecycle to surface growth opportunities and keep account data current ahead of PAM follow-up. - Triage and resolve inbound requests from the pharmacy team that require direct outreach to HCP offices. Qualifications: Required: - 1–3 years of experience in operations, administrative support, data entry, or sales operations - Strong attention to detail and data accuracy - Experience with CRM platforms (Salesforce preferred) - Excellent communication skills; comfortable conducting efficient, professional outreach with provider offices - Strong organizational and multitasking ability Preferred: - Healthcare operations or provider data experience - Familiarity with Salesforce Benefits/Why Join Us: "It is rare to have a company that both deeply impacts its customers and is able to provide its services across a massive population. At Blink, we have a huge impact on people when they are most vulnerable: at the intersection of their healthcare and finances. We are also the fastest growing healthcare company in the country and are driving that impact across millions of new patients every year. Our business model not only helps people, but drives economics that allow us to build a generational company. We are a relentlessly learning, constantly curious, and aggressively collaborative cross-functional team dedicated to inventing new ways to improve the lives of our customers. We are an equal opportunity employer and value diversity of all kinds. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status. Applicants who provide their phone number and consent to receive text messages may receive SMS or MMS updates from Blink Health regarding their application." We need to remove EEO boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the equal opportunity employer statement and the non-discrimination line. Also remove the SMS consent line? That's not EEO but maybe considered application instruction? It's about receiving updates; could be considered application instruction? It's not exactly instruction to apply, but it's about consent. Might be considered boilerplate; safer to remove it. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The SMS consent line is not exactly application instruction but could be considered part of application process. Safer to remove it. Thus Benefits section should keep the impactful statements before the EEO line. So Benefits paragraph: "It is rare to have a company that both deeply impacts its customers and is able to provide its services across a massive population. At Blink, we have a huge impact on people when they are most vulnerable: at the intersection of their healthcare and finances. We are also the fastest growing healthcare company in the country and are driving that impact across millions of new patients every year. Our business model not only helps people, but drives economics that allow us to build a generational company. We are a relentlessly learning, constantly curious, and aggressively collaborative cross-functional team dedicated to inventing new ways to improve the lives of our customers." Now produce HTML. We need to ensure no extra whitespace? Just output. Let's craft:

  About the role

  Blink Health is the fastest growing healthcare technology company that builds products to make prescriptions accessible and affordable to everybody. Our two primary products – BlinkRx and Quick Save – remove traditional roadblocks within the current prescription supply chain, resulting in better access to critical medications and improved health outcomes for patients. BlinkRx is the world’s first pharma-to-patient cloud that offers a digital concierge service for patients who are prescribed branded medications. Patients benefit from transparent low prices, free home delivery, and world-class support on this first-of-its-kind centralized platform. With BlinkRx, never again will a patient show up at the pharmacy only to discover that they can’t afford their medication, their doctor needs to fill out a form for them, or the pharmacy doesn’t have the medication in stock. We are a highly collaborative team of builders and operators who invent new ways of working in an industry that historically has resisted innovation. Join us!

  The Provider Support Coordinator supports the Practice Access Management (PAM) team at the intersection of data quality and provider engagement. This role is equally operational and customer-facing: Provider Support Coordinators execute data and administrative workflows in Salesforce in addition to conducting structured outbound outreach to provider offices on behalf of BlinkRx. PSCs are often the first point of contact a provider office has with BlinkRx, and play a critical role in establishing the foundation for PAM-led growth. The ideal candidate is detail-oriented and process-driven, with strong communication skills and confidence engaging professionally with provider offices.

  Responsibilities

  • Create, update, and maintain provider accounts and contacts in Salesforce following standardized processes to keep practice records accurate and complete.
  • Clean up records by fixing duplicate accounts and contacts, correcting associations, reassigning holding-account contacts, and ensuring proper account hierarchy.
  • Complete and validate required account and contact fields so downstream workflows and automation function as expected.
  • Monitor automated workflows and alerts; investigate and resolve issues flagged by systems or the PAM team.
  • Flag recurring issues, data inconsistencies, or process gaps and share them with the appropriate partners for follow-up.
  • Make outbound calls to provider offices to support marketing opt-ins, confirm communication consent, and verify key practice and contact details.
  • Conduct introductory outreach to new accounts — introduce BlinkRx, gather key office and workflow information needed for PA processes, and lay the groundwork for PAM-led growth efforts.
  • Recognize when a provider shows interest or requires follow-up during outreach and document relevant context.
  • Ensure clear, timely handoffs to the PAM team with accurate notes to support successful engagement.
  • Reach out to existing accounts at key points in the relationship lifecycle to surface growth opportunities and keep account data current ahead of PAM follow-up.
  • Triage and resolve inbound requests from the pharmacy team that require direct outreach to HCP offices.

  Qualifications

  Required:

  • 1–3 years of experience in operations, administrative support, data entry, or sales operations
  • Strong attention to detail and data accuracy
  • Experience with CRM platforms (Salesforce preferred)
  • Excellent communication skills; comfortable conducting efficient, professional outreach with provider offices
  • Strong organizational and multitasking ability

  Preferred:

  • Healthcare operations or provider data experience
  • Familiarity with Sales