Client Care Advisor - Fort Worth

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the Role: paragraph describing role. - About the Team: maybe not a required heading; but we could include as part of About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if present. The posting includes "About the Role:" and "About the Team:" and then bullet list "As a Client Care Advisor at Honor, you will:" which are responsibilities. Then "We’re looking for you to bring:" which are requirements/qualifications. Then "Leadership Principles:" maybe not needed. Then EEO boilerplate. We need to decide what goes where. Responsibilities: bullet list after "As a Client Care Advisor at Honor, you will:" includes items. Requirements/Qualifications/Skills: The "We’re looking for you to bring:" list includes experience, abilities, etc. Could be split into Requirements (experience) and Qualifications (preferred) and Skills (specific abilities). But we can combine if content is thin. However instruction: prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (combining experience, qualifications, skills), Pay, Schedule (travel). Benefits maybe not mentioned explicitly; there is no benefits section. Pay: they mention annual on-target earnings $72,000–$80,000, with 20% tied to uncapped monthly commission. That's pay info. Schedule: they mention ~75+% travel in the field across Bexar County, with reliable transportation and flexibility for evenings/weekends as customer needs arise. Also ability to spend ~75% of time in the field, with reliable transportation and flexibility for occasional evenings/weekends. That's schedule/travel. Thus we can have sections: About the role, Responsibilities, Requirements, Pay, Schedule. We should not include Benefits if not present. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting. Let's extract prose for About the role: The paragraph(s) under "About the Role:" up to before "About the Team:" maybe. Original: "About the Role: The Client Care Advisor plays a critical role in helping families navigate one of the most important decisions they’ll make: choosing the right care for a loved one. This role combines consultative sales, care coordination, and ongoing relationship management to guide families from initial inquiry through service start and beyond. You will lead high-quality consultations to understand each client’s needs, urgency, and readiness, and translate that into clear, appropriate care plans. You are accountable for moving families from inquiry to start, while ensuring a smooth onboarding experience and strong ongoing engagement. Beyond the initial decision, you will stay closely connected to clients and families, conducting reassessments, ensuring service quality, and adapting care as needs evolve. You will partner with scheduling and operations teams to ensure reliable execution, while maintaining high standards for documentation and compliance. Success in this role is measured by consult-to-start conversion, client satisfaction, and long-term retention. High performers combine empathy and strong judgment with a results orientation — building trust quickly, creating appropriate urgency, and helping families take action with confidence. This role includes significant time in the field, including in-person consultations, service starts, and quality visits. It also requires navigating sensitive family dynamics, urgent needs, and occasional after-hours situations" Then "This role requires ~75+% travel in the field across Bexar County, with reliable transportation and flexibility for evenings/weekends as customer needs arise." This is schedule/travel. Then "This role offers annual on-target earnings of $72,000–$80,000, with 20% tied to uncapped monthly commission." That's pay. Then "About the Team: Honor’s Owned & Operated (O&O) team runs company-owned markets, serving clients directly while also helping shape how care is delivered across the broader network. O&O is where new ideas are tested, processes are refined, and best practices are developed before being shared more widely. Working in O&O means being close to both clients and execution, with the opportunity to influence how operations, consultations, and service quality evolve at scale. It’s a fast-moving environment that blends hands-on impact with the chance to help define the future of home care with Honor." That could be part of About the role or separate but we don't have a heading for About the Team; we could incorporate into About the role as extra prose. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It says "include a section ONLY when the posting has real, specific content for it". So we could add About the team as part of About the role or maybe we could add a separate section but not in list; but better to keep to allowed headings. We'll incorporate About the team into About the role prose. Now Responsibilities: bullet list after "As a Client Care Advisor at Honor, you will:" includes: - Own consult-to-start conversion by conducting high-quality consultations and proactively guiding families to timely decisions - Lead successful service starts by aligning expectations, coordinating care setup, and mitigating onboarding risks - Drive retention and growth through ongoing client engagement, reassessments, and care plan adjustments - Serve as a trusted advisor to families, helping them navigate complex care decisions with clarity and confidence - Partner cross-functionally with scheduling, operations, and Care Pros to ensure consistent, high-quality service delivery - Use data and systems to manage your portfolio, track performance, and maintain accurate documentation - Contribute to referral relationship growth and local market reputation as needed These are duties. Now Requirements/Qualifications/Skills: The "We’re looking for you to bring:" list includes: - 1+ year of experience in a consultative, client-facing role (e.g., healthcare, senior care, social work, care coordination, or similar) - Demonstrated ability to guide clients through decisions and drive measurable outcomes (e.g., conversion, retention, service adoption) - Strong relationship management skills, with experience supporting clients and families over time and adapting to evolving needs - Experience owning measurable client outcomes. Examples include consult-to-start conversion, client retention, service adoption, or other performance metrics. - Experience leading structured conversations (discovery, needs assessment, recommendations, next steps) - Ability to partner cross-functionally to deliver services effectively and resolve execution challenges - Comfort working within structured systems and tools (e.g., CRM, documentation standards, defined consult frameworks, Microsoft Office, Salesforce or similar) - Operational discipline, including managing follow-up, tracking performance, and maintaining accurate records - Ability to spend ~75% of time in the field, with reliable transportation and flexibility for occasional evenings/weekends. - Experience working with older adults and families or a background in Healthcare Administration, Social Work, Gerontology, or a related field is preferred We could split: Requirements (experience) and Qualifications (preferred) and Skills (abilities). But to avoid many thin sections, we could combine into Requirements (including experience, skills, abilities) and maybe Qualifications for preferred background. However we have a specific "preferred" line. Could treat as Qualifications. Thus we could have: - Requirements: bullet list of the first 8 items (experience, ability to guide, relationship management, owning outcomes, leading conversations, partner cross-functionally, comfort with systems, operational discipline). Also maybe include ability to spend 75% time in field (that's schedule but also a requirement). But schedule already covered. - Qualifications: bullet list of the preferred background: Experience working with older adults and families or a background in Healthcare Administration, Social Work, Gerontology, or a related field is preferred. But we also have Leadership Principles section; but that's not a required heading; we could omit as it's more generic. It's substantive but not fitting headings; we could incorporate into About the role maybe. However it's a list of principles; but we could drop as it's not directly about role? It's about leadership principles relevant to role. Might be considered part of Requirements? But it's not a requirement; it's description of culture. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info. Where to put? Could add a section "Leadership Principles" but not in allowed headings list. However instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It might be okay to add other headings if needed, but better to stick to those. However we could incorporate Leadership Principles into About the role or Requirements as prose. But it's a list of principles; we could turn into a

  under a

  maybe "Leadership Principles". But that deviates from instruction. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for those sections; but we could also use other headings if needed? The safer approach is to only use those headings. So we need to fit Leadership Principles content somewhere else, maybe under About the role as prose. We can embed a paragraph summarizing the leadership principles: "Honor’s Leadership Principles are the foundation of translating our mission into action. These principles define how we show up and make decisions, and how we hire, develop and grow talent. While Honor has 13 leadership principles, the following are particularly relevant to this role: Relentlessly Focus on Clients, Build Trust, Drive Impact." Then we could list them as a

  . That preserves detail. Thus we can have a section maybe "Leadership Principles" but not in list; but we could incorporate under About the role as a subsection? But we must not create extra headings beyond allowed? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but it's implied to use those for those sections. To be safe, we could add a

  for Leadership Principles? Might be considered violating. Better to embed within About the role as a

  and maybe a

  inside that

  ? But

  cannot be inside

  . Could put after the

  . But then we need a heading? Could just put the list directly after the paragraph without a heading; but that might be odd. However we can include a

  for Leadership Principles as it's a section; the instruction didn't forbid; it just gave examples. I'd assume it's okay to use other headings if needed, but the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be read as "when you need a section heading, use

  " and those are examples of possible sections. So we can use

  for any section heading we need