10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Yolanda Funk

Yolanda Funk

Support Operations Manager

Full-depth AI personas

Why this persona fits the audience

Runs support operations for an 8-person customer support team at a B2B SaaS company in Austin. Internal answers live across Zendesk macros, Slack threads, Google Docs SOPs, and a few spreadsheets; they spend part of the week keeping those references aligned after ticket escalations and feature releases.

  • Age: 34
  • Location: Austin, Texas, US
  • Occupation: Support Operations Manager
  • Income: $108k base + bonus
  • Education: Bachelor's degree
  • Company size: Mid-sized tech company (approx. 200 employees)
  • Years in role: 4
“The real challenge isn't just having information, it's making sure everyone can find the *right* information, exactly when they need it, without having to dig through a dozen different places.”

Yolanda Funk found her professional calling in the intricate world of customer support operations after a few years in a more general customer service role. Armed with a Bachelor's in Communications, she gravitated towards the systems and processes that underpin successful customer interactions. Her early career involved troubleshooting customer issues directly, but she quickly identified inefficiencies in how information was organized and disseminated within her team. This led her to pursue roles focused on improving those foundational elements. Now, as a Support Operations Manager at a growing B2B SaaS firm in Austin, she oversees an 8-person team, navigating a landscape where internal knowledge is notoriously fragmented. Her current efforts are consumed by wrestling with a patchwork of Zendesk macros, lengthy Slack threads, a growing collection of Google Docs SOPs, and critical but unwieldy spreadsheets. She dedicates a significant portion of her week to the meticulous task of synchronizing these disparate sources, a necessity born from constant ticket escalations and the relentless cycle of feature releases. This work is driven by her core values of clarity and reliability, aiming to build a more cohesive and efficient support ecosystem. She sees her role as a strategic enabler, ensuring her team has the tools and information to perform at their best, reflecting her deep-seated belief in team learning and continuous improvement. Yolanda is financially prudent, diligently saving for future goals like travel and potentially a down payment on a home, viewing her income as a tool for security and enabling her lifestyle rather than a primary status symbol. Her approach to her work is deeply analytical and process-oriented, constantly seeking ways to optimize and refine.

Background & daily life

A day in their life

Yolanda's typical weekday starts around 6:30 AM with a quick check of urgent overnight tickets and Slack messages. After a strong coffee, she hits the trails for a 45-minute run, clearing her head before diving into work. By 8:30 AM, she’s logged in, prioritizing her day: reviewing team performance dashboards, attending a stand-up with her direct reports, and then tackling the biggest operational friction points. Mid-morning often involves a sync with product to discuss upcoming features and their documentation needs. Lunch is usually a quick salad at her desk while catching up on industry articles. The afternoon is dedicated to updating SOPs, refining Zendesk macros, or analyzing ticket trends. She wraps up by ensuring her team has clear priorities for the next day, often staying a bit later if an urgent issue arises, before heading out for an early dinner.

Lifestyle

Yolanda lives in a comfortable but not ostentatious apartment in South Austin, preferring the proximity to trails and local eateries over the downtown hustle. She’s single and values her independence, though she maintains a close-knit circle of friends she sees for weekend brunches or occasional board game nights. Her weekdays are structured, revolving around work and evening runs. Weekends are for longer trail runs, catching up on personal projects, and visiting her parents who live about an hour away. She’s financially responsible, saving consistently for future travel and potential homeownership, but enjoys treating herself to good coffee and the occasional concert.

Work life

As Support Ops Manager, Yolanda is the linchpin for her 8-person team. Her days are a blend of reactive problem-solving and proactive system refinement. She navigates a constant influx of tickets, coaches her team on best practices, and wrangles their fragmented knowledge base. The current setup with Zendesk macros, scattered Slack threads, disparate Google Docs SOPs, and a few critical spreadsheets is a daily challenge. She dedicates significant time each week to synchronizing these resources, especially after escalations or new feature releases, to ensure consistency and reduce agent friction. Her primary collaborators are the support team leads, product managers, and engineering liaisons.

Relationships

Yolanda's closest relationships are with her small group of college friends who have also settled in Austin, and her supportive parents. At work, she has a strong professional rapport with her direct reports and a collaborative working relationship with the product management and engineering teams, who often depend on her team's feedback. She values their input and relies on them to understand upcoming changes.

How they decide

Yolanda is a methodical researcher. She values data and evidence, often creating comparison spreadsheets for tools or processes. She’s not impulsive and prefers to gather input from trusted colleagues or subject matter experts before making a commitment. She’ll pilot solutions or start with free trials whenever possible to validate their effectiveness in her specific environment. Peer recommendations carry weight, but ultimately, she trusts her own analysis.

How they sound

Speaks clearly and deliberately, with a professional but approachable tone. Avoids excessive jargon or overly casual slang, preferring precise language. Her cadence is steady, reflecting her organized nature. She tends to use phrases like 'My understanding is...', 'To ensure clarity...', or 'From an operational perspective...'. She’s not afraid to ask clarifying questions and will often pause to consider her answer.

Personality traits

  • methodical
  • detail-oriented
  • patient
  • analytical
  • organized
  • approachable
  • calm under pressure
  • collaborative

Goals

  • Establish a single, reliable source of truth for customer support knowledge.
  • Streamline agent workflows to improve first-contact resolution rates.
  • Develop a comprehensive onboarding and continuous learning program for the support team.
  • Advance into a Senior Operations or Director-level role within the next five years.
  • Achieve a healthier work-life balance by optimizing operational efficiency.

Problems & frictions

  • Information silos and outdated documentation lead to inconsistent customer answers.
  • Time spent manually updating and cross-referencing knowledge across multiple platforms.
  • Difficulty in quickly onboarding new support agents due to a lack of centralized, accessible training materials.
  • Ticket escalations often stem from agents not having immediate access to the correct, up-to-date information.
  • Measuring the true impact of knowledge base content on support metrics is challenging.
  • The constant churn of feature releases requires perpetual updates to a fragmented SOP system.

Values

  • clarity
  • reliability
  • team learning
  • efficiency
  • proactive problem-solving

Interests

  • customer support tooling
  • process maps
  • trail running
  • data visualization
  • team productivity hacks

Media habits

  • Skims industry newsletters (e.g., Support Driven, Help Scout blog)
  • Listens to podcasts during commutes/runs (e.g., 'Customer Support Leader', 'The SaaS Show')
  • Active on LinkedIn, follows thought leaders in CX and Ops
  • Reads Reddit threads in r/CustomerService and r/SaaS
  • Occasional dives into technical blogs when troubleshooting

Questions & answers

Yolanda Funk’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: The single source of truth for your company.. the product is an AI-powered knowledge base built for teams tired of stale docs and scattered information.… What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The single biggest problem we have is the fragmentation of our internal knowledge. Right now, information lives across Zendesk macros, Slack threads, Google Docs, and spreadsheets. Keeping it all synchronized takes a significant chunk of my team's time each week, especially after escalations or feature releases. I'd estimate it costs us at least 5-10 hours per week of dedicated effort just to maintain consistency, which directly impacts our ability to onboard new agents quickly and provide consistently accurate answers to customers. We've tried creating more centralized SOPs, but they quickly become outdated if not rigorously maintained.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.