Why this persona fits the audience
He leads a 4-person customer support pod at a SaaS company and tracks AI tools for ticket triage, response drafting, and knowledge-base search. He is comfortable trying browser-based tools but typically evaluates them alongside free alternatives and the team’s existing scripts.
- Age: 34
- Location: Hyderabad, India
- Occupation: Support Team Lead
- Income: ₹16L
- Education: Bachelor's in Information Systems
- Company size: 25-50 employees (startup with 1.5M VC funding)
- Years in role: 5
“‘Customer support isn’t about fixing problems—it’s about preventing them. But my boss wants me to fix problems faster, and my team wants me to prevent more problems. I’m caught in the middle.’”
Chetan Varma grew up in Visakhapatnam, the second son of a retired banker and a high school history teacher. He graduated with a BS in Information Systems, took a job at a call center, and quickly rose to team lead. At 27, he joined a VC-backed startup as a support rep and earned his promotion within 18 months. Now 34, he leads a 4-person pod at a SaaS company that helps freelancers track contracts. His biggest challenge is reducing ticket volume without hiring, which pushes him to explore AI tools. He’s a hands-on leader who scripts macros for his team but insists on manual testing ‘just to be sure.’ His team’s knowledge base is a point of pride (it’s grown 40% since he took over), though he admits it’s a ‘patchwork’ of vendor docs and agent notes. He’s frugal with budget but spends freely on self-education—his top expense last year was a course on AI for support. His ‘aha moment’ was realizing that 90% of ticket shrinkage came from better onboarding docs, not automation. He’s skeptical of AI tools that overpromise (‘Last year, three tools promised 50% ticket reduction—none hit 20%’), but he’s open to testing when the setup is free and the claims are modest. His goal isn’t to ‘disrupt’ support but to make it predictable. His team calls him ‘calm in a crisis,’ though he says that’s just his ‘high-neuroticism coping mechanism.’
Background & daily life
A day in their life
Chetan’s alarm goes off at 6:30 AM. He cycles to a gym near work by 7, showers, and eats a banana on the walk to his office. By 9 AM, he’s in his stand-up, reviewing ticket volumes with his team. The first half of his day is spent reviewing high-priority tickets, flagging edge cases for his team’s training docs. At lunch, he grabs paratha from a street vendor and checks Reddit’s r/csreps for workflow tips. Afternoon is spent testing a new AI triage tool (he’s capping it at 10 minutes per test). At 5, he calls his parents. By 8 PM, he’s debugging his team’s Notion setup before poker night. He falls asleep watching a CSAT webinar (he’ll forget it tomorrow).
Lifestyle
Chetan rents a minimalist 2BHK in Jubilee Hills, two metro stops from work. His mornings start with black coffee and a 30-minute cycling session at a nearby park, rain permitting. Weekends are split between cooking elaborate Andhra meals (his mother’s recipes) and debugging his team’s knowledge-base gaps. He’s frugal with subscriptions but splurges on rare used books (cookbooks, tech memoirs). His social circle is tight—mostly former grad school peers and former teammates from his last startup. Money-wise, he avoids debt but saves opportunistically, eyeing a down payment for a Maruti Brezza by 2026. Health-wise, his BP spikes during quarter-end reviews, so he’s attempting meditation (Hims app, 3/7 days).
Work life
Chetan leads a 4-person pod supporting a B2B SaaS tool for freelancers. His days are split: 40% ticket triage (using Zoho Desk), 30% coaching his team, and 30% tweaking workflows. His biggest pain point is ticket deflection—last quarter, 28% of tickets could’ve been resolved by a better knowledge base. He’s experimented with AI drafts (Draftone, a free tool) but hasn’t hit 80% accuracy for contract-heavy replies. His team uses a mix of Slack, Notion, and a self-built Google Sheets dashboard for metrics. His boss, a UX-focused CEO, prioritizes metrics over urgency, which frustrates Chetan when ticket volumes spike. He’s currently testing a referral bonus system to reduce agent attrition.
Relationships
Chetan’s family lives in Visakhapatnam, and he video-calls his parents weekly to teach them WhatsApp tricks. His closest friend, Priya, is a PM at a fintech startup—they debate AI ethics over Filter Coffee at Ramana’s. At work, he’s mentoring Rahul, a junior agent with dyslexia, by creating voice-to-text templates. He respects his boss’s vision but chafes against her “move fast” imperatives. His poker buddies are all ex-startup folks who vent about layoffs (he’s the only one still employed at a startup). His older sister texts him daily memes about office life, which he saves for team culture days.
How they decide
He’s cautious with tools but quick to prototype solutions. He gathers data first (always screenshots metrics), then pilots internally before committing. He’s peer-influenced but prefers Reddit and LinkedIn threads to sales calls. His last 3 purchases were all recommended by someone he respects: his coworker’s laptop, his sister’s phone, and his mother’s recipe app. He avoids flashy demos but will try a tool if it’s free and integrates with Google Sheets.
How they sound
Chetan speaks in measured, logical cadences but drops Hindi slang with coworkers. He avoids jargon (calls himself a ‘triage guy’ over ‘support lead’) and uses analogies (his favorite: ‘Our KB is like a ramen cup—simple ingredients, but if one’s bad, the whole thing is ruined’). He’s quick to laugh at his own mistakes (e.g., ‘I just spent 2 hours setting up Yeti, a free tool, and it crashed on Day 2—my fault for not RTFM’). He defaults to formal emails but sends memes in group chats. He never says ‘disruptive’ or ‘synergy’ unless mocking VC buzzwords.
Personality traits
- Analytical but pragmatic (avoids theorizing without use-case testing)
- Methodical in evaluating tools (tests for 2 weeks before team rollout)
- Slightly skeptical of AI hype (prefers tools with clear ROI)
- Socially warm but task-focused in meetings
- Self-taught in basic scripting (keeps a Google Sheet of automation ideas)
- Financially conservative (justifies expenses with ROI data)
- Patient with repeated tickets but frustrated by vague complaints
- Quietly ambitious (eyes team expansion when metrics hit 20% growth)
- Fond of low-stakes gambling (plays poker twice monthly with coworkers)
- Metaphorically sees customer support as 'triage' (medical framing)
Goals
- Reduce average response time from 4.2 to 3.5 hours by Q3
- Automate 30% of repeat ticket types before year-end
- Lead a 5-person team by 2025 (without burning out)
- Build a personal brand as a ‘support ops’ thought leader (1,000 LinkedIn followers)
- Cook his mother’s original dinner for his cousins’ visit in August
- Earn a CSAT score of 95% for 3 consecutive quarters (current: 89%)
Problems & frictions
- AI drafting tools hallucinate legal jargon, prompting customer confusion
- His team’s scripts don’t cover 25% of edge cases (outsourced content quality)
- Compensation is uncompetitive vs. peer startups (analyzed Glassdoor)
- Notion’s search function fails when agents use inconsistent tags
- He’s juggling 3 overlapping projects (ticket automation, agent training, knowledge-base overhaul)
- His manager expects “data-driven decisions” but rejects his proposed budget for AI tools
Values
- responsiveness
- service quality
- stability
- efficiency
- autonomy
Interests
- customer support software
- ticket workflows
- AI knowledge bases
- productivity hacks
- budget-friendly tech
Media habits
- LinkedIn for industry news
- Reddit (r/csreps, r/AItools)
- YouTube (tech reviews)
- Flipboard (productivity)
- spot-checks Twitter for SaaS trends