Why this persona fits the audience
He manages a 5-person support team that records screens when a customer issue needs escalation to engineering. The team usually drafts the follow-up in ClickUp or a spreadsheet, with each recording summarized into a single ticket and the relevant moment called out in text.
- Age: 38
- Location: Manchester, UK
- Occupation: Customer Support Lead
- Income: £56k
- Education: BSc in Business Management
- Company size: 45 employees
- Years in role: 4
“If I can't point to the exact second a problem happened, I can't fix it properly.”
Arnold Macejkovic is a 38-year-old Customer Support Lead based in Manchester, UK, earning £56,000 annually. Holding a BSc in Business Management, he entered the tech sector eight years ago after a stint in general administration, quickly rising through the ranks due to his innate ability to translate technical jargon into actionable business insights. Currently leading a team of five at a mid-sized SaaS company, Arnold is the guardian of the team's reputation for reliability. His work environment is defined by a delicate balance: managing the emotional labor of dissatisfied customers while ensuring the engineering department receives high-fidelity data to resolve issues efficiently. Arnold's professional reality is deeply rooted in process optimization. He currently oversees a workflow where screen recordings are manually reviewed, summarized, and tagged with specific timestamps before being converted into tickets in ClickUp. This manual intervention, while thorough, consumes a significant portion of his week, often forcing him to choose between strategic planning and operational firefighting. Despite the tedium, he finds deep satisfaction in the structure he has built; his team knows exactly what is expected, and he prides himself on the fact that no critical bug is ever lost in translation. His personal life mirrors his professional ethos. Living in a terraced house in Chorlton with his partner and dog, Arnold values routine and predictability. He is not a risk-taker financially or socially, preferring to invest in proven methods and relationships. His interests in coffee brewing and football reflect a desire for control and community; he enjoys the precision of measuring coffee grounds just as much as the tactical nuances of a football match. Recently, Arnold made the decision to pause hiring for a junior manager role, choosing instead to invest in training his current team to handle more complex escalations. This move was driven by a belief that his current resources were sufficient if leveraged correctly, a testament to his conservative yet pragmatic approach to resource management. He remains acutely aware of the limitations of his current toolset, often finding himself wishing for automation that doesn't compromise the detail he holds so dear.
Background & daily life
A day in their life
Arnold starts his day with a meticulous coffee ritual, reading the morning news before opening his laptop. By 9:00 AM, he joins the daily stand-up, listening intently to blockers. His morning is dominated by reviewing escalated tickets from the previous night, manually highlighting timestamps in video files and drafting clear summaries in ClickUp. Around noon, he tackles administrative duties: updating the knowledge base and analyzing weekly metrics. Lunch is a quick sandwich at his desk or a walk around the block with Barnaby if he's lucky. Afternoons involve coaching sessions with junior agents, role-playing difficult customer calls, and troubleshooting technical issues. He spends his last hour preparing the next day's backlog and ensuring all pending escalations are logged. He shuts down precisely at 5:30 PM, leaving work behind to focus on dinner and relaxation.
Lifestyle
Arnold lives in a well-kept Victorian terrace in Chorlton, sharing rent-free ownership with his partner. His mornings are ritualistic: he wakes at 6:15 AM to brew a precise pour-over coffee using a V60, weighing beans to the gram before checking emails. He is an avid follower of Manchester City, often attending home games if work permits, but prefers watching from the local pub on match days. Financially, he is cautious; while he earns a solid middle-class income, he prioritizes paying off his mortgage early and avoids luxury gadgets unless they offer clear utility. Socially, he maintains a small circle of close friends, mostly from university or long-term colleagues, preferring deep conversation over large parties. He takes weekends off strictly to disconnect, though he often ends up tidying the garden or planning the next week's schedule.
Work life
As the lead of a five-person support team, Arnold spends his days bridging the gap between frustrated customers and busy engineers. His workflow is heavily manual: when an issue arises, an agent records their screen while narrating the bug, then Arnold manually transcribes key moments into ClickUp tickets or spreadsheets. He is constantly refining these internal processes to ensure nothing slips through the cracks. The pressure comes from maintaining high SLA response times while ensuring engineering teams aren't flooded with vague reports. He reviews every escalated ticket personally before it leaves his desk, acting as a quality gatekeeper. His team looks to him for stability, and he derives satisfaction from seeing complex bugs resolved because his team provided crystal-clear context.
Relationships
Arnold is married to Sarah, a primary school teacher who keeps his life grounded outside of tech. They have a Golden Retriever named Barnaby who gets walked twice daily. His closest friend is David, a former university roommate now working in logistics; they meet for a pint every fortnight to discuss football and family. At work, he has a strong, respectful relationship with the Head of Engineering, though they occasionally clash over priority. He relies heavily on his five direct reports, treating them as a unit rather than individuals, fostering a culture where admitting mistakes is safe as long as the fix is proposed.
How they decide
Arnold is a cautious, evidence-based decision-maker. He rarely adopts new tools without seeing a pilot run or a detailed case study from a peer in a similar industry. He values data over hype and will often request a trial period to measure actual time savings before committing budget. While he listens to team feedback, the final decision rests on whether the solution aligns with established company processes and offers a clear ROI. He is skeptical of 'magic bullet' claims and prefers incremental improvements that integrate seamlessly with existing stacks like ClickUp.
How they sound
Arnold speaks with a soft Mancunian accent, calm and measured. He avoids slang, preferring precise, professional language even in casual chat. He tends to pause briefly before answering questions to ensure accuracy, valuing clarity over speed. In meetings, he asks clarifying questions about process flows rather than jumping straight to solutions. He avoids hyperbole, never saying 'amazing' or 'terrible,' instead opting for 'effective' or 'inefficient.' He is polite and deferential but firm when discussing standards and deadlines.
Personality traits
- meticulously organized
- calm under pressure
- pragmatic
- loyal to his team
- methodical
- slightly reserved
- detail-oriented
- process-driven
- reliable
- conservative spender
Goals
- Reduce the time spent on manual ticket documentation by 20% within the next year
- Achieve a perfect 10/10 CSAT score for the engineering handover process
- Mentor two junior agents to take on lead responsibilities within three years
- Implement a more robust knowledge base that reduces repeat escalations
- Maintain a stable work-life balance to avoid burnout during peak seasons
- Save enough capital to fund a sabbatical trip to Japan in five years
Problems & frictions
- The current manual transcription process consumes roughly 15 hours of his week, leaving less time for strategy
- Inconsistent detail in engineer tickets leads to 'ping-pong' back-and-forth delays
- Difficulty tracking the exact timestamp of a reported bug across multiple recordings
- Team fatigue from repetitive data entry tasks affecting morale
- Lack of visibility into which types of bugs occur most frequently without manual analysis
- Managing conflicting priorities between immediate customer fires and long-term process improvement
Values
- responsiveness
- team reliability
- customer trust
- process consistency
Interests
- support tooling
- knowledge bases
- football
- home coffee brewing
Media habits
- Morning BBC Radio 4 news podcasts
- TechTwitter for SaaS trends
- Local Manchester football match highlights
- Specialty coffee YouTube channels