Community & Customer Experience Lead (For Pooling) | Philippines

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract content. Let's parse the description. First paragraph: "At Peak Support, we are passionate about delivering exceptional service to our customers and clients. As a rapidly growing services provider, we offer a wide range of services including customer support, sales operations, and business process outsourcing to high-growth companies. Our commitment to providing outstanding customer experience and supporting our clients as they grow and scale is at the heart of everything we do." That's about the company, could be "About the role" or "About the company". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and put that prose. Next: "We’re Looking For a Community & Customer Experience Lead Who Will Own Two Closely Connected Areas Of a Mission-driven Food Company Community & Influencers: Building relationships with creators, influencers, customers, ambassadors, partners, and people who genuinely connect with what the company stands for.Customer Experience: Making sure customers receive fast, thoughtful, helpful support and that what we learn from customers gets communicated back into the business." That's description of role. Could be part of About the role or Responsibilities. We'll treat as part of About the role. Then sections: "Community, Creators & Influencers" bullet list of duties. Then "Customer Support & Experience" bullet list. Then "Building Community" prose. Then "AI, Automation & Tools" prose. Then "From Execution to Leadership" prose. Then "What Success Looks Like" prose. Then "Peak Support and our Work-from-Home PLUS model" prose about benefits? Might be Benefits section. Then "Requirements" heading with bullet list. Then "Expectations & Accountability" bullet list. Then note about pooling status (maybe drop as boilerplate? It's application instruction? It says note about pooling status, we should remove application instructions. Likely drop. We need to decide sections: About the role, Responsibilities, Requirements, Expectations (maybe Skills?), Benefits? The posting mentions Work-from-Home PLUS model, Glassdoor rating, remote work, etc. That's benefits. So we can have Benefits section. We should not create Pay or Schedule sections because no specific pay or schedule info. We need to preserve all substantive information, not invent. We need to use

  • for any list of duties/requirements/benefits. So for each list we need
    • . We need to use

      for prose. We must not repeat job title as heading. We must not include boilerplate like EEO etc. There's none. We must not include duplicated lines. Let's extract content. First, About the role: combine first paragraph and the "We’re Looking For..." paragraph. Prose: "At Peak Support, we are passionate about delivering exceptional service to our customers and clients. As a rapidly growing services provider, we offer a wide range of services including customer support, sales operations, and business process outsourcing to high-growth companies. Our commitment to providing outstanding customer experience and supporting our clients as they grow and scale is at the heart of everything we do. We’re Looking For a Community & Customer Experience Lead Who Will Own Two Closely Connected Areas Of a Mission-driven Food Company Community & Influencers: Building relationships with creators, influencers, customers, ambassadors, partners, and people who genuinely connect with what the company stands for. Customer Experience: Making sure customers receive fast, thoughtful, helpful support and that what we learn from customers gets communicated back into the business." We can keep as one

      . Next, Responsibilities: we have multiple sub-sections: Community, Creators & Influencers; Customer Support & Experience; Building Community; AI, Automation & Tools; From Execution to Leadership; What Success Looks Like. Could combine all responsibilities under one Responsibilities section with lists and prose. But we need to use

      • for any list of duties/requirements/benefits. So we need to identify lists. Community, Creators & Influencers list: - Identify and recruit creators, influencers, affiliates, ambassadors, and potential brand advocates - Build genuine, long-term relationships rather than relying only on transactional influencer campaigns - Manage outreach, product seeding, follow-ups, communication, and ongoing relationships - Develop systems for consistently finding and engaging new creators - Encourage and organize user-generated content, testimonials, reviews, and customer stories - Engage with our community across social channels and other relevant platforms - Identify highly engaged customers who could become advocates for the brand - Develop programs and initiatives that give people reasons to participate in and share the brand community - Track relationships, outreach, content, and results Customer Support & Experience list: - Initially handle customer support directly across our primary customer channels - Respond quickly, professionally, and empathetically to customer questions and problems - Resolve issues while protecting and strengthening the customer relationship - Identify recurring questions and problems and develop systems to address them - Build FAQs, templates, workflows, and processes that improve response quality and speed - Collect customer feedback and communicate important insights back to marketing, operations, product, and leadership - Look for opportunities to turn great customer experiences into reviews, referrals, testimonials, and long-term relationships Building Community prose: "Community is more than social media and influencer outreach. We’re looking for someone who can build genuine connections, spark conversations, identify brand advocates, and turn customers into an engaged community around shared interests, values, and the brand’s mission. Our community includes allergy-aware families, people interested in gut health and clean nutrition, active individuals and athletes, parents, creators, and people who connect with our social mission. The goal is to bring these people closer to the brand and to one another." AI, Automation & Tools prose: "We expect this person to actively use AI and modern tools for creator research, outreach personalization, customer-support workflows, response drafting, CRM and relationship management, follow-up systems, feedback analysis, reporting, and documentation. AI should make you more effective at building relationships. It should never make those relationships feel automated. You must be able to recognize when a situation requires human judgment, empathy, creativity, or a personal response." From Execution to Leadership prose: "This is initially a hands-on role, with the opportunity to grow into managing a small team. As the company grows, you’ll lead functions across customer support, creator and influencer outreach, community engagement, and affiliate and ambassador relationships. You’ll also build processes, systems, and expectations while eventually training and managing team members. We’re looking for someone who can build and grow the function from the ground up." What Success Looks Like prose: "Success means building an engaged community, strengthening creator and customer relationships, and delivering an excellent customer experience. Over time, this includes increasing advocacy, reviews, referrals, and user-generated content while improving support, systems, and processes. Most importantly, we want someone who genuinely enjoys building relationships and can scale the function without losing the personal connection." We could treat these as responsibilities. Now Benefits: "Peak Support and our Work-from-Home PLUS model At Peak Support, we are dedicated to providing exceptional service to our clients and an exceptional work environment for our team members. We don’t do this with ping pong tables or video games. We do it by creating a positive, encouraging and performance-driven culture that enables our team members to build rewarding, long-term careers. We’re proud that our Glassdoor rating of 4.5 is the highest in the Business Process Outsourcing industry. Peak Support offers all the convenience of working from home, with the benefits of working for an established organization with an exceptional team and tremendous opportunities for growth. Peak Support has been 100% remote since day one, so we have built a culture and a set of processes that support the success of our remote team members." That's benefits. Now Requirements: bullet list under "What We’re Looking For". Let's extract: - Strong written and verbal communication skills - Experience with community building, influencer/creator relationships, customer experience, or related work - Genuine enjoyment of communicating and building relationships with people - Strong understanding of social media and creator ecosystems - Ability to communicate professionally while still sounding human - Strong organizational, follow-up, and problem-solving skills - Comfortable using AI, automation, CRM, and modern productivity tools - Ability to create systems, improve processes, and learn new technology quickly - Able to work independently without constant direction - Potential and desire to eventually manage a small team - Experience with food, wellness, CPG, ecommerce, nutrition, or mission-driven consumer brands is a plus Also there is "Expectations & Accountability" bullet list: - Follow through consistently and communicate proactively - Respond to customers and partners in a timely manner - Treat every customer interaction as an opportunity to strengthen the relationship - Build relationships rather than simply send outreach - Keep systems, records, and follow-ups organized - Bring ideas and solutions rather than waiting for instructions - Use AI and tools intelligently without becoming dependent on them - Identify opportunities to improve systems and processes - Learn from results and continually improve - Work with urgency while maintaining quality, empathy, and attention to detail We could treat Expectations as part of Responsibilities or separate section like "Expectations". The instruction says we can use headings like Skills, Benefits, Pay, Schedule. Expectations not listed but we could still use a heading if content exists. However they said "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we might combine Expectations into Responsibilities or Skills. But Expectations are more about how to work, could be considered Skills? Might be better to have a separate section "Expectations". However to keep few sections, we could merge Expectations into Responsibilities as additional bullet list. But we need to use

        • for any list of duties/requirements/benefits. Expectations is a list of expectations, could be considered duties. So we can include under Responsibilities. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to output HTML fragment only. Structure:

          About the role

          ... prose ...

          Responsibilities

          Then we need to include lists and prose. Could combine multiple

          and

          . We have prose sections: Building Community, AI, Automation & Tools, From Execution to Leadership, What Success Looks Like. Those are prose. We'll put each as

          . We also have two lists: Community, Creators & Influencers; Customer Support & Experience. Thus under Responsibilities we will have:

          Community, Creators & Influencers

          ? Actually heading inside responsibilities maybe not needed; we can just have the list preceded by a brief intro? But we can just output the list directly. However we need to preserve the subsection headings? The instruction says use

          for section headings (e.g. About the role, Responsibilities...). It didn't forbid using other headings like

          but we should avoid extra headings? Not specified. Safer to not add extra headings inside; just present the content. Thus we can do:

          Responsibilities

          • Identify and recruit creators, influencers, affiliates, amb