Account Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: Why Work at TicketManager (maybe About the role?), The Role, Responsibilities, Desired Skills and Experience, TicketManager Highlights (which includes location, compensation, benefits, etc). We must use

for section headings. 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. Preserve all substantive info. Remove boilerplate etc. No cookie/navigation/legal/EEO etc. There's none. We need to include sections only when posting has real specific content. So we need sections: About the role? The posting includes "Why Work at TicketManager" (culture). Could map to "About the role" maybe? But we have "The Role" heading. Use that as section heading. Also "Responsibilities" heading. "Desired Skills and Experience" heading. "TicketManager Highlights" could be broken into Benefits, Pay, Schedule, etc. The posting includes location, compensation, variable comp, reports to, work expectations, retirement, health benefits, time off, interview process, events, perks, recognition. We need to include sections only when content present. So we can have sections: About the role (maybe combine Why Work at TicketManager and The Role?), but we have separate headings: "Why Work at TicketManager" and "The Role". The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those exact headings, but we can also use other headings if they match content? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to map content to those standard headings. So we need to decide which sections to include: About the role (covers why work at TicketManager and the role description). Responsibilities (list). Requirements/Qualifications/Skills (desired skills and experience). Benefits (health benefits, retirement, PTO, perks). Pay (compensation). Schedule (work expectations: In-Office Monday-Friday). Possibly Location could be part of About the role or separate but not required. We should not create sections with filler like "not specified". So we include only those with content. Let's extract content: Why Work at TicketManager: paragraph about building technology, fast-growing profitable company, values ownership, collaboration, excellence, passionate about making work impactful and fun, excited about live events, cutting-edge tech, work that matters. The Role: description of Account Manager role, portfolio, responsibilities overview, career path, etc. Responsibilities: bullet list under Responsibilities heading with subpoints: Account Ownership & Customer Success, Adoption, Retention & Growth, Customer Business Reviews, Cross-Functional Account Management, Account Planning & CRM, Events & Customer Engagement. Each has multiple sentences. Desired Skills and Experience: list of bullet-like sentences (but not formatted as list). We'll convert to

  • . TicketManager Highlights: includes location, compensation, variable comp & commission eligibility, reports to, work expectations, retirement, health benefits, time off, interview process, events, perks, recognition. We need to map to sections: - About the role: combine Why Work at TicketManager and The Role? Might be too much but okay. Could split: About the role (why work) and Responsibilities separate. But we have The Role heading which is similar to About the role. I'd treat "Why Work at TicketManager" as About the role. And "The Role" as maybe also part of About the role? But we can't duplicate headings. Perhaps we can have About the role covering both why work and role overview. Then Responsibilities separate. Then Requirements/Skills separate. Then Benefits, Pay, Schedule. Let's craft:

    About the role

    Live events are fun... (Why Work at TicketManager paragraph) ... TicketManager is hiring an Account Manager (AM) to own and grow a portfolio of customers, primarily consisting of accounts at approximately $2,500 MRR and below. This is a customer-facing, revenue-focused role responsible for driving customer engagement, adoption, retention, expansion, and long-term value. The Account Manager is the entry point into TicketManager’s Customer Success career path and provides the foundation for growth into roles such as Retention Manager, Account Director, Strategic Director, and beyond. Account Managers will build the customer, product, and commercial expertise needed to take on increasingly complex and strategic accounts as they grow within the organization. As the primary relationship owner for their assigned book of business, the Account Manager will develop a strong understanding of each customer’s goals, drive adoption of TicketManager’s platform and services, monitor account health, identify opportunities for growth, and ensure customers continue to see measurable value from their partnership with TicketManager. This is a hands-on role for someone who wants to build a career in Customer Success and account management within a B2B SaaS environment. Success requires strong relationship-building skills, commercial instincts, organization, curiosity, and the ability to coordinate internal resources to deliver an exceptional customer experience.

    Then Responsibilities:

    Responsibilities

    • ... each bullet as separate
    • containing the sentences.
    We need to break each responsibility heading into its own
  • maybe with internal

    ? But instruction: use

    • for any list of duties/requirements/benefits. So each bullet can be an
    • containing the text (maybe multiple sentences). We'll keep as is. Responsibilities list: - Account Ownership & Customer Success: Own the day-to-day relationship and overall success of an assigned portfolio of customers, primarily consisting of accounts at approximately $2,500 MRR and below. Develop a strong understanding of each customer’s business objectives, TicketManager usage, key stakeholders, and opportunities to deliver greater value. Build trusted relationships with customer stakeholders and serve as the primary point of contact throughout the customer lifecycle. Maintain consistent customer engagement and ensure accounts receive proactive, high-quality communication and support. - Adoption, Retention & Growth: Drive adoption and utilization of TicketManager’s products and services across assigned accounts. Monitor account health, engagement, usage, and customer sentiment to identify potential risks and opportunities early. Develop and execute action plans to improve engagement, strengthen customer relationships, and increase long-term value. Identify upsell, cross-sell, and expansion opportunities across TicketManager’s product portfolio and partner with the appropriate Revenue team members to move opportunities forward. Support renewal readiness by maintaining strong customer relationships, documenting account health and value, and partnering closely with the Retention team throughout the renewal process. - Customer Business Reviews: Prepare and lead customer business reviews that demonstrate product usage, value delivered, and opportunities to strengthen the partnership. Use customer data, product usage, and account insights to provide recommendations and identify opportunities for increased adoption and value. Partner with internal teams to prepare account-specific materials and ensure follow-through on commitments and next steps. - Cross-Functional Account Management: Serve as the internal quarterback for assigned accounts, coordinating across Customer Support, Ticket Operations, Product, Sales, Retention, and other teams as needed. Proactively identify customer issues or risks, engage the appropriate internal resources, and maintain ownership through resolution. Ensure internal teams have the customer context and information needed to deliver a consistent experience. - Account Planning & CRM: Maintain accurate, up-to-date account records, customer contacts, activity, opportunities, risks, and next steps. Develop account plans for priority customers within the assigned portfolio. Maintain visibility into customer health, upcoming renewals, growth opportunities, and open issues. Demonstrate strong CRM hygiene and disciplined follow-through across the assigned book of business. - Events & Customer Engagement: Represent TicketManager with customers at live events, customer meetings, and TicketManager’s annual Partner Summit. Use in-person customer engagement to strengthen relationships, understand customer needs, and uncover opportunities to deliver additional value. Travel regularly to customer offices and live events as business needs require. Next, Desired Skills and Experience:

      Skills

      maybe? Or

      Qualifications

      . The instruction list includes Skills. We'll use

      Skills

      . Provide
      • each bullet. List items: - BA/BS degree required - 2–5+ years of professional experience in Customer Success, Account Management, B2B SaaS, client services, sales, or another customer-facing role. - Strong relationship-building skills with the ability to develop credibility and trust with customer stakeholders. - Customer-first mindset with a genuine interest in understanding business needs and helping customers achieve measurable outcomes. - Commercial mindset with an interest in developing skills across customer retention, renewals, upselling, and account growth. - Strong verbal and written communication skills with the confidence to lead customer conversations, meetings, and presentations. - Highly organized and able to effectively manage a portfolio of customers, competing priorities, follow-ups, and deadlines. - Proactive problem solver who takes ownership and follows issues through resolution. - Comfortable working cross-functionally and coordinating across multiple internal teams. - Ability to learn a SaaS platform and translate product capabilities into meaningful customer value. - Comfortable using customer data, product usage, and account insights to guide conversations and recommendations. - Growth-oriented and motivated to develop toward increasingly complex and strategic Customer Success and Account Management roles. - Willing and excited to travel and engage customers at offices, live events, and TicketManager programs. - Experience in B2B SaaS, ticketing, sports, events, hospitality, sponsorships, or enterprise services is a plus. Now Benefits:

        Benefits

        with
        • items: 401(k) Company Match, Medical, Dental, Vision & Chiropractic, Unlimited PTO, Quarterly live event credits, monthly happy hours, volunteering, Fun collaborative in-office culture with catered lunches and big company perks, Recognition: Inc. 5000 fastest-growing private company six years, Best Places to Work awards, 4.5 Glassdoor rating, Used by over 4,000 globally known companies including ~15% of Fortune 500. Some of these are more like perks/recognition but still benefits. We'll include them. Pay:

          Pay

          with

          maybe? It says use

          for prose. Compensation: $75,000-$100,000 Base Salary, Variable Compensation & Commission Eligibility. We'll put in

          . Schedule:

          Schedule

          with

          : Work Expectations: Role is In-Office, Monday-Friday. Location maybe not needed as separate section; could be included in About the role or Benefits? Not required. We must not include boilerplate like Interview Process etc? That's part of highlights but could be considered part of Benefits? It's not a benefit exactly but still info. The instruction: include a section ONLY when posting has real specific content. Interview process is specific content. Should we include it? Could be part of Benefits or maybe a separate section like "Process". But not in list of headings. Probably we can include it under Benefits or maybe under About the role? Safer to include as a separate section? The instruction says use those example headings but not limited to them? It says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we shouldn't invent others like "Interview Process". So we should fold interview process into maybe Benefits or About the role? It's not a benefit. Could be part of About the role? Not really. Could be omitted? But we must preserve ALL substantive information. So we need to include it somewhere. Perhaps we can include it under Benefits as a bullet: "Multistage interview process with senior leaders across TicketManager". That seems okay