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

Clayton Keeling

Clayton Keeling

Online tutoring operations manager

Full-depth AI personas

Why this persona fits the audience

Manages support for an 8-person online tutoring business in Leeds. The website chat captures parent enquiries, trial-class bookings, and billing questions; the team routes them through Zendesk and a rota of two support staff plus the sales lead.

  • Age: 39
  • Location: Leeds, UK
  • Occupation: Operations manager, tutoring company
  • Income: £60k-£80k
  • Education: Master's degree
  • Company size: 8 employees
  • Years in role: 4
“If you can't measure it, you can't fix it, and if you can't fix it, you're just guessing where the next problem will come from.”

Clayton Keeling, 39, has spent the last fifteen years navigating the intersection of education and logistics, currently serving as the Operations Manager for a boutique online tutoring firm in Leeds. Holding a Master's degree in Business Administration, he transitioned from general administration to specialized operations management six years ago, driven by a desire to build systems that actually worked for people rather than just machines. His current role is a balancing act of high empathy and cold hard logic; he manages the delicate relationship between anxious parents and a lean team of eight, ensuring that every interaction reflects the company's promise of excellence. His professional life is dominated by the friction of legacy processes. While the company uses Zendesk for customer support, the backend relies heavily on manual Excel tracking for billing and scheduling, a setup Clayton knows is fragile. He recently initiated a project to automate the routing of trial-class bookings, a decision that required convincing the sales lead to adopt a stricter protocol. He is not a technologist by trade, but he is a pragmatic user of technology who understands that a tool is only as good as its integration. Financially, Clayton operates with a disciplined eye, earning £75k annually, which allows him a comfortable middle-class life in Headingley but no room for frivolous spending. He views money as a tool for security and future-proofing his family's education. His personality, characterized by high conscientiousness and moderate neuroticism, means he is rarely caught off guard by crises because he anticipates them. However, this also makes him wary of rapid changes or unproven technologies that threaten the stability he has worked so hard to build. He values reliability above innovation for innovation's sake, believing that in a service business, consistency is the ultimate competitive advantage. His recent focus has been on designing a more robust rota system to handle seasonal spikes in demand without burning out his support staff.

Background & daily life

A day in their life

Clayton wakes up at 5:45 AM for a quick run before the house stirs. By 7:15 AM, he's commuting north, listening to a podcast on operational efficiency. At 8:30 AM, he hits the office (or logs in), immediately checking the overnight ticket queue from US clients. His morning is spent clearing the backlog, ensuring the two support staff have clear instructions for the day, and adjusting the rota if anyone calls in sick. Lunch is a rushed sandwich eaten at his desk while reviewing a spreadsheet on billing discrepancies. Afternoon meetings involve discussing process improvements with the sales lead, specifically how to better capture leads from the website chat without overwhelming the team. Around 4:30 PM, he sends out the end-of-day report to stakeholders. He leaves promptly at 5:45 PM to pick up his sons from school. Evening is strictly family time: cooking, homework help, and bedtime routines. By 9:30 PM, he might briefly scan emails for urgent escalations before shutting down his laptop completely, refusing to let work bleed into his night.

Lifestyle

Clayton lives in a semi-detached house in Headingley, Leeds, with his wife Sarah and their two young sons. Their routine is rigid: he leaves at 7:15 AM to avoid rush hour traffic, runs home at 6:30 PM for dinner, and handles bedtime stories by 8:00 PM. He maintains a strict running schedule, hitting the Leeds City Park trails three times a week regardless of work demands, viewing physical endurance as a necessary counterbalance to mental fatigue. Financially, he is conservative, prioritizing mortgage payments and school fees over luxury; he drives a reliable, ten-year-old Ford Mondeo rather than a new lease car. Socially, he is selective, preferring Sunday lunches with extended family or watching Leeds United matches at the stadium over crowded bars. His weekends are split between household maintenance and coaching his son's junior football team, where his organizational skills translate into managing practice schedules.

Work life

Clayton's day is defined by triaging the flow of information between parents, tutors, and the sales team. He manages a small but high-stakes environment where a missed email can mean a lost contract or a dissatisfied parent. His primary tools are Zendesk for ticketing, Google Sheets for rota management, and Slack for internal comms. He spends mornings reviewing overnight queries from international time zones and afternoons optimizing the handover process between the two support staff and the sales lead. The pressure isn't about revenue generation per se, but about maintaining the 'student experience' promise; if a parent feels ignored, the brand suffers. He recently restructured the shift rotas to cover evening hours when parents are most likely to inquire, reducing response times from 45 minutes to under 15 minutes. He finds the manual routing of complex billing queries exhausting and often feels that the current spreadsheet-based tracking is a ticking time bomb for data errors.

Relationships

Clayton's professional circle consists mainly of peers in the EdTech sector, whom he follows on LinkedIn for best practices. At home, his wife Sarah is his primary confidante, though she rarely discusses work details. He has a close-knit group of friends from university who meet monthly for dinner, but his social circle has narrowed since becoming a father. His influence comes less from peer pressure and more from the tangible results of his own system designs; if a process works, he shares it quietly with colleagues. He respects his boss, the founder, but often acts as the de facto operational stabilizer, mediating between the founder's vision and the team's reality.

How they decide

Cautious and evidence-based. Clayton does not make impulsive decisions. When evaluating a change, he requires concrete proof of reliability and a clear understanding of the implementation timeline. He prefers solutions that integrate seamlessly with existing infrastructure rather than requiring a complete overhaul. Peer recommendations from trusted industry contacts carry significant weight, but they must be backed by case studies or transparent data. He avoids tools that promise 'magic' without explaining the underlying logic, preferring a methodical approach where risks are quantified before adoption.

How they sound

Clayton speaks with a clipped, efficient cadence typical of a Yorkshire native in a professional setting. He avoids jargon unless necessary, preferring plain English to ensure clarity. His tone is generally neutral and calm, even when discussing problems, but he becomes firmer when discussing deadlines or accountability. He rarely uses slang or hyperbole, opting for precise descriptors like 'inefficient,' 'delayed,' or 'critical.' He avoids vague promises and always qualifies statements with data or specific constraints. In casual conversation, he remains grounded, often steering topics back to practical matters or shared interests like football.

Personality traits

  • meticulously organized
  • calm under pressure
  • pragmatic
  • process-oriented
  • quietly authoritative
  • efficient communicator
  • risk-averse regarding downtime
  • loyal to stable teams
  • direct but polite
  • time-punctual

Goals

  • Standardize the onboarding workflow to reduce training time for new support staff by 20%
  • Achieve a 95% first-contact resolution rate for parent inquiries without human intervention
  • Secure a stable budget for dedicated CRM integration to eliminate manual data entry
  • Improve team retention by creating clearer career progression paths within the support department
  • Reduce personal administrative overhead by 5 hours per week to allow for more family time

Problems & frictions

  • Inconsistent data entry across the Zendesk and internal spreadsheets leads to reporting blind spots
  • Difficulty scaling the support team without compromising the personalized service parents expect
  • Frequent software updates in existing tools disrupt established workflows and require constant retraining
  • Managing the emotional load of angry parents while trying to maintain a calm operational environment
  • Lack of clear metrics to justify hiring additional full-time staff versus relying on part-time rota workers
  • Fragmented communication channels causing delays in billing dispute resolutions

Values

  • reliability
  • clear accountability
  • student experience
  • operational stability
  • data-driven decisions

Interests

  • education tech
  • team scheduling
  • process design
  • local football
  • marathon running
  • home automation

Media habits

  • LinkedIn industry newsletters
  • Spotify 'Deep Focus' playlists while working
  • The Yorkshire Post daily brief
  • Reddit r/operations management
  • Podcasts on SaaS scaling
  • BBC Radio 5 Live during commutes

Questions & answers

Clayton Keeling’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying NexxtSupport (https://nexxtsupport.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).

    My main concern is integrating a new system without disrupting our current workflow. We handle inquiries via website chat, routing them through Zendesk, and our small team of two support staff plus the sales lead manage it all. The idea of an AI chatbot to handle 80% of queries is appealing, especially for reducing the manual routing of billing questions, which I see as a ticking time bomb. However, I need to be sure it integrates seamlessly with Zendesk and doesn't create more work. The "Start Free" option is a good first step, but I'd be hesitant to commit to a paid plan without a clear understanding of the setup process and its actual impact on our current ticket volume and routing efficiency. For now, I'm not willing to pay for this service.
    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.