Customer Support Analyst
About the Role
as section heading). Then we have responsibilities list (Essential Duties and Responsibilities). Then Qualifications list. Then Preferred Skills list. Then Benefits: "Competitive salary and benefits including medical, dental, vision, HSA/FSA, 401(k) with employer matching and education reimbursement." That's specific enough for Benefits section. Pay: Not explicitly stated; only "Competitive salary". That's vague but maybe considered not specific enough? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Competitive salary and benefits". That's not a specific number, but it's still stating that there is a competitive salary. Is that enough? The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive salary" is somewhat vague but still a statement. Might be considered acceptable? However they said "Prefer a few substantive sections over many thin ones." Might be okay to include Benefits and maybe not Pay because it's not a specific number. Schedule: they gave working hours: "7:30 AM – 4:30 PM EST or 10:00 AM–7:00 PM EST." That's specific. So we can include Schedule section. Thus sections: About the Role, Responsibilities, Qualifications, Preferred Skills (maybe as Skills), Benefits, Schedule. We must not include Pay. We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Our Core Values" maybe? It's not a required section but could be included? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Core Values is specific content but not a standard heading list; we could include as a section if we want, but not required. The instruction says prefer a few substantive sections over many thin ones. Could include Core Values as a section but maybe not needed. We'll stick to the standard headings.
We need to capture the "About the Role" prose: The paragraph after "About the Role". We'll put that in
.
Responsibilities: list items under Essential Duties and Responsibilities. We'll output
- each.
Qualifications: list items under Qualifications.
Preferred Skills: list under Preferred Skills.
Benefits: list items? The benefits sentence: "Competitive salary and benefits including medical, dental, vision, HSA/FSA, 401(k) with employer matching and education reimbursement." Could be a
or
- . Since it's a list of benefits, we can make
- Medical
etc. But we need to preserve all detail; we could keep as a but rule says use
- for any list of duties/requirements/benefits. So we should make a list.
Schedule: we have two shift options. Could be a
or
. Since it's a schedule, we can make with the two options.
We must not repeat job title as heading. Not include Job ID.
We must output only HTML fragment.
Let's craft:
About the Role
iScribeHealth is an AI-powered virtual scribe solution that helps healthcare providers efficiently document patient care and sync data with Electronic Health Records (EHR) systems. Founded in 2015, we are dedicated to reducing provider burnout and improving healthcare efficiency through cutting-edge AI and automation. Our mobile platform streamlines workflows, enabling doctors to focus on patient care while ensuring seamless EHR integration. At iScribeHealth, we empower our employees to make a meaningful impact, both for themselves and the patients we serve. The Customer Support Analyst serves as the frontline technical support for all customers using the iScribeHealth app and services. This client-facing role requires a professional who can swiftly and effectively address client concerns while building trust and maintaining strong relationships. The Analyst collaborates closely with the support and development teams to resolve technical issues and improve product functionality and escalates issues to Level 2 support as needed. This role requires proficiency in the iScribe product, troubleshooting capabilities, and the ability to identify and address inefficiencies in the system. This is a high-volume role. The successful candidate resolves a heavy daily flow of support tickets while staying composed and keeping momentum under sustained pressure. It suits a methodical, detail-oriented professional who is comfortable following defined processes and repetitive workflows, works independently once trained, and stays even-keeled in customer interactions. A clinical background is a significant advantage in understanding provider needs and moving quickly through issues. To meet our committed hours of support coverage, the working hours for this position are 7:30 AM – 4:30 PM EST or 10:00 AM–7:00 PM EST. The individual must be ready to promptly pickup calls, support tickets, and other requests at starting time, or adjust accordingly to align with coverage across other time zones.
But note we already have schedule info in that paragraph; we might separate schedule later. However we should not duplicate. The instruction: preserve ALL substantive information; we can keep schedule in About the Role paragraph and also have a Schedule section? That would duplicate. Better to keep schedule in its own section and remove from About the Role paragraph to avoid duplication. But we must preserve all info; we can move schedule details to Schedule section and keep About the Role paragraph without schedule. However the About the Role paragraph originally includes schedule sentence; we could edit it out but that would be removing info. We need to keep it somewhere. We could keep it in About the Role paragraph and not have a separate Schedule section, but we have schedule specifics; we could still make a Schedule section and keep the sentence in About the Role but maybe rephrase to avoid duplication? The rule says preserve ALL substantive information; duplication is not prohibited but we should avoid duplicated lines (they said remove duplicated lines). So we should not duplicate the same sentence. So we should either keep schedule in About the Role and not have a separate Schedule section, or move schedule to Schedule section and remove from About the Role. Which is better? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Schedule has real specific content, so we should include a Schedule section. Then we should not duplicate that content elsewhere. So we should remove the schedule sentence from About the Role paragraph.
Thus we need to edit About the Role paragraph to exclude the schedule sentence. Let's rewrite About the Role paragraph without that sentence.
Original About the Role paragraph includes: "To meet our committed hours of support coverage, the working hours for this position are 7:30 AM – 4:30 PM EST or 10:00 AM–7:00 PM EST. The individual must be ready to promptly pickup calls, support tickets, and other requests at starting time, or adjust accordingly to align with coverage across other time zones."
We'll remove those two sentences.
Now About the Role paragraph will be:
"iScribeHealth is an AI-powered virtual scribe solution that helps healthcare providers efficiently document patient care and sync data with Electronic Health Records (EHR) systems. Founded in 2015, we are dedicated to reducing provider burnout and improving healthcare efficiency through cutting-edge AI and automation. Our mobile platform streamlines workflows, enabling doctors to focus on patient care while ensuring seamless EHR integration. At iScribeHealth, we empower our employees to make a meaningful impact, both for themselves and the patients we serve. The Customer Support Analyst serves as the frontline technical support for all customers using the iScribeHealth app and services. This client-facing role requires a professional who can swiftly and effectively address client concerns while building trust and maintaining strong relationships. The Analyst collaborates closely with the support and development teams to resolve technical issues and improve product functionality and escalates issues to Level 2 support as needed. This role requires proficiency in the iScribe product, troubleshooting capabilities, and the ability to identify and address inefficiencies in the system. This is a high-volume role. The successful candidate resolves a heavy daily flow of support tickets while staying composed and keeping momentum under sustained pressure. It suits a methodical, detail-oriented professional who is comfortable following defined processes and repetitive workflows, works independently once trained, and stays even-keeled in customer interactions. A clinical background is a significant advantage in understanding provider needs and moving quickly through issues."
Now Responsibilities list: we need to capture each bullet under "Essential Duties and Responsibilities". Let's list them:
- Answer customer inquiries related to healthcare technology products and services.
- Provide prompt responses to a high volume of incoming calls, emails, and messages, ensuring timely and effective communication.
- Troubleshoot common software and hardware issues, including connectivity, login, and navigation concerns.
- Review and make customizations to provider AI prompts on the backend so that notes align with provider needs and information flows into the correct fields.
- Reprocess jobs through the AI engine as needed to optimize documentation accuracy.
- Assist providers in building and implementing macros within the product.
- Provide guidance on product features and assist with basic configuration.
- Follow scripts and templates for efficient handling of customer inquiries.
- Maintain detailed records of support cases within the Intercom system.
- Document customer interactions and escalate unresolved issues to Level 2 support as needed.
- Identify recurring issues and report trends to the Customer Support VP for review.
- Foster strong, professional relationships with clients and act as their advocate.
Now Qualifications list:
- Clinical background strongly preferred. Active or former CMA, RN, LPN, or other clinical experience, with clinics, emergency room, urgent care, ICU, or other high-acuity settings weighted most highly, both for clinical knowledge and for demonstrated composure in high-pressure, high-throughput environments.
- Proficiency with EMR or EHR systems, medical terminology, and healthcare industry regulations.
- Experience in customer support or technical support, preferably in the healthcare technology industry.
- Demonstrated ability to sustain focus, accuracy, and composure under a high daily volume of tickets and continuous pressure.
- Strong troubleshooting skills with the ability to diagnose and resolve software and hardware issues.
- Methodical, detail-oriented working style, comfortable following defined processes and repetitive workflows and self-directing once trained.
- Excellent written and verbal communication skills, with a calm, professional manner in confrontational or escalated interactions.
- Ability to multitask, prioritize, and manage time efficiently in a fast-paced environment.
- A customer-centric mindset with strong, independent problem-solving abilities, alongside the ability to collaborate effectively with cross-functional teams.
Now Preferred Skills list:
- Experience in healthcare IT support or electronic health records (EHR) systems.
- Enthusiasm for and curiosity about AI tools, and an understanding of AI-driven documentation processes.
- Comfort working within web-based SaaS platforms.
- Proficiency in using customer support software such as Intercom.
- Knowledge of scripting or macro-building within healthcare applications.
Now Benefits list: we have "Competitive salary and benefits including medical, dental, vision, HSA/FSA, 401(k) with employer matching and education reimbursement."
We can break into items: Competitive salary, Medical, Dental, Vision, HSA/FSA, 401(k) with employer matching, Education reimbursement.
But we need to preserve the phrase "Competitive salary and benefits including". Might be okay to list as separate items.
We'll make - Competitive salary
- Medical
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Our Core Values" maybe? It's not a required section but could be included? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Core Values is specific content but not a standard heading list; we could include as a section if we want, but not required. The instruction says prefer a few substantive sections over many thin ones. Could include Core Values as a section but maybe not needed. We'll stick to the standard headings. We need to capture the "About the Role" prose: The paragraph after "About the Role". We'll put that in
. Responsibilities: list items under Essential Duties and Responsibilities. We'll output
- each.
Qualifications: list items under Qualifications.
Preferred Skills: list under Preferred Skills.
Benefits: list items? The benefits sentence: "Competitive salary and benefits including medical, dental, vision, HSA/FSA, 401(k) with employer matching and education reimbursement." Could be a
or
- . Since it's a list of benefits, we can make
- Medical etc. But we need to preserve all detail; we could keep as a
- for any list of duties/requirements/benefits. So we should make a list.
Schedule: we have two shift options. Could be a
or
- . Since it's a schedule, we can make
- Competitive salary
- Medical
with the two options. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's craft:
About the Role
iScribeHealth is an AI-powered virtual scribe solution that helps healthcare providers efficiently document patient care and sync data with Electronic Health Records (EHR) systems. Founded in 2015, we are dedicated to reducing provider burnout and improving healthcare efficiency through cutting-edge AI and automation. Our mobile platform streamlines workflows, enabling doctors to focus on patient care while ensuring seamless EHR integration. At iScribeHealth, we empower our employees to make a meaningful impact, both for themselves and the patients we serve. The Customer Support Analyst serves as the frontline technical support for all customers using the iScribeHealth app and services. This client-facing role requires a professional who can swiftly and effectively address client concerns while building trust and maintaining strong relationships. The Analyst collaborates closely with the support and development teams to resolve technical issues and improve product functionality and escalates issues to Level 2 support as needed. This role requires proficiency in the iScribe product, troubleshooting capabilities, and the ability to identify and address inefficiencies in the system. This is a high-volume role. The successful candidate resolves a heavy daily flow of support tickets while staying composed and keeping momentum under sustained pressure. It suits a methodical, detail-oriented professional who is comfortable following defined processes and repetitive workflows, works independently once trained, and stays even-keeled in customer interactions. A clinical background is a significant advantage in understanding provider needs and moving quickly through issues. To meet our committed hours of support coverage, the working hours for this position are 7:30 AM – 4:30 PM EST or 10:00 AM–7:00 PM EST. The individual must be ready to promptly pickup calls, support tickets, and other requests at starting time, or adjust accordingly to align with coverage across other time zones.
But note we already have schedule info in that paragraph; we might separate schedule later. However we should not duplicate. The instruction: preserve ALL substantive information; we can keep schedule in About the Role paragraph and also have a Schedule section? That would duplicate. Better to keep schedule in its own section and remove from About the Role paragraph to avoid duplication. But we must preserve all info; we can move schedule details to Schedule section and keep About the Role paragraph without schedule. However the About the Role paragraph originally includes schedule sentence; we could edit it out but that would be removing info. We need to keep it somewhere. We could keep it in About the Role paragraph and not have a separate Schedule section, but we have schedule specifics; we could still make a Schedule section and keep the sentence in About the Role but maybe rephrase to avoid duplication? The rule says preserve ALL substantive information; duplication is not prohibited but we should avoid duplicated lines (they said remove duplicated lines). So we should not duplicate the same sentence. So we should either keep schedule in About the Role and not have a separate Schedule section, or move schedule to Schedule section and remove from About the Role. Which is better? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Schedule has real specific content, so we should include a Schedule section. Then we should not duplicate that content elsewhere. So we should remove the schedule sentence from About the Role paragraph. Thus we need to edit About the Role paragraph to exclude the schedule sentence. Let's rewrite About the Role paragraph without that sentence. Original About the Role paragraph includes: "To meet our committed hours of support coverage, the working hours for this position are 7:30 AM – 4:30 PM EST or 10:00 AM–7:00 PM EST. The individual must be ready to promptly pickup calls, support tickets, and other requests at starting time, or adjust accordingly to align with coverage across other time zones." We'll remove those two sentences. Now About the Role paragraph will be: "iScribeHealth is an AI-powered virtual scribe solution that helps healthcare providers efficiently document patient care and sync data with Electronic Health Records (EHR) systems. Founded in 2015, we are dedicated to reducing provider burnout and improving healthcare efficiency through cutting-edge AI and automation. Our mobile platform streamlines workflows, enabling doctors to focus on patient care while ensuring seamless EHR integration. At iScribeHealth, we empower our employees to make a meaningful impact, both for themselves and the patients we serve. The Customer Support Analyst serves as the frontline technical support for all customers using the iScribeHealth app and services. This client-facing role requires a professional who can swiftly and effectively address client concerns while building trust and maintaining strong relationships. The Analyst collaborates closely with the support and development teams to resolve technical issues and improve product functionality and escalates issues to Level 2 support as needed. This role requires proficiency in the iScribe product, troubleshooting capabilities, and the ability to identify and address inefficiencies in the system. This is a high-volume role. The successful candidate resolves a heavy daily flow of support tickets while staying composed and keeping momentum under sustained pressure. It suits a methodical, detail-oriented professional who is comfortable following defined processes and repetitive workflows, works independently once trained, and stays even-keeled in customer interactions. A clinical background is a significant advantage in understanding provider needs and moving quickly through issues." Now Responsibilities list: we need to capture each bullet under "Essential Duties and Responsibilities". Let's list them: - Answer customer inquiries related to healthcare technology products and services. - Provide prompt responses to a high volume of incoming calls, emails, and messages, ensuring timely and effective communication. - Troubleshoot common software and hardware issues, including connectivity, login, and navigation concerns. - Review and make customizations to provider AI prompts on the backend so that notes align with provider needs and information flows into the correct fields. - Reprocess jobs through the AI engine as needed to optimize documentation accuracy. - Assist providers in building and implementing macros within the product. - Provide guidance on product features and assist with basic configuration. - Follow scripts and templates for efficient handling of customer inquiries. - Maintain detailed records of support cases within the Intercom system. - Document customer interactions and escalate unresolved issues to Level 2 support as needed. - Identify recurring issues and report trends to the Customer Support VP for review. - Foster strong, professional relationships with clients and act as their advocate. Now Qualifications list: - Clinical background strongly preferred. Active or former CMA, RN, LPN, or other clinical experience, with clinics, emergency room, urgent care, ICU, or other high-acuity settings weighted most highly, both for clinical knowledge and for demonstrated composure in high-pressure, high-throughput environments. - Proficiency with EMR or EHR systems, medical terminology, and healthcare industry regulations. - Experience in customer support or technical support, preferably in the healthcare technology industry. - Demonstrated ability to sustain focus, accuracy, and composure under a high daily volume of tickets and continuous pressure. - Strong troubleshooting skills with the ability to diagnose and resolve software and hardware issues. - Methodical, detail-oriented working style, comfortable following defined processes and repetitive workflows and self-directing once trained. - Excellent written and verbal communication skills, with a calm, professional manner in confrontational or escalated interactions. - Ability to multitask, prioritize, and manage time efficiently in a fast-paced environment. - A customer-centric mindset with strong, independent problem-solving abilities, alongside the ability to collaborate effectively with cross-functional teams. Now Preferred Skills list: - Experience in healthcare IT support or electronic health records (EHR) systems. - Enthusiasm for and curiosity about AI tools, and an understanding of AI-driven documentation processes. - Comfort working within web-based SaaS platforms. - Proficiency in using customer support software such as Intercom. - Knowledge of scripting or macro-building within healthcare applications. Now Benefits list: we have "Competitive salary and benefits including medical, dental, vision, HSA/FSA, 401(k) with employer matching and education reimbursement." We can break into items: Competitive salary, Medical, Dental, Vision, HSA/FSA, 401(k) with employer matching, Education reimbursement. But we need to preserve the phrase "Competitive salary and benefits including". Might be okay to list as separate items. We'll make
but rule says use
- . Since it's a list of benefits, we can make