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

Lela Dickinson

Lela Dickinson

customer support specialist

Full-depth AI personas

Why this persona fits the audience

Currently answers tickets and live chat for a five-person startup in Toronto. The team is two founders plus three employees, and she is the first person customers reach when they run into issues using the company’s web app.

  • Age: 26
  • Location: Toronto, Canada
  • Occupation: Customer support specialist
  • Income: CAD 62k
  • Education: College diploma in communications
  • Company size: 5
  • Years in role: 2
“It's always about finding that balance between being efficient and truly understanding what the person on the other end needs.”

Lela Dickinson's journey into customer support was a natural progression from her communications diploma and an innate desire to help others. Growing up in a suburban Toronto household, she was always the go-to person for friends needing advice or help with a task. This tendency, coupled with a strong sense of responsibility, led her to pursue a role where she could directly impact user satisfaction. She landed her current position at a nascent tech startup two years ago, drawn by the promise of direct impact and the fast-paced environment. Her role demands high conscientiousness; she meticulously tracks customer issues, ensures follow-up, and takes accountability for resolutions. While she possesses a natural agreeableness and enjoys connecting with people, she's learned to set boundaries to avoid burnout, a challenge in her current high-demand position. Her income of CAD 62k allows for a comfortable lifestyle in Toronto, enabling her to save for future goals and enjoy her hobbies, but she remains budget-conscious, prioritizing experiences and professional development over material possessions. She recently made a conscious decision to implement stricter time-blocking techniques to manage her workload more effectively, a direct response to feeling overwhelmed by the sheer volume of incoming support requests, particularly during peak usage times for the web app. This involves setting dedicated blocks for ticket response, proactive outreach, and documentation, a shift from her earlier, more reactive approach.

Background & daily life

A day in their life

Lela's weekday typically begins around 7:30 AM with a quick check of urgent emails and Slack messages before her commute. She listens to a podcast on the subway, arriving at the office by 9:00 AM. The morning is usually a flurry of responding to incoming tickets and live chats, identifying patterns in customer feedback, and collaborating with the tech lead on bug fixes. Lunch is a brief affair, often spent scanning industry news or a quick walk. The afternoon involves deeper dives into complex issues, drafting support documentation, and attending a brief stand-up with the founders. She usually wraps up around 5:30 PM, heading home to prepare dinner, perhaps planning a new baking project for the weekend.

Lifestyle

Lela lives a structured yet engaging life in Toronto. Her weekdays are a blend of work, a quick trip to the gym, and evenings spent listening to podcasts or catching up with friends. Weekends often involve testing new baking recipes, tending to her small balcony herb garden, or exploring local farmers' markets. She's mindful of her finances, saving a portion of her income for future travel and professional development, but enjoys splurging on quality ingredients for her baking. Socially, she prefers smaller gatherings with close friends over large parties.

Work life

As the primary customer support specialist at a lean startup, Lela's days are dynamic and often unpredictable. She juggles responding to urgent ticket escalations via Zendesk, engaging in real-time troubleshooting via Intercom chat, and documenting recurring issues for the development team. Her workspace is a shared desk in the open-plan office, where she collaborates closely with the two founders and two other junior employees. The pressure is constant to provide swift, effective solutions, as customer satisfaction directly impacts the app's reputation and adoption rates, especially with limited resources.

Relationships

Lela maintains close ties with her parents, who live in a nearby suburb, and relies on their steady advice. Her core friend group consists of about five people she met during college, with whom she shares everything from work frustrations to baking triumphs. She considers the startup founders mentors, though their fast-paced approach can sometimes be overwhelming.

How they decide

Lela tends to be methodical and research-oriented when making decisions, especially those with long-term implications. She gathers information, weighs pros and cons carefully, and often seeks input from trusted friends or mentors before committing. For immediate work-related issues, she relies on established best practices and her own problem-solving skills.

How they sound

Speaks clearly and at a moderate pace, with a friendly but professional tone. She uses standard Canadian English, avoiding excessive slang. When explaining technical issues, she simplifies complex terms effectively. She tends to be reassuring and patient, often saying things like, 'Let's see if we can figure this out together' or 'I understand how frustrating that must be.' She avoids overly casual language in professional contexts.

Personality traits

  • Empathetic
  • Detail-oriented
  • Reliable
  • Proactive
  • Calm under pressure
  • Methodical
  • Warm
  • Resourceful
  • Organized

Goals

  • Advance to a senior customer success role within a growing tech company.
  • Develop expertise in user onboarding and retention strategies.
  • Complete a part-time certificate in project management.
  • Travel to Japan to experience its unique culture and cuisine.
  • Build a more robust professional network in the Toronto tech scene.

Problems & frictions

  • Limited visibility into the product roadmap, making it difficult to anticipate customer needs.
  • Feeling the strain of being the sole point of contact for all customer issues, leading to occasional burnout.
  • Balancing the need for thorough problem resolution with the startup's demand for speed.
  • Navigating internal communication challenges between customer feedback and the development team's priorities.
  • The constant need to wear multiple hats in a small company setting.

Values

  • helpfulness
  • patience
  • accountability
  • clear communication
  • problem-solving

Interests

  • customer experience
  • podcasts
  • baking
  • urban gardening
  • indie music

Media habits

  • Listens to true crime and productivity podcasts during her commute.
  • Scans tech news sites and industry blogs during lunch.
  • Follows customer experience influencers on LinkedIn.
  • Uses Instagram for lifestyle content and sharing baking projects.
  • Reads articles and forums related to communication strategies.

Questions & answers

Lela Dickinson’s public research answers, newest questions first. Up to 10 per page.

  1. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: Manage Multiple AI Agents in One Place.

    The biggest concern for us would be integrating this with our current workflow. We're a small team, and I'm often the one trying to connect different tools. I'd need to understand how existing agents I might already be using elsewhere could connect, and what kind of technical lift that would be. The pricing, starting at $199/month, is something we'd need to evaluate carefully against our budget, but the core question is about seamless integration and how much time it would save versus create.
    View answer & full research →
  2. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: Manage Multiple AI Agents in One Place.

    I would investigate further. The idea of managing multiple AI agents from one place sounds incredibly useful, especially given how I'm currently juggling different support channels and sometimes feel overwhelmed. The ability to see up to eight chats at once and manage them from my phone is a huge draw. My main question is how well it integrates with existing tools we might use, and whether the "Connect an existing agent" feature truly works seamlessly for bringing in agents from other platforms. While the $199/month price isn't exorbitant, I'd need to understand the full scope of what that includes for a small startup like ours.
    View answer & full research →
  3. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: Manage Multiple AI Agents in One Place.

    This product, Agent Teams, seems like it could help centralize managing multiple AI agents. Since I'm currently the sole point of contact for customer issues, the idea of having a 'Chat Wall' to see up to eight agent chats at once is appealing. It could potentially help me track who's handling what and identify blockers more easily, which would be a big help in juggling everything. I'm curious how well it integrates with agents we might already be using elsewhere. The page mentions connecting external agents, but I'd need to understand the specifics of that. Also, the 'Open desktop' feature sounds useful for intervening when an agent needs human help, but I'd want to ensure it's straightforward to use and doesn't add to my workload.
    View answer & full research →
  4. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Cofounders for Your Startup.

    My biggest concern would be the integration with our current systems and how seamless the handover process would be between these AI cofounders and our human team, especially for critical customer support issues. I also wonder about the AI's ability to truly understand nuanced customer emotions and provide that empathetic touch. We're a small team, and while the idea of AI cofounders is intriguing for scaling, ensuring reliable and effective support without sacrificing quality is paramount. It would be helpful to see some case studies or demos specifically showing how these AI agents handle complex, sensitive customer interactions and how quickly they can be onboarded and integrated into our existing workflow.
    View answer & full research →
  5. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: AI Cofounders for Your Startup.

    I would investigate further. The idea of AI cofounders for product, growth, and operations is intriguing, especially given my current role where I'm the sole point of contact for customer issues, and sometimes feel overwhelmed. The "Operations" aspect, which mentions keeping onboarding, support, and customer feedback moving, is particularly relevant. However, the main reason I'd investigate is to understand how these agents actually handle nuanced customer issues and if they can truly provide the empathetic support I aim for. My most important unanswered question is how well these AI agents integrate with existing support tools like Zendesk and Intercom, and what the learning curve is for managing them.
    View answer & full research →
  6. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: AI Cofounders for Your Startup.

    This product, Agent Teams, sounds like it could potentially help with the "Operations" side of things by managing onboarding, support, and customer feedback. Given my role, having AI agents take ownership of these tasks could free me up to focus on deeper issues or documentation. However, it's unclear how well it integrates with our current systems or if it truly understands the nuances of our specific web app and customer base. I'd also be concerned about the handover process and ensuring customer issues are resolved effectively and empathetically, not just processed. The idea of "AI cofounders" is intriguing but also a bit abstract.
    View answer & full research →
  7. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: The One-Person Company.

    As the sole person handling customer support, the idea of agents managing agents is intriguing, but I'm concerned about how this integrates with our current workflow. We rely heavily on direct customer feedback to inform the product roadmap, and I worry about losing that direct line if everything is filtered through an 'Operations' agent. My biggest blocker is understanding how my role would evolve and ensuring that customer issues are still being addressed with the necessary empathy and detail. I'd need to see a clear process for how customer feedback is escalated and how the agents ensure it directly influences product development, perhaps with a demo showing the handoff between the operations agent and the product agent.
    View answer & full research →
  8. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: The One-Person Company.

    I would investigate further. The idea of agents managing agents is intriguing, especially the 'Operations' aspect which could potentially help with customer feedback and support, areas I'm very familiar with. However, the concept is still quite abstract. My main reason for investigating is to understand how this actually works in practice for a small startup like ours. The most important unanswered question for me is how much actual human oversight is needed, and how effectively these agents can handle nuanced customer issues without direct human intervention. Given that I'm a customer support specialist and not a founder, I don't have purchasing authority for a tool at $199/month, but I could certainly make a recommendation if it proved valuable.
    View answer & full research →
  9. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: The One-Person Company.

    This product, Agent Teams, sounds like it could potentially help automate some of the background operations that often fall to me. The idea of having specialists for Product, Growth, and Operations, coordinated by a lead agent, is intriguing. For my startup, it could fit into managing the "Operations" side, which includes customer feedback and onboarding. However, it's a bit unclear how it would integrate with my current support tickets and live chat via Zendesk and Intercom. I'm also curious about the "lead agent" and how much direction it truly needs from us founders. The "From $199/month" pricing is a bit steep for our budget, and I'd need to understand exactly what that covers and if it truly reduces workload.
    View answer & full research →
  10. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Teams for Startups of 1–5 People.

    My main concern would be the integration and reliability of these AI teammates. As the primary support contact, I need to ensure any new tools truly help, not hinder, our customers. While the idea of AI support sounds promising for handling volume, I'd need to understand how it handles complex, nuanced issues and how it learns from customer interactions. The page mentions persistent files and memory, which is good, but I'd want to see clear evidence of its ability to resolve issues effectively before relying on it. The cost from $199/month is noted, but the biggest blocker for me would be ensuring it doesn't create more work or customer frustration by providing incorrect or unhelpful responses. I'd need to see case studies or a trial period focused specifically on support scenarios.
    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.