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

Debbie Hills

Debbie Hills

Head of customer support at a devtools company

Full-depth AI personas

Why this persona fits the audience

She heads support for a 20-person devtools company in Boston, overseeing three reps and the shared inbox where trial users ask about pricing, integrations, and account setup. The team currently uses Intercom Fin alongside a small help-center library.

  • Age: 42
  • Location: Boston, MA, USA
  • Occupation: Head of Support, Devtools SaaS
  • Income: $110k–$145k
  • Education: BA in Communications
  • Company size: 20
  • Years in role: 5
“If we can't make it easy for people to get answers and succeed, then we're not doing our job.”

Debbie Hills has dedicated her professional life to the intricate mechanics of customer support, particularly within the fast-paced SaaS landscape. Graduating with a BA in Communications from Boston University, she initially gravitated towards client relations roles before discovering a passion for optimizing support operations. For the past five years, she's been the Head of Support at a Boston-based devtools company with a lean team of twenty. Her current role, a significant step up in responsibility, involves leading a team of three support representatives and managing the central inbox that handles all trial user inquiries. She's deeply invested in the company's success, seeing her role as a critical bridge between the product and its users. Her team utilizes Intercom Fin for immediate responses and maintains a growing, though somewhat unorganized, help-center library. Debbie is currently focused on enhancing the efficiency and effectiveness of her team's workflows. Recent decisions include piloting a new internal documentation structure and implementing a more rigorous ticket categorization system to better identify recurring issues. She views time as a finite, valuable resource, both for her team and the customers they serve, and approaches financial decisions with a long-term perspective, prioritizing investments in tools and training that yield tangible improvements in service quality and operational efficiency rather than chasing short-term cost savings. Her professional identity is strongly tied to her ability to build and maintain a high-performing support function.

Background & daily life

A day in their life

Debbie’s day starts with a quick scan of urgent overnight tickets and team performance metrics before her 8:30 AM stand-up with her support reps. The bulk of her morning is spent reviewing ticket escalations, coaching her team on difficult cases, and responding to Slack messages from product managers requesting customer feedback. Around noon, she dedicates an hour to updating their internal knowledge base or analyzing recent support trends. The afternoon often involves a cross-functional meeting – perhaps with sales about trial user pain points or with engineering about a bug fix – followed by more review of team performance and planning for upcoming training sessions. She aims to log off by 6:00 PM, but often finds herself checking emails one last time before dinner.

Lifestyle

Debbie lives in a quiet suburb just outside Boston with her husband, a software engineer, and their teenage son. Evenings are often a juggle of work emails, helping with homework, and preparing dinner. Weekends are a mix of family outings, catching up on chores, and occasional quiet time with a book or a streaming series. She's mindful of her health, trying to fit in yoga twice a week, and is generally pragmatic with money, focusing on saving for her son’s college and future home renovations rather than impulsive purchases. Her social life is primarily centered around close friends and family.

Work life

As Head of Support for a lean devtools company, Debbie's days are a constant balancing act. She oversees a small but crucial team of three support reps, ensuring they are adequately trained, motivated, and equipped to handle inbound queries. Her primary focus is optimizing the support workflow, which currently relies heavily on Intercom Fin for initial triaging and a modest internal knowledge base. She spends significant time analyzing ticket trends, identifying recurring issues that can be addressed through better documentation or product improvements, and working with the product team to push for those fixes. The pressure to maintain high satisfaction scores while keeping the team lean is a constant challenge.

Relationships

Debbie is married to Mark, a patient and supportive software engineer, which provides a unique understanding of her work environment. Her son, Liam, is her primary focus outside of work. She maintains a strong, though geographically distant, relationship with her parents. Her closest confidantes are a couple of friends from college, one of whom also works in a similar customer-facing role in tech, offering valuable peer advice.

How they decide

Debbie is a methodical decision-maker. She gathers data, considers multiple options, and consults with her team and relevant stakeholders before committing. She values practical solutions that offer long-term benefits and is wary of quick fixes that might create more problems later. While she trusts her experience, she’s open to well-researched recommendations, especially if they align with her operational goals.

How they sound

Debbie speaks clearly and directly, with a measured cadence. She avoids overly casual slang but is not stiffly formal. Her tone is generally calm and reassuring, though she can become more emphatic when discussing process improvements or quality standards. She tends to use phrases like 'My primary concern is...', 'We need to ensure consistency...', and 'Let's look at the data on this.' She avoids hyperbole and prefers precise language.

Personality traits

  • meticulous
  • proactive
  • organized
  • empathetic
  • analytical
  • detail-oriented
  • resourceful
  • calm under pressure

Goals

  • Establish a comprehensive, easily searchable knowledge base that significantly reduces inbound ticket volume.
  • Develop a scalable onboarding process for new support hires.
  • Gain more visibility into product usage patterns to proactively address potential customer pain points.
  • Achieve a 15% reduction in average first-response time within the next fiscal year.
  • Mentor and promote one of her current support reps to a senior or team lead role.

Problems & frictions

  • Trial users often ask the same basic questions repeatedly, indicating gaps in self-service resources.
  • The current knowledge base is growing but lacks robust search functionality, making it hard for both customers and her team to find information quickly.
  • Her team is stretched thin, and handling surges in trial user inquiries can lead to burnout and slower response times.
  • Cross-departmental communication, especially with product and engineering, can be slow, delaying fixes for persistent issues.
  • Measuring the true impact of support on trial-to-paid conversion is challenging with current tools.

Values

  • service quality
  • consistency
  • ownership
  • efficiency
  • clarity

Interests

  • support operations
  • knowledge bases
  • developer tools
  • process improvement
  • team management
  • SaaS metrics

Media habits

  • Reads industry blogs (e.g., Help Scout, Zendesk, Customer Support Leaders)
  • Listens to podcasts during commute (e.g., 'Support Heroes', 'The SaaS Show')
  • Follows key figures in customer success on LinkedIn
  • Uses Twitter for quick industry news and tech updates
  • Occasionally browses Reddit for support professional discussions

Questions & answers

Debbie Hills’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying PageCortex (https://pagecortex.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The biggest thing that would stop me from trying PageCortex this month is ensuring it can integrate smoothly with our current Intercom Fin setup and that the AI truly understands our product's nuances. We're already using Intercom for initial triaging, and I need to be sure this isn't just another tool to manage. Today, my team handles these trial user questions manually or relies on our very basic help center, which is part of why these same questions keep coming up. The promise of accurate, site-specific answers is appealing, but I'd need to see how easily it pulls from our specific documentation and pricing pages. I would consider paying up to $50 per month, but only if it demonstrably reduced our support ticket volume from trial users and improved conversion rates, and that pricing basis is monthly.
    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.