Technical Customer Care Specialist I

We need to output HTML fragment with sections: About the role? The posting includes a description before Job Summary: "As the leading innovator...". That could be About the role or maybe About the company. The instruction: use

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. We need to include sections only if there is real content. We have: - About the role: maybe the introductory paragraph about Vitu and mission. That's substantive. - Responsibilities: there is a "Key Responsibilities" section with bullet-like sentences. We can put as

  • . - Requirements/Qualifications: there is "Minimum Qualifications And Experience" and "Preferred Experience". Could combine into Requirements and Qualifications? The instruction lists separate headings: Requirements, Qualifications, Skills. We can decide to use "Qualifications" for minimum qualifications and maybe "Preferred Experience" as part of Qualifications or Skills. But we need to avoid thin sections. Perhaps combine into one "Qualifications" section covering both minimum and preferred. Or separate if content is enough. - Skills: maybe not explicitly listed; we have "Excellent verbal and written communication skills", "Strong problem-solving and multitasking abilities", "Customer-focused attitude with patience and empathy", "Experience with support tools like Zendesk, Freshdesk, Salesforce, or similar platforms", "Familiarity with CRM systems and ticketing software". Those could be Skills. - Benefits: there is a paragraph about benefits: "We offer a comprehensive benefits package including - Healthcare Coverage ...". That's substantive. - Pay: there is "Compensation And Schedule" with hourly rate range $18.50 - $22.00. That's pay. - Schedule: also in same section: "Schedule will be: Monday - Thursday: 12-9pm EST and Saturdays 9-6 EST." So we need separate Pay and Schedule sections? The instruction says prefer a few substantive sections over many thin ones. But we have both pay and schedule specifics; they are separate headings allowed. Could combine into one "Compensation and Schedule" but headings list includes Pay and Schedule separate. However we can decide to make separate sections if content is substantive. Both are substantive. So we will include Pay and Schedule sections. We must not include boilerplate like EEO etc. Remove duplicated lines. Also remove "Applicants may reside in any US time zone but will work according to the one listed." That's part of schedule? It's schedule detail; we can include in Schedule section. Also remove "The final pay for this position will be determined by multiple factors including, but not limited to, location, education, experience, training and skills." That's pay detail; we can include in Pay section. Also remove "At Vitu, our engaged workforce is the key to our success..." that's fluff but maybe part of About the role? It's generic culture; could be considered boilerplate but it's about company culture. Might be considered not essential but it's substantive? It's generic but still about company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This culture paragraph is not exactly boilerplate but could be considered fluff. However we might keep it in About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's clearly boilerplate. It's not legal/EEO. It's about culture; could be considered substantive. We'll keep it. We need to output only HTML fragment, no /, no markdown fences. Structure:

    About the role

    ... (intro paragraph about Vitu, mission, offices)

    Responsibilities

    • ...
    ...

    Qualifications

    Minimum qualifications: ...

    Preferred experience: ...

    Or we could use
    for each. But we also have Skills section. Could combine skills into Qualifications? But we have separate heading Skills allowed. Let's make Skills section for the soft skills and tool familiarity. Thus:

    Skills

    • Excellent verbal and written communication skills
    • Strong problem-solving and multitasking abilities
    • Customer-focused attitude with patience and empathy
    • Experience with support tools like Zendesk, Freshdesk, Salesforce, or similar platforms
    • Familiarity with CRM systems and ticketing software
    Qualifications: Minimum qualifications and Preferred experience. We could do:

    Qualifications

    • High school diploma or equivalent; associate or bachelor’s degree in a related field is a plus.
    • 0–2 years of experience in customer support, technical support, or IT help desk.
    • Basic understanding of operating systems, networking, or software troubleshooting.

    Preferred experience with support tools like Zendesk, Freshdesk, Salesforce, or similar platforms; familiarity with CRM systems and ticketing software.

    But note we already listed those in Skills; duplication. Better to separate: Qualifications for education/experience; Skills for abilities/tools. Avoid duplication: The preferred experience with tools could be in Skills, not Qualifications. So Qualifications only education/experience. Thus: Qualifications: - High school diploma or equivalent; associate or bachelor’s degree in a related field is a plus. - 0–2 years of experience in customer support, technical support, or IT help desk. - Basic understanding of operating systems, networking, or software troubleshooting. Skills: - Excellent verbal and written communication skills - Strong problem-solving and multitasking abilities - Customer-focused attitude with patience and empathy - Experience with support tools like Zendesk, Freshdesk, Salesforce, or similar platforms - Familiarity with CRM systems and ticketing software Now Pay:

    Pay

    The hourly rate range for this position is $18.50 - $22.00. Final pay will be determined by multiple factors including location, education, experience, training, and skills.

    Schedule:

    Schedule

    Schedule will be: Monday - Thursday: 12-9pm EST and Saturdays 9-6 EST. Applicants may reside in any US time zone but will work according to the listed schedule.

    Benefits:

    Benefits

    • Healthcare Coverage for you and your family covering Medical, Dental & Vision
    • Tax Advantage accounts such as Health Savings Account (HSA) & Flexible Spending Accounts (FSA)
    • Generous PTO
    • Pet Insurance
    • Retirement Planning
    • ID Theft Insurance
    • Life and Disability Insurance
    • Commuter Benefits
    • Accident & Hospital, Critical Illness Insurance
    • Tuition Reimbursement
    We need to ensure we didn't include duplicated lines. The responsibilities section had duplicated lines: "Facilitate communication to other departments as needed to resolve client concerns." and "Provide proper follow- up to ensure the customer is kept apprised of the issue status." appeared twice. We should deduplicate. Let's extract responsibilities from the posting: Key Responsibilities: - The Technical Customer Care Specialist will be responsible for routine customer questions relating to product usage within [Business Unit], as well as technical support issues relating to the suite of products. - Leverage technical knowledge to deliver excellent care to clients while adhering to quality assurance standards. - Handle routine customer questions relating to product usage. - Provide technical support on issues through to resolution. - Maintains expert-level knowledge of [Business Unit] processes and procedures. - Accurately log all customer information in the CRM tool. - Facilitate communication to other departments as needed to resolve client concerns. - Communicate with key stakeholders to identify and resolve inquiries. - Provide proper follow-up to ensure the customer is kept apprised of the issue status. - Facilitate communication to other departments as needed to resolve client concerns. (duplicate) - Provide proper follow-up to ensure the customer is kept apprised of the issue status. (duplicate) We'll deduplicate. Thus responsibilities list: - Responsible for routine customer questions relating to product usage within [Business Unit], as well as technical support issues relating to the suite of products. - Leverage technical knowledge to deliver excellent care to clients while adhering to quality assurance standards. - Handle routine customer questions relating to product usage. - Provide technical support on issues through to resolution. - Maintain expert-level knowledge of [Business Unit] processes and procedures. - Accurately log all customer information in the CRM tool. - Facilitate communication to other departments as needed to resolve client concerns. - Communicate with key stakeholders to identify and resolve inquiries. - Provide proper follow-up to ensure the customer is kept apprised of the issue status. Now About the role: we need to include the introductory paragraph about Vitu and mission, plus maybe the offices list. The posting includes: "As the leading innovator in Vehicle-to-Government (V2Gov) technology, Vitu is transforming the way vehicles, businesses, government, and drivers interact with one another. Vitu provides innovative, cutting-edge services to the motor vehicle industry. Our namesake solution manages titling and registration transactions in all 50 states and across multiple locations — all on one platform. With the mission of expanding and automating Vehicle-to-Government (V2Gov) transactions, the Vitu platform is reimagining how drivers, businesses and governments interact with vehicles. Vitu has offices in California, Florida, Georgia, Illinois, Indiana, Kentucky, Minnesota, Montana, North Carolina, New Hampshire, New Jersey, New York, Ohio, Oregon, Pennsylvania, and Virginia." That's substantive. Also there is a "Job Summary" paragraph: "The Technical Customer Care Specialist will work directly with clients via Phone, E-mail, Chat and / or other electronic methods of communication to resolve their application and product issues. In addition, the Technical Customer Care Specialist will also be responsible for routine customer questions relating to product usage within [Business Unit], as well as technical support issues relating to the Vitu Automotive suite of products. This role is responsible for leveraging technical knowledge to deliver excellent care to clients while adhering to quality assurance standards." That could be part of About the role or Responsibilities. But we already have Responsibilities separate. The Job Summary is similar to responsibilities but we can incorporate into About the role as overview. However we must not duplicate content. We could keep About the role as the company description and mission, and maybe include the Job Summary as part of About the role? But the instruction says prefer few substantive sections over many thin ones. We could merge Job Summary into About the role to avoid thin Responsibilities? But Responsibilities already has substantive list. So we keep About the role as company description; we could also include the Job Summary as a brief overview under About the role. However that might duplicate some responsibilities content. But we can keep it as