persona
Personal & Professional Profile

Hannah is a business-side customer who contacts support when the software interrupts real operational work. She values speed, clarity, and signs that the support team understands the practical impact of her issue rather than treating it like a generic ticket.

Roles and Responsibilities
  • Keep operational workflows running smoothly for her team

  • Report software issues that block or slow critical work

  • Coordinate with internal users to gather issue details and impact

  • Balance support follow-up with the rest of her operational workload

  • Escalate internally when software downtime affects service delivery

Key Traits
  • Organized

  • Direct

  • Resilient

  • Pragmatic

  • Results-focused

A Day in the Life Of Hannah Brooks
  • Morning: Checks team operations, usage issues, and anything blocking task completion

  • Late morning: Submits support requests for unresolved software issues affecting staff

  • Afternoon: Follows up on open tickets while juggling deadlines and team coordination

  • End of day: Updates stakeholders on issue status and workarounds if support has not resolved the problem

Goals and Pain Points

Goals:

  • Get software problems resolved quickly so her team can keep working

  • Know whether an issue is urgent and who is handling it

  • Avoid repeating the same context across multiple support interactions

  • Receive responses that are useful, specific, and appropriate to the seriousness of the issue

Pain Points:

  • Support forms often feel like they disappear into a black hole after submission

  • She loses time when she has to explain the issue again after being transferred

  • Generic responses make her doubt whether anyone understood the business impact

  • Delays in routing technical issues can disrupt her team’s daily operations

Special Skills
  • Operational coordination

  • Issue reporting

  • Stakeholder communication

  • Process troubleshooting

  • Priority management

Background

Hannah works in operations for a field services company that depends heavily on software to coordinate day-to-day work. She is not a technical specialist, but she is often the person who notices process friction first because she sees how system issues ripple into missed appointments, internal confusion, and team frustration.

Motivations
  • Keep her team productive and avoid avoidable downtime

  • Feel heard and taken seriously when reporting an issue

  • Get clear next steps instead of vague reassurance

  • Build confidence that the software vendor can support the business reliably

Scenario

Hannah submits a ticket when a workflow in the software starts failing for multiple team members just before a busy afternoon window. She wants quick acknowledgment, confidence that the urgency has been recognized correctly, and a response that reflects her actual problem rather than a generic canned answer. If the case needs a specialist, she wants that handoff to happen quickly and without having to restate everything.