Technical support,
with the person still in view.
For the last five years, much of my professional work has taken place in technical support.
Behind each ticket is somebody trying to do something.
The systems I support can sit behind banks, hospitals, community services and organisations trying to stay connected to people who depend on them. A failed call, routing issue or unexpected API response may be the technical symptom; the consequence exists beyond the ticket.
Context before conclusion.
My role often sits between the person affected by a problem and the technical teams investigating it. The useful work is turning impact, sequence and evidence into a shared account of what is happening and what should happen next.
A signal, not a scorecard.
Focus or tap an indicator to inspect the context behind each figure.
Rounded figures from separately reviewed Salesforce and Jira records, to 16 October 2026. These activities can overlap and are not counts of distinct customer incidents. Closed or completed workflow status does not alone verify customer resolution. Indicator bars are illustrative, not measured comparisons.
Not a tally of hours.
A record of becoming.
The role grew from resolving individual issues to strengthening escalation evidence and helping others investigate, communicate and grow.