Why this persona fits the audience
He runs support operations for a marketplace startup in Bengaluru with a four-person team. The group uses macros, shared inbox rules, and spreadsheets to manage help articles, escalation paths, and the small set of website flows that affect ticket volume. He is comfortable coordinating technical changes, but the implementation is usually done by a developer or analyst on the team.
- Age: 33
- Location: Bengaluru, India
- Occupation: Support Operations Manager
- Income: INR 19L
- Education: Bachelor's degree in computer applications
- Company size: Startup, ~40 employees
- Years in role: 4 years
“The real challenge isn't just solving problems for customers, it's building systems that prevent those problems from happening in the first place.”
Aayushman Jha grew up in a middle-class family in Chennai, where his father worked as an accountant and his mother was a homemaker. From a young age, he showed an aptitude for logic and problem-solving, which led him to pursue a Bachelor's degree in Computer Applications. After graduating, he joined a small tech firm as a support executive, quickly realizing his knack for understanding customer pain points and identifying process inefficiencies. He moved to Bengaluru seeking better career opportunities and joined his current marketplace startup four years ago as a Support Operations Manager. He was initially tasked with setting up the support function from scratch. His current role involves managing a team of four, overseeing daily operations, and ensuring customer queries are handled efficiently. He has been instrumental in developing their current system of macros, shared inbox rules, and extensive spreadsheets that form the backbone of their support operations. Aayushman is comfortable coordinating with the engineering team for technical changes, though he relies on the dedicated developer or analyst for implementation due to resource constraints. He is deeply invested in improving team efficiency and customer satisfaction, constantly looking for ways to optimize their existing workflows. His income of INR 19L allows for a comfortable life, but he remains mindful of expenses, prioritizing savings for his family's future. He sees his role as critical to the company's growth, understanding that a smooth customer experience is paramount for a marketplace. He is driven by a desire for order and reliability in the often-chaotic startup environment, constantly seeking to bring structure and predictability to his team's work.
Background & daily life
A day in their life
Aayushman's day typically begins around 7:30 AM with a quick check of urgent overnight tickets and team performance metrics. After dropping his son at school, he heads to the office. His mornings are often spent in team stand-ups, reviewing ticket queues, and collaborating with the developer on any ongoing technical fixes. He dedicates time to updating their internal knowledge base or refining macros. Lunch is usually a quick affair at his desk or a nearby eatery. Afternoons involve more in-depth analysis, planning for future process improvements, and responding to escalations. He aims to wrap up by 6:30 PM to be home for dinner with his family, though urgent issues can sometimes extend his day.
Lifestyle
Aayushman lives in a moderately sized apartment in a well-connected suburb of Bengaluru. His days are structured, balancing his demanding role with family commitments. Weekends are reserved for his wife and son, often involving trips to local parks or visiting family. He enjoys watching cricket matches with friends and occasionally tries out new restaurants. Financially, he's a careful planner, prioritizing savings for his son's future education and aiming for a down payment on a larger home within the next five years. He values his downtime, seeing it as essential for recharging.
Work life
Aayushman manages a lean support operations team of four at a fast-growing e-commerce marketplace. His team is the frontline for customer issues, handling everything from order inquiries to technical glitches affecting website flows. They currently rely on a mix of macros, shared inbox rules, and intricate spreadsheets to track escalations and manage their knowledge base. While Aayushman is comfortable discussing technical requirements and potential solutions, the actual implementation of any system changes or integrations is typically delegated to the team's sole developer or a data analyst, given their limited resources. The pressure is constant to maintain high response times and resolution rates without a dedicated budget for advanced tools.
Relationships
Aayushman is married to Priya, a school teacher, and they have a young son, Aarav. His immediate family is his primary support system. He maintains a close circle of friends from college, with whom he discusses work challenges and life in general. Within the company, he collaborates closely with the product and engineering leads, though his primary working relationships are with his direct reports.
How they decide
Aayushman is a methodical and data-driven decision-maker. He prefers to gather information, analyze options, and consider the practical implications before committing. He values input from his team and relevant stakeholders but ultimately relies on logical reasoning and evidence to make choices, especially concerning operational changes. He is not impulsive and tends to weigh potential risks and benefits carefully.
How they sound
Speaks in clear, measured Hindi and English, often code-switching between the two. His tone is generally calm and professional, even when discussing stressful situations. He avoids overly casual slang but uses common professional jargon. He tends to explain his reasoning thoroughly, ensuring clarity. He's not one for hyperbole and prefers factual statements.
Personality traits
- Methodical
- Detail-oriented
- Pragmatic
- Patient
- Analytical
- Reliable
- Collaborative
- Resourceful
Goals
- Streamline support workflows to reduce ticket resolution time by 15% in the next year.
- Develop a more robust internal knowledge base that empowers agents and reduces reliance on tribal knowledge.
- Gain more visibility into customer pain points through better data analysis from support interactions.
- Advance into a more strategic role within the company, potentially leading a larger operations or customer success team.
- Achieve a better work-life balance by automating repetitive tasks.
Problems & frictions
- The current reliance on spreadsheets for tracking complex escalation paths is error-prone and time-consuming.
- Lack of a centralized, easily searchable knowledge base leads to inconsistent answers and agent ramp-up time.
- Difficulty in quickly identifying and diagnosing recurring technical issues impacting customer experience due to fragmented data.
- Limited bandwidth of the development team means operational improvements often face long waiting times.
- Balancing the need for responsiveness with the team's capacity, especially during peak seasons.
- The ad-hoc nature of current tools makes it hard to generate comprehensive reports on support performance.
Values
- Responsiveness
- Reliability
- Team efficiency
- Process improvement
- Customer satisfaction
Interests
- Customer support systems
- Knowledge management
- Workflow automation
- Cricket
- Technology trends
Media habits
- Reads industry blogs (e.g., Zendesk, Intercom)
- Listens to podcasts on productivity and tech
- Follows tech news on LinkedIn and Twitter
- Watches cricket matches