Account Manager
TicketManager · Calabasas, CA · 1 mo ago
On-siteSales$75k–$100k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions. The posting includes sections: "Why Work at TicketManager", "The Role", "Responsibilities:", "Desired Skills and Experience:", "TicketManager Highlights:" which includes location, compensation, benefits, etc.
We need to map to allowed headings.
- About the role: could correspond to "The Role" description (the paragraph about role). Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions. The posting includes sections: "Why Work at TicketManager", "The Role", "Responsibilities:", "Desired Skills and Experience:", "TicketManager Highlights:" which includes location, compensation, benefits, etc.
We need to map to allowed headings.
- About the role: could correspond to "The Role" description (the paragraph about role). Use About the role
then
with that content. - Responsibilities: we have a list under "Responsibilities:" with subheadings (Account Ownership & Customer Success, Adoption, Retention & Growth, etc). We need to output
- for any list of duties/requirements/benefits. The responsibilities are multiple bullet-like paragraphs; we can treat each as a list item. Should we keep subheadings? Probably just list items. Could embed subheading as part of li text. We'll output
- ... each responsibility paragraph.
- Requirements: maybe "Desired Skills and Experience:" includes required qualifications: BA/BS degree required, 2–5+ years experience, etc. That's more like requirements/qualifications/skills. We need to decide sections: Requirements, Qualifications, Skills. The posting lumps them. We could split: Requirements (education, experience), Qualifications (maybe same), Skills (desired skills). But we must not create thin sections; better to combine into one section like "Requirements" covering education, experience, and maybe skills. However we have separate headings allowed; we need to include only when there is real specific content. We could have "Requirements" for education and experience, "Skills" for the skill list. But we need to avoid duplication. Let's examine content:
Desired Skills and Experience:
- 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...
- Customer-first mindset...
- Commercial mindset...
- Strong verbal and written communication skills...
- Highly organized...
- Proactive problem solver...
- Comfortable working cross-functionally...
- Ability to learn a SaaS platform...
- Comfortable using customer data...
- Growth-oriented...
- Willing and excited to travel...
- Experience in B2B SaaS, ticketing, sports, events, hospitality, sponsorships, or enterprise services is a plus.
Thus we can treat education and experience as Requirements, and the bullet list as Skills. Or we could have a single "Requirements" section containing both. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one section "Requirements" that includes education, experience, and skills. But we have also a separate "Skills" heading allowed; but we can skip if we combine.
We also have Benefits, Pay, Schedule sections from TicketManager Highlights: location, compensation, benefits, work expectations, retirement, health benefits, time off, perks, recognition, etc. We need to include Pay (compensation), Benefits (health, retirement, PTO, perks), Schedule (Work Expectations: Role is In-Office, Monday-Friday). Also location maybe not needed but could be part of About the role? Not required. We'll include location maybe in About the role? Not needed. We'll keep location maybe as a short paragraph under About the role? But we must not invent. The location is in TicketManager Highlights: "Location: Calabasas, CA (HQ) or New York, NY". That's substantive; we could include it in About the role or a separate section like "Location". But location not among allowed headings. So we could fold it into About the role paragraph.
Thus sections:
- About the role: include description of role from "The Role" paragraph plus maybe location.
- Responsibilities: list of responsibilities.
- Requirements: education + experience.
- Skills: list of desired skills.
- Benefits: health benefits, retirement, PTO, perks, recognition, etc.
- Pay: compensation range.
- Schedule: work expectations (In-Office, Monday-Friday).
We must not include sections with filler like "commensurate with experience". We have specific content.
Now we need to output HTML fragment only, no markdown fences.
We'll produce:
About the role
... (combined role description + location)
Responsibilities
- ... ...
Requirements
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.
Skills
- 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.
Benefits
- 401(k) Company Match
- Medical, Dental, Vision & Chiropractic health benefits
- Unlimited PTO
- Quarterly live event credits, monthly happy hours, and volunteering opportunities
- Fun, collaborative, in-office culture with catered lunches and big company perks
- Recognized as Inc. 5000 fastest-growing private company six years in a row; Best Places to Work by Inc. Magazine, LA Business Journal, Sports Business Journal; 4.5 Glassdoor rating; used by over 4,000 globally known companies including ~15% of Fortune 500
Pay
$75,000-$100,000 Base Salary; Variable Compensation & Commission Eligibility
Schedule
Role is In-Office, Monday-Friday
Check for any duplicated lines: we removed boilerplate like "Why Work at TicketManager" etc. We kept the role description. Did we preserve all substantive info? Let's verify. Original role description 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." We need to include that in About the role. Also we added location. Good. Responsibilities: we need to capture each bullet under Responsibilities: The original had headings: Account Ownership & Customer Success, Adoption, Retention & Growth, Customer Business Reviews, Cross-Functional Account Management, Account Planning & CRM, Events & Customer Engagement. Each with paragraphs. We'll combine each paragraph into a list item. Ensure we keep all details. Let's extract each: 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. We'll put each bullet as separate - . Could group under subheadings but not needed. Now Requirements: we have education and experience. Also maybe "Desired Skills and Experience:" includes BA/BS degree required and 2–5+ years experience. That's it. Skills: we have the list of desired skills (the bullet points after the experience line). We'll list them as above. Ben
- ... each responsibility paragraph.
- Requirements: maybe "Desired Skills and Experience:" includes required qualifications: BA/BS degree required, 2–5+ years experience, etc. That's more like requirements/qualifications/skills. We need to decide sections: Requirements, Qualifications, Skills. The posting lumps them. We could split: Requirements (education, experience), Qualifications (maybe same), Skills (desired skills). But we must not create thin sections; better to combine into one section like "Requirements" covering education, experience, and maybe skills. However we have separate headings allowed; we need to include only when there is real specific content. We could have "Requirements" for education and experience, "Skills" for the skill list. But we need to avoid duplication. Let's examine content:
Desired Skills and Experience:
- 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...
- Customer-first mindset...
- Commercial mindset...
- Strong verbal and written communication skills...
- Highly organized...
- Proactive problem solver...
- Comfortable working cross-functionally...
- Ability to learn a SaaS platform...
- Comfortable using customer data...
- Growth-oriented...
- Willing and excited to travel...
- Experience in B2B SaaS, ticketing, sports, events, hospitality, sponsorships, or enterprise services is a plus.
Thus we can treat education and experience as Requirements, and the bullet list as Skills. Or we could have a single "Requirements" section containing both. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one section "Requirements" that includes education, experience, and skills. But we have also a separate "Skills" heading allowed; but we can skip if we combine.
We also have Benefits, Pay, Schedule sections from TicketManager Highlights: location, compensation, benefits, work expectations, retirement, health benefits, time off, perks, recognition, etc. We need to include Pay (compensation), Benefits (health, retirement, PTO, perks), Schedule (Work Expectations: Role is In-Office, Monday-Friday). Also location maybe not needed but could be part of About the role? Not required. We'll include location maybe in About the role? Not needed. We'll keep location maybe as a short paragraph under About the role? But we must not invent. The location is in TicketManager Highlights: "Location: Calabasas, CA (HQ) or New York, NY". That's substantive; we could include it in About the role or a separate section like "Location". But location not among allowed headings. So we could fold it into About the role paragraph.
Thus sections:
- About the role: include description of role from "The Role" paragraph plus maybe location.
- Responsibilities: list of responsibilities.
- Requirements: education + experience.
- Skills: list of desired skills.
- Benefits: health benefits, retirement, PTO, perks, recognition, etc.
- Pay: compensation range.
- Schedule: work expectations (In-Office, Monday-Friday).
We must not include sections with filler like "commensurate with experience". We have specific content.
Now we need to output HTML fragment only, no markdown fences.
We'll produce: