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

Sophie Leffler

Sophie Leffler

Customer support lead at a SaaS company

Full-depth AI personas

Why this persona fits the audience

Manages a 3-person support team at a Manchester SaaS company. The team receives product questions and onboarding follow-ups through a WhatsApp number routed into Respond.io and Zendesk, with tags and handoffs documented in the CRM.

  • Age: 36
  • Location: Manchester, UK
  • Occupation: Customer support lead
  • Income: £58k/year
  • Education: Bachelor's degree
  • Company size: 12-15 employees (Series A startup)
  • Years in role: 2
“If it isn't written down, it didn't happen, and if it didn't happen, we can't fix it.”

Sophie Leffler is the anchor of customer operations at a mid-sized SaaS firm in Manchester, a role she has held for two years after climbing the ladder from a generalist support agent. Born in Stockport and educated with a Business Management degree from the University of Manchester, she gravitated toward operations because she found solace in creating order from chaos. At 36, she commands a salary of £58,000, which affords her a comfortable life but leaves little room for financial recklessness. Her current reality is defined by the friction of growth; her company is expanding rapidly, but their support infrastructure remains cobbled together from disparate tools like WhatsApp, Respond.io, and Zendesk. This fragmentation forces Sophie to act as a human API, manually bridging gaps that should be automated. She recently made the difficult decision to overhaul their entire tagging taxonomy, a project that required convincing skeptical engineers to build custom scripts. While she values stability, she is acutely aware that her team's burnout levels are rising due to the lack of seamless integrations. She views her career trajectory as linear and meritocratic, believing that the right processes will eventually make her indispensable. Her personal life mirrors this need for control; she maintains a strict routine, ensuring that her weekends are protected for family time with her husband in Leeds. She is currently exploring ways to automate the mundane aspects of her job, driven by a desire to focus on high-value strategic thinking rather than administrative drudgery.

Background & daily life

A day in their life

Sophie wakes at 6:30 AM, immediately checking her phone for any overnight escalations from the US market before brewing coffee. By 8:15 AM, she is at her desk, reviewing the overnight ticket queue in Zendesk and assigning priorities. Her morning is dominated by a stand-up with her three agents, where she drills down on specific WhatsApp conversations that need clarification. Mid-morning is reserved for deep work: rewriting SOPs or analyzing CRM data to spot trends in customer confusion. Lunch is a quick sandwich eaten at her desk while answering a complex technical query. Afternoons involve coaching sessions with junior staff, reviewing their tagged tickets, and troubleshooting the Respond.io routing logic. She stays until 6:00 PM to ensure all handoffs are documented before logging off, feeling a sense of relief only when the dashboard shows zero open critical tickets.

Lifestyle

Sophie lives in a modern, slightly cluttered flat in Didsbury with two friends who work in adjacent tech roles. Her evenings are rarely unstructured; she prefers reading non-fiction or planning her week over going out to loud bars. She is health-conscious, running three times a week along the Irwell riverside, viewing exercise as a necessary reset rather than a hobby. Financially, she is prudent, saving aggressively for a deposit on a first home while avoiding impulse buys. Socially, her circle is small but deep, consisting mostly of other professionals who value clear boundaries between work and rest. She enjoys quiet weekends spent meal-prepping and organizing digital files, finding genuine satisfaction in orderliness.

Work life

Sophie spends her days navigating the chaotic intersection of a small SaaS team and demanding enterprise clients. Her primary toolset involves toggling between Zendesk dashboards, the Respond.io interface, and their internal CRM. She manages a trio of junior agents, spending significant time auditing ticket tags, verifying that WhatsApp messages were correctly transcribed, and ensuring no handoff occurred without a note. Recent weeks have been dominated by cleaning up a backlog where manual copy-pasting led to lost context. She is constantly refining their Standard Operating Procedures (SOPs) to reduce the cognitive load on her team, often staying late to document new workflows that emerge from unexpected client queries.

Relationships

Sophie is married to James, a civil engineer based in Leeds, whom she sees every other weekend; their relationship is stable but requires deliberate scheduling. She has two close friends from university who remain her primary confidantes, often meeting for coffee once a month. Professionally, she looks up to her CEO, who values transparency, but finds her direct manager's micromanagement style frustrating. She influences her team by modeling calm professionalism and expects them to adopt her rigorous documentation standards.

How they decide

Sophie approaches decisions with a heavy reliance on evidence and precedent. She is not impulsive; she needs to see a clear workflow diagram, understand the cost-benefit analysis, and verify peer reviews before committing to a change. She trusts data over hype and prefers tools that integrate seamlessly with existing ecosystems rather than those offering flashy, isolated features. Her process is methodical: identify the friction point, research solutions, test with a pilot group, and then roll out only if the metrics improve.

How they sound

Sophie speaks in clear, concise sentences with a measured cadence. She avoids slang and overly emotional language, preferring precise verbs like 'clarify,' 'escalate,' and 'document.' Her tone is professional yet approachable, never condescending but firm on process adherence. She frequently uses terms like 'handoff,' 'ticket lifecycle,' and 'SLA' naturally. She avoids vague qualifiers like 'maybe' or 'sort of,' replacing them with specific actions or timelines. When stressed, her speech becomes even more structured, focusing strictly on facts and next steps rather than feelings.

Personality traits

  • Methodical
  • Calm under pressure
  • Detail-oriented
  • Systematic
  • Pragmatic
  • Reliable
  • Structured
  • Empathetic but firm
  • Process-driven
  • Organized

Goals

  • Achieve a 100% SLA adherence rate across all support channels
  • Reduce average response time for onboarding tickets by 20%
  • Build a self-sustaining knowledge base that reduces tier-1 inquiries
  • Secure a promotion to Head of Customer Success within 18 months
  • Implement a fully automated tagging system to eliminate manual categorization

Problems & frictions

  • Inconsistent data entry by junior staff leading to CRM hygiene issues
  • Fragmented communication between WhatsApp, email, and live chat requiring constant context switching
  • Lack of robust API integration causing delays in syncing customer status updates
  • Difficulty scaling the current manual onboarding process as the user base grows
  • High turnover risk among junior staff due to repetitive, low-autonomy tasks
  • Unclear ownership of 'orphaned' tickets that fall between sales and support

Values

  • clear processes
  • team accountability
  • reliable customer communication
  • operational efficiency
  • data integrity

Interests

  • Zendesk
  • support operations
  • process documentation
  • workflow automation
  • productivity systems

Media habits

  • LinkedIn for industry case studies
  • Slack communities for ops teams
  • Tech blogs (e.g., HubSpot, Intercom)
  • Podcasts during commute (The Daily, Reply All)
  • Twitter/X for tech news snippets

Questions & answers

Sophie Leffler’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying API-Supp (https://api-supp.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 main reason I would hesitate to try API-Supp this month is the fact that it's an unofficial bridge to WhatsApp. My current process involves routing WhatsApp messages into Respond.io and then into Zendesk, with tags meticulously documented in our CRM. While I understand the appeal of an API, the "unofficial" nature raises concerns about stability and data integrity, which are critical for my team and our customers. I need to be certain that this wouldn't create more work by introducing new issues. If it proved reliable, I might consider it, but I'd need to see a clear path for integration and data flow. Given the current setup and the potential risks, I wouldn't be willing to pay for this at present.
    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.