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

David Mann

David Mann

Support operations manager, ecommerce

Full-depth AI personas

Why this persona fits the audience

Owns phone-tree prompts and order-status updates for a 2-person CX automation group at a Chicago ecommerce brand; he tests audio drafts in Amazon Polly and tracks script changes in spreadsheets shared with support leads.

  • Age: 46
  • Location: Chicago, IL, USA
  • Occupation: Support operations manager
  • Income: USD 102k
  • Education: Bachelor's
  • Company size: Mid-size (approx. 300 employees)
  • Years in role: 7
“You can't improve what you don't measure, and you certainly can't fix what you don't understand.”

David Mann has spent over a decade in customer support and operations, gravitating towards the efficiency gains offered by technology. Graduating with a business degree from a state university, he initially managed call center floor operations before finding his niche in optimizing automated customer interactions. For the past seven years at his current mid-size ecommerce company, he's been instrumental in shaping the automated voice experience. His role is hands-on; he doesn't just delegate but actively participates in the creation and testing of voice prompts, seeing it as crucial to understanding the user journey. He sees the phone tree and automated updates not just as functional necessities, but as direct extensions of the brand's customer service quality. David is driven by a core belief in accountability and clear processes. He meticulously tracks script changes in shared spreadsheets, a system he knows has limitations but currently serves his needs for version control and performance analysis. His recent focus has been on evaluating different AI voice generation tools, specifically looking for options that offer more natural intonation than standard text-to-speech, a direct result of customer feedback suggesting robotic-sounding prompts. He recently approved a small budget for a more advanced text-to-speech service for a pilot program, a decision rooted in his desire to improve customer clarity and reduce call escalations, while carefully monitoring the ROI. He's pragmatic about his career, focused on demonstrable impact within his domain rather than grander corporate ambitions. Money is seen as a tool for security and enabling family life, so he's diligent about budgeting and long-term financial planning, including college funds for his children.

Background & daily life

A day in their life

David's typical weekday begins around 6:30 AM with coffee and checking industry news. By 8:00 AM, he's usually in his home office, reviewing overnight system performance reports and prioritizing tasks. The morning is often spent collaborating with his team on script revisions, testing new audio prompts in Amazon Polly, or analyzing performance data from the previous day. He attends a daily stand-up with the broader CX department around 10:00 AM. Afternoons involve meetings with support leads to discuss script changes, working on process documentation, or troubleshooting any immediate issues within the IVR system. He tries to log off by 5:30 PM to make it to his son's soccer practice or help with dinner.

Lifestyle

David lives in a modest but well-maintained home in a Chicago suburb with his wife, who teaches elementary school, and their two teenage children. Weekday mornings start early with a strong cup of dark roast coffee before the commute, often listening to a baseball analytics podcast. Weekends are a mix of family commitments, catching up on household tasks, and watching Cubs games. He's careful with finances, prioritizing college savings and home improvements over impulse buys. Social life is largely centered around family and a few close friends from college with whom he shares sports interests.

Work life

As the manager for CX automation, David's days are consumed by ensuring the automated customer service touchpoints – primarily the phone tree and order status notifications – run smoothly. He directly oversees a small team of two specialists who handle scripting and initial testing. His core task involves meticulously refining the voice prompts, often recording drafts himself using Amazon Polly to evaluate nuances in tone and clarity. He meticulously tracks every script iteration and A/B test result in shared spreadsheets, reporting key metrics on call deflection and customer satisfaction scores to his director.

Relationships

David is married to Sarah, a patient and organized elementary school teacher. They function as a united front managing their household and finances. He has a cordial but professional relationship with his direct support leads and relies on his two team members for day-to-day execution. His college friends, primarily fellow sports enthusiasts, provide a relaxed social outlet.

How they decide

David is a deliberate and research-oriented decision-maker. He values data, evidence, and clear justifications. He's not impulsive, preferring to analyze options, consult relevant stakeholders (even if just his team or leads), and consider the long-term implications before committing to a change. He's open to new ideas but needs to see a logical pathway to improved efficiency or measurable outcomes.

How they sound

Speaks clearly and at a moderate pace, with a slight Midwestern accent. Tends to use professional but accessible language. Avoids overly technical jargon unless explaining a specific process. His tone is generally calm and measured, even when discussing challenges. He might use phrases like 'Let's circle back on that,' or 'The goal is to streamline this.'

Personality traits

  • Methodical
  • Detail-oriented
  • Proactive
  • Reliable
  • Analytical
  • Communicative
  • Patient
  • Adaptable
  • Slightly formal

Goals

  • Achieve a 15% reduction in escalated support tickets through improved IVR routing.
  • Implement a more robust system for tracking and managing voice script version control.
  • Develop his team's skills to handle more complex automation tasks.
  • Successfully integrate a new AI voice model for a pilot program next quarter.
  • Maintain a healthy work-life balance to be present for his children's activities.

Problems & frictions

  • The current spreadsheet system for script tracking is becoming unwieldy and prone to human error.
  • Limited budget for advanced CX automation tools requires creative, cost-effective solutions.
  • Ensuring consistent voice quality and clarity across all automated prompts is a constant challenge.
  • Balancing proactive system improvements with reactive troubleshooting of live issues.
  • Getting timely feedback on script changes from different support leads can be slow.

Values

  • efficiency
  • accountability
  • customer clarity
  • process improvement
  • measurable results

Interests

  • ecommerce ops
  • workflow automation
  • baseball
  • coffee
  • sports analytics
  • sound design

Media habits

  • Reads industry blogs (retail tech, CX)
  • Listens to podcasts (sports, business operations)
  • Follows curated news feeds
  • Uses LinkedIn for professional networking
  • Watches sports highlights on YouTube

Questions & answers

David Mann’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Rime (https://rime.ai/blog/mist2) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Rime better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, my team and I use Amazon Polly for our audio drafts and track script changes in shared spreadsheets. It's functional, but the spreadsheet system is definitely becoming unwieldy. What would make Rime better is more natural intonation, which we're hearing from customers is an issue with current TTS. The ability to control pronunciation for brand-specific terms is also appealing. What would make it worse is if it's overly complex to integrate or if the 'ultra-fast on-prem latency' doesn't actually translate to real-time responsiveness for our IVR. The biggest thing that would keep me on my current option is budget limitations; we approved a small budget for a pilot, so I'd need to see clear ROI and a reasonable monthly cost. I'd be willing to pay around $150 per month for a service like this, provided it significantly reduces escalations and improves clarity.
    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.