Practice Support Specialist (Part Time Onsite)
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 parse the posting.
Content:
- As a Practice Support Specialist, you'll be part of our Practice Support team and the go-to person on site in our Clifton Park office. You'll help patients, referring partners, and internal staff get what they need by managing inquiries over the phone, by email, and through electronic ticketing, making sure questions are answered and requests are handled quickly and professionally. This part-time, in-person role is based in our Clifton Park office, for up to 25 hours per week. Days and hours are flexible but will be scheduled within Monday-Friday, 9 a.m.-5 p.m. Along with supporting patients and partners, you'll keep the office running smoothly by handling mail, keeping supplies stocked, and making sure the space stays organized. You'll also handle key support tasks such as verifying benefit eligibility, scheduling and rescheduling appointments, and assisting patients with registration and other needs. Training will be provided. This role is all about creating a welcoming, efficient, and supportive environment that makes it easy for patients and partners to get the help they need and ensures the office operates smoothly.
Then "Requirements" heading appears in the posting: "Requirements High School diploma or GED required; Associate degree strongly preferredExperience in a customer service or call center role a plus; training provided for candidates without direct experienceExcellent verbal and written communication skillsComfortable navigating multiple software platforms and web-based applicationsAbility to work in a HIPAA-compliant manner with sensitive and private data, including maintaining a secure and confidential workspaceExperience with patient scheduling or registration is a plusExperience with insurance eligibility verification is a plusPrior experience in a medical or behavioral health setting is a plusExperience using Zendesk or similar ticketing systems preferredExperience with EHR or EMR systems is a plusExperience with standard office productivity tools is a plusBilingual or multilingual proficiency is a plusMust be eligible to work in the United States"
Then "Benefits" heading: "Benefits Competitive hourly rate of 22.00-25.00 USDComprehensive Medical, Dental, and Vision plans availablePaid Time Off, Sick Time, and Paid Company Holidays401(k) Retirement Savings Program with 2% company matchVoluntary Life InsuranceEmployee Assistance Program (EAP)Annual business-related expense stipend"
Then "About Aptihealth" description.
We need to decide sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (list of requirements), Benefits (list of benefits), maybe Skills? But we can combine Requirements and Skills? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections with real content.
We have content for About the role (intro paragraph). Responsibilities: we have duties: managing inquiries over phone/email/ticketing, answering questions, handling requests quickly and professionally, handling mail, keeping supplies stocked, keeping space organized, verifying benefit eligibility, scheduling/rescheduling appointments, assisting patients with registration and other needs, training provided (maybe not a duty). Also "creating a welcoming, efficient, and supportive environment". We can list these as bullet points.
Requirements: list of qualifications: High School diploma or GED required; Associate degree strongly preferred; Experience in a customer service or call center role a plus; training provided for candidates without direct experience; Excellent verbal and written communication skills; Comfortable navigating multiple software platforms and web-based applications; Ability to work in a HIPAA-compliant manner with sensitive and private data, including maintaining a secure and confidential workspace; Experience with patient scheduling or registration is a plus; Experience with insurance eligibility verification is a plus; Prior experience in a medical or behavioral health setting is a plus; Experience using Zendesk or similar ticketing systems preferred; Experience with EHR or EMR systems is a plus; Experience with standard office productivity tools is a plus; Bilingual or multilingual proficiency is a plus; Must be eligible to work in the United States.
We could separate Requirements (education, eligibility) and Skills (technical/soft skills). But we can just have Requirements section with all bullet points. The instruction says we can have Qualifications, Skills sections if we want. But we prefer few substantive sections. So we can have About the role, Responsibilities, Requirements, Benefits. Possibly also Pay? The posting includes "Competitive hourly rate of 22.00-25.00 USD" under Benefits. That is pay info. Should we create a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay (hourly rate). However they also included pay within Benefits block. Should we separate Pay? The instruction says we can have Pay section. But we could also include pay within Benefits. The instruction says "Prefer a few substantive sections over many thin ones." So maybe combine pay into Benefits. Since they gave Benefits heading already, we can keep Benefits section and include pay as first bullet.
Schedule: The posting mentions part-time up to 25 hours per week, days and hours flexible within Monday-Friday 9 a.m.-5 p.m. That's schedule info. Should we create a Schedule section? The instruction says include a section only when posting has real, specific content for it. It does have schedule specifics. So we could create a Schedule section with that info. However we could also include schedule in About the role or Responsibilities? Probably better to have a Schedule section.
But we need to avoid filler like "commensurate with experience". Not present.
Thus sections: About the role (intro paragraph), Responsibilities (list), Requirements (list), Benefits (list including pay), Schedule (list or paragraph). Could also include Qualifications? But we have Requirements.
We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
As a Practice Support Specialist, you'll be part of our Practice Support team and the go-to person on site in our Clifton Park office. You'll help patients, referring partners, and internal staff get what they need by managing inquiries over the phone, by email, and through electronic ticketing, making sure questions are answered and requests are handled quickly and professionally. This part-time, in-person role is based in our Clifton Park office, for up to 25 hours per week. Days and hours are flexible but will be scheduled within Monday-Friday, 9 a.m.-5 p.m. Along with supporting patients and partners, you'll keep the office running smoothly by handling mail, keeping supplies stocked, and making sure the space stays organized. You'll also handle key support tasks such as verifying benefit eligibility, scheduling and rescheduling appointments, and assisting patients with registration and other needs. Training will be provided. This role is all about creating a welcoming, efficient, and supportive environment that makes it easy for patients and partners to get the help they need and ensures the office operates smoothly.
But note schedule info is also in this paragraph; maybe we should move schedule to its own section. However the About the role paragraph currently includes schedule. If we move schedule to its own section, we might duplicate. Better to keep schedule in About the role? But we also want a Schedule section. The instruction says prefer few substantive sections over many thin ones. If we split schedule out, we get more sections. Might be better to keep schedule in About the role and not create a separate Schedule section. However the schedule info is specific; but we can keep it in About the role. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having schedule info in About the role. So we can omit Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
Now Responsibilities: list duties: managing inquiries over phone, email, electronic ticketing; answering questions; handling requests quickly and professionally; handling mail; keeping supplies stocked; keeping space organized; verifying benefit eligibility; scheduling and rescheduling appointments; assisting patients with registration and other needs; creating a welcoming, efficient, supportive environment (maybe more of a goal). We'll list as bullet points.
Requirements: list as bullet points.
Benefits: list bullet points: Competitive hourly rate of 22.00-25.00 USD; Comprehensive Medical, Dental, and Vision plans available; Paid Time Off, Sick Time, and Paid Company Holidays; 401(k) Retirement Savings Program with 2% company match; Voluntary Life Insurance; Employee Assistance Program (EAP); Annual business-related expense stipend.
We should not include the "About Aptihealth" description? That's boilerplate? It's about the company, not required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Aptihealth" is not boilerplate but company description. Might be considered substantive? It's about the company mission. Could be included as "About the company" but not listed as allowed heading. The allowed headings list does not include About the company. But we could incorporate into About the role? Probably not needed. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Aptihealth paragraph is substantive about the company. Should we include it? The allowed headings do not have a specific heading for company overview, but we could use About Aptihealth
though not in the list. The list says e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It 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 could add About Aptihealth as a heading. However the instruction says "Prefer a few substantive sections over many thin ones." Adding another section may be okay if it's substantive. But we already have About the role; About Aptihealth is separate. Could we merge? The About the role paragraph already describes role; the company description is separate. Might be okay to include as a section.
But we need to decide. The instruction says "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." It doesn't forbid other headings.
Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, About Aptihealth.
But we need to avoid too many thin sections. About Aptihealth is a paragraph; we could make it a
under About the role? But
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 parse the posting. Content: - As a Practice Support Specialist, you'll be part of our Practice Support team and the go-to person on site in our Clifton Park office. You'll help patients, referring partners, and internal staff get what they need by managing inquiries over the phone, by email, and through electronic ticketing, making sure questions are answered and requests are handled quickly and professionally. This part-time, in-person role is based in our Clifton Park office, for up to 25 hours per week. Days and hours are flexible but will be scheduled within Monday-Friday, 9 a.m.-5 p.m. Along with supporting patients and partners, you'll keep the office running smoothly by handling mail, keeping supplies stocked, and making sure the space stays organized. You'll also handle key support tasks such as verifying benefit eligibility, scheduling and rescheduling appointments, and assisting patients with registration and other needs. Training will be provided. This role is all about creating a welcoming, efficient, and supportive environment that makes it easy for patients and partners to get the help they need and ensures the office operates smoothly. Then "Requirements" heading appears in the posting: "Requirements High School diploma or GED required; Associate degree strongly preferredExperience in a customer service or call center role a plus; training provided for candidates without direct experienceExcellent verbal and written communication skillsComfortable navigating multiple software platforms and web-based applicationsAbility to work in a HIPAA-compliant manner with sensitive and private data, including maintaining a secure and confidential workspaceExperience with patient scheduling or registration is a plusExperience with insurance eligibility verification is a plusPrior experience in a medical or behavioral health setting is a plusExperience using Zendesk or similar ticketing systems preferredExperience with EHR or EMR systems is a plusExperience with standard office productivity tools is a plusBilingual or multilingual proficiency is a plusMust be eligible to work in the United States" Then "Benefits" heading: "Benefits Competitive hourly rate of 22.00-25.00 USDComprehensive Medical, Dental, and Vision plans availablePaid Time Off, Sick Time, and Paid Company Holidays401(k) Retirement Savings Program with 2% company matchVoluntary Life InsuranceEmployee Assistance Program (EAP)Annual business-related expense stipend" Then "About Aptihealth" description. We need to decide sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (list of requirements), Benefits (list of benefits), maybe Skills? But we can combine Requirements and Skills? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections with real content. We have content for About the role (intro paragraph). Responsibilities: we have duties: managing inquiries over phone/email/ticketing, answering questions, handling requests quickly and professionally, handling mail, keeping supplies stocked, keeping space organized, verifying benefit eligibility, scheduling/rescheduling appointments, assisting patients with registration and other needs, training provided (maybe not a duty). Also "creating a welcoming, efficient, and supportive environment". We can list these as bullet points. Requirements: list of qualifications: High School diploma or GED required; Associate degree strongly preferred; Experience in a customer service or call center role a plus; training provided for candidates without direct experience; Excellent verbal and written communication skills; Comfortable navigating multiple software platforms and web-based applications; Ability to work in a HIPAA-compliant manner with sensitive and private data, including maintaining a secure and confidential workspace; Experience with patient scheduling or registration is a plus; Experience with insurance eligibility verification is a plus; Prior experience in a medical or behavioral health setting is a plus; Experience using Zendesk or similar ticketing systems preferred; Experience with EHR or EMR systems is a plus; Experience with standard office productivity tools is a plus; Bilingual or multilingual proficiency is a plus; Must be eligible to work in the United States. We could separate Requirements (education, eligibility) and Skills (technical/soft skills). But we can just have Requirements section with all bullet points. The instruction says we can have Qualifications, Skills sections if we want. But we prefer few substantive sections. So we can have About the role, Responsibilities, Requirements, Benefits. Possibly also Pay? The posting includes "Competitive hourly rate of 22.00-25.00 USD" under Benefits. That is pay info. Should we create a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay (hourly rate). However they also included pay within Benefits block. Should we separate Pay? The instruction says we can have Pay section. But we could also include pay within Benefits. The instruction says "Prefer a few substantive sections over many thin ones." So maybe combine pay into Benefits. Since they gave Benefits heading already, we can keep Benefits section and include pay as first bullet. Schedule: The posting mentions part-time up to 25 hours per week, days and hours flexible within Monday-Friday 9 a.m.-5 p.m. That's schedule info. Should we create a Schedule section? The instruction says include a section only when posting has real, specific content for it. It does have schedule specifics. So we could create a Schedule section with that info. However we could also include schedule in About the role or Responsibilities? Probably better to have a Schedule section. But we need to avoid filler like "commensurate with experience". Not present. Thus sections: About the role (intro paragraph), Responsibilities (list), Requirements (list), Benefits (list including pay), Schedule (list or paragraph). Could also include Qualifications? But we have Requirements. We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus:
About the role
As a Practice Support Specialist, you'll be part of our Practice Support team and the go-to person on site in our Clifton Park office. You'll help patients, referring partners, and internal staff get what they need by managing inquiries over the phone, by email, and through electronic ticketing, making sure questions are answered and requests are handled quickly and professionally. This part-time, in-person role is based in our Clifton Park office, for up to 25 hours per week. Days and hours are flexible but will be scheduled within Monday-Friday, 9 a.m.-5 p.m. Along with supporting patients and partners, you'll keep the office running smoothly by handling mail, keeping supplies stocked, and making sure the space stays organized. You'll also handle key support tasks such as verifying benefit eligibility, scheduling and rescheduling appointments, and assisting patients with registration and other needs. Training will be provided. This role is all about creating a welcoming, efficient, and supportive environment that makes it easy for patients and partners to get the help they need and ensures the office operates smoothly.
But note schedule info is also in this paragraph; maybe we should move schedule to its own section. However the About the role paragraph currently includes schedule. If we move schedule to its own section, we might duplicate. Better to keep schedule in About the role? But we also want a Schedule section. The instruction says prefer few substantive sections over many thin ones. If we split schedule out, we get more sections. Might be better to keep schedule in About the role and not create a separate Schedule section. However the schedule info is specific; but we can keep it in About the role. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having schedule info in About the role. So we can omit Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
Now Responsibilities: list duties: managing inquiries over phone, email, electronic ticketing; answering questions; handling requests quickly and professionally; handling mail; keeping supplies stocked; keeping space organized; verifying benefit eligibility; scheduling and rescheduling appointments; assisting patients with registration and other needs; creating a welcoming, efficient, supportive environment (maybe more of a goal). We'll list as bullet points.
Requirements: list as bullet points.
Benefits: list bullet points: Competitive hourly rate of 22.00-25.00 USD; Comprehensive Medical, Dental, and Vision plans available; Paid Time Off, Sick Time, and Paid Company Holidays; 401(k) Retirement Savings Program with 2% company match; Voluntary Life Insurance; Employee Assistance Program (EAP); Annual business-related expense stipend.
We should not include the "About Aptihealth" description? That's boilerplate? It's about the company, not required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Aptihealth" is not boilerplate but company description. Might be considered substantive? It's about the company mission. Could be included as "About the company" but not listed as allowed heading. The allowed headings list does not include About the company. But we could incorporate into About the role? Probably not needed. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Aptihealth paragraph is substantive about the company. Should we include it? The allowed headings do not have a specific heading for company overview, but we could use About Aptihealth
though not in the list. The list says e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It 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 could add About Aptihealth as a heading. However the instruction says "Prefer a few substantive sections over many thin ones." Adding another section may be okay if it's substantive. But we already have About the role; About Aptihealth is separate. Could we merge? The About the role paragraph already describes role; the company description is separate. Might be okay to include as a section.
But we need to decide. The instruction says "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." It doesn't forbid other headings.
Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, About Aptihealth.
But we need to avoid too many thin sections. About Aptihealth is a paragraph; we could make it a
under About the role? But
for prose. Thus:
About the role
As a Practice Support Specialist, you'll be part of our Practice Support team and the go-to person on site in our Clifton Park office. You'll help patients, referring partners, and internal staff get what they need by managing inquiries over the phone, by email, and through electronic ticketing, making sure questions are answered and requests are handled quickly and professionally. This part-time, in-person role is based in our Clifton Park office, for up to 25 hours per week. Days and hours are flexible but will be scheduled within Monday-Friday, 9 a.m.-5 p.m. Along with supporting patients and partners, you'll keep the office running smoothly by handling mail, keeping supplies stocked, and making sure the space stays organized. You'll also handle key support tasks such as verifying benefit eligibility, scheduling and rescheduling appointments, and assisting patients with registration and other needs. Training will be provided. This role is all about creating a welcoming, efficient, and supportive environment that makes it easy for patients and partners to get the help they need and ensures the office operates smoothly.
But note schedule info is also in this paragraph; maybe we should move schedule to its own section. However the About the role paragraph currently includes schedule. If we move schedule to its own section, we might duplicate. Better to keep schedule in About the role? But we also want a Schedule section. The instruction says prefer few substantive sections over many thin ones. If we split schedule out, we get more sections. Might be better to keep schedule in About the role and not create a separate Schedule section. However the schedule info is specific; but we can keep it in About the role. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having schedule info in About the role. So we can omit Schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits. Now Responsibilities: list duties: managing inquiries over phone, email, electronic ticketing; answering questions; handling requests quickly and professionally; handling mail; keeping supplies stocked; keeping space organized; verifying benefit eligibility; scheduling and rescheduling appointments; assisting patients with registration and other needs; creating a welcoming, efficient, supportive environment (maybe more of a goal). We'll list as bullet points. Requirements: list as bullet points. Benefits: list bullet points: Competitive hourly rate of 22.00-25.00 USD; Comprehensive Medical, Dental, and Vision plans available; Paid Time Off, Sick Time, and Paid Company Holidays; 401(k) Retirement Savings Program with 2% company match; Voluntary Life Insurance; Employee Assistance Program (EAP); Annual business-related expense stipend. We should not include the "About Aptihealth" description? That's boilerplate? It's about the company, not required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Aptihealth" is not boilerplate but company description. Might be considered substantive? It's about the company mission. Could be included as "About the company" but not listed as allowed heading. The allowed headings list does not include About the company. But we could incorporate into About the role? Probably not needed. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Aptihealth paragraph is substantive about the company. Should we include it? The allowed headings do not have a specific heading for company overview, but we could useAbout Aptihealth
though not in the list. The list says e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "usefor 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 could add About Aptihealth as a heading. However the instruction says "Prefer a few substantive sections over many thin ones." Adding another section may be okay if it's substantive. But we already have About the role; About Aptihealth is separate. Could we merge? The About the role paragraph already describes role; the company description is separate. Might be okay to include as a section. But we need to decide. The instruction says "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." It doesn't forbid other headings. Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, About Aptihealth. But we need to avoid too many thin sections. About Aptihealth is a paragraph; we could make it a
under About the role? But