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

Lola Mills

Lola Mills

Customer support engineer

Full-depth AI personas

Why this persona fits the audience

Handles webhook troubleshooting for an API company in Chicago and reproduces customer issues by running local sample apps and forwarding ports through SSH during screenshares. Often uses a free tunnel tool and copies the public address into ticket notes, Slack, and Zendesk.

  • Age: 33
  • Location: Chicago, Illinois, US
  • Occupation: Customer support engineer
  • Income: $85k-$105k
  • Education: Bachelor's degree in computer information systems
  • Company size: Mid-sized tech company (200-500 employees)
  • Years in role: 5
“There's a certain satisfaction in untangling a really knotty problem, knowing you've made something work smoothly again for someone else.”

Lola Mills grew up in a suburban environment outside of Philadelphia, developing an early fascination with how things worked, often taking apart old electronics. This led her to pursue a Bachelor's degree in Computer Information Systems at a state university, where she excelled in coursework focused on networking and system administration. Upon graduation, she took a role as a junior support technician, quickly realizing her aptitude for debugging complex technical issues. She moved to Chicago five years ago, drawn by the city's vibrant tech scene and diverse neighborhoods, and secured her current position as a Customer Support Engineer at a growing API company. Her income range reflects her experience and the specialized nature of her role. Lola is highly conscientious, meticulously documenting every step of her troubleshooting process and striving for accuracy in her resolutions. She values responsiveness highly, understanding the critical impact of API downtime on her customers' businesses. Her approach to work is deeply rooted in problem-solving; she sees each ticket as a puzzle to be solved. She is particularly adept at navigating complex network configurations and using tools like SSH to gain necessary access for diagnosis. Recently, she's been experimenting with integrating a more robust logging system within her team's workflow to proactively identify potential webhook issues before they impact clients, a decision driven by a desire to improve overall system stability and reduce reactive firefighting. She views her career as a continuous learning process, always seeking to deepen her understanding of distributed systems and network protocols. She lives within her means, prioritizing financial stability and saving for long-term goals over immediate gratification.

Background & daily life

A day in their life

Lola's day typically starts around 8:00 AM with a quick scan of urgent emails and Slack channels while sipping coffee. After a brief team stand-up, she dives into her queue of tickets, prioritizing based on severity and customer impact. A significant portion of her morning is spent screensharing with customers, patiently guiding them through troubleshooting steps, and meticulously reproducing issues using local sample apps and SSH tunneling. Lunch is usually a prepped meal eaten at her desk while catching up on a tech podcast. The afternoon involves more troubleshooting, documenting findings in Zendesk, collaborating with developers on bug fixes, and sometimes creating internal documentation for common issues. She aims to log off by 5:30 PM, reserving evenings for personal interests and relaxation.

Lifestyle

Lola lives in a modest but well-organized 1-bedroom apartment in Chicago’s Lincoln Square neighborhood. She's committed to her routine, which includes prepping healthy meals for the week on Sundays to save time and eat better. Her evenings are often spent unwinding with a podcast or tending to her small balcony herb garden. While she enjoys city life, she prioritizes a balanced, low-stress existence, saving diligently for future travel and occasional upgrades to her home setup. Socially, she prefers smaller gatherings with close friends over large parties.

Work life

Lola's days are a whirlwind of customer tickets, Slack pings, and screenshare sessions. Her primary focus is diagnosing and resolving complex webhook issues, often requiring her to dive deep into customer environments. This involves meticulously reproducing reported problems, frequently using SSH to tunnel into local development setups and test configurations. She juggles multiple urgent requests simultaneously, constantly prioritizing and documenting her findings thoroughly in Zendesk. Collaboration with the development team is key, as she often needs to escalate nuanced bugs or request specific code changes.

Relationships

Lola maintains a close-knit circle of friends, mostly met through university or previous jobs. They offer a sounding board for both professional challenges and personal decisions. Her family lives out of state, and they connect weekly via video calls. She has a good rapport with her immediate team, characterized by mutual respect and a shared drive to solve problems efficiently.

How they decide

Lola is a highly analytical and research-driven decision-maker. Before committing to any new tool or process, she thoroughly investigates its functionality, compares it against existing solutions, and reads reviews or case studies. She values practical evidence and demonstrable benefits over hype, and will often experiment with free trials or open-source alternatives if available. She is also influenced by the recommendations of trusted colleagues and industry peers.

How they sound

Speaks clearly and at a moderate pace, with a generally professional but approachable tone. Avoids excessive slang, but might use mild technical jargon naturally within context. Her cadence is steady, reflecting her methodical approach. She tends to be reassuring and empathetic when dealing with frustrated customers, and direct but polite when communicating with colleagues.

Personality traits

  • methodical
  • patient
  • detail-oriented
  • collaborative
  • resourceful
  • calm under pressure
  • practical
  • reliable
  • curious

Goals

  • Achieve a senior support engineer position
  • Contribute to open-source projects related to API development
  • Save enough for a down payment on a small condo
  • Master a new programming language for personal projects
  • Maintain a healthy work-life balance

Problems & frictions

  • Inconsistent customer technical proficiency leading to communication challenges
  • The constant pressure to reduce ticket resolution times
  • Managing the overhead of juggling multiple complex troubleshooting sessions simultaneously
  • Difficulty in replicating intermittent or environment-specific customer issues
  • The need to stay current with rapidly evolving API technologies and best practices

Values

  • responsiveness
  • helpfulness
  • accuracy
  • problem-solving
  • efficiency

Interests

  • debugging
  • podcasts
  • meal prep
  • indie rock music
  • urban gardening

Media habits

  • Listens to tech podcasts during commute
  • Reads developer blogs and Stack Overflow
  • Follows industry news on Twitter/X
  • Uses YouTube for technical tutorials
  • Occasionally browses Reddit for niche tech discussions

Questions & answers

Lola Mills’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Expose local servers to the internet (https://airic.serveo.net/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I use a free tunnel tool and copy the public address into tickets. The biggest obstacle to trying this new tool immediately would be integrating it into my existing workflow and ensuring it's reliable. I haven't explored paid options because the free tools have sufficed. If this offers significantly better stability or advanced features for webhook testing, I might consider paying, perhaps around $6 per month for a Pro plan, similar to what's offered here for unlimited tunnels and no interstitial warnings. The pricing isn't entirely clear if it's a one-time pass or a recurring monthly charge for the Pro plan, so I'd need to confirm that.
    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.