Controlled workflow changes
Test changes on a slice of tickets before you ship them to everyone.
Every app here came from hitting the same wall more than once — tools that didn't exist on the marketplace, security features that cost too much to justify, or workflows I kept rebuilding from scratch at every new team.
Test changes on a slice of tickets before you ship them to everyone.
PII detection and ticket access visibility without the enterprise price tag.
Required context, routing tags, and clean internal notes before tickets move.
Checklists agents actually have to complete before a ticket can be solved.
Focus
Most Zendesk teams have the same short list of operational problems. Missing context on escalations. No way to test workflow changes safely. Sensitive data sitting in ticket comments. Steps that agents skip because nothing enforces them. These apps exist to close those gaps without adding another system to manage.
Everything runs inside your existing Zendesk account. No external backends, no separate dashboards, no new logins for your team.
Set up in an afternoon. Designed so a Zendesk admin can configure, adjust, and maintain without engineering support.
Tags, notes, fields, and checks that plug into the reporting and workflows you already have.
Products
Not built to fill out a portfolio. Built because I kept running into these problems and the marketplace either didn't have a solution or the existing ones weren't quite right.
Roll out Zendesk workflow changes to a controlled percentage of new tickets before enabling them account-wide.
Use it for AI flows, routing changes, escalation workflows, intake forms, survey changes — anything where you want to know it works before you flip it on for everyone.
Most URL builders on the marketplace are almost right. Quick Links lets you build sidebar links that pull from ticket fields, requester data, org fields, and custom values — so agents stop copying and pasting into every tool they open.
Detects sensitive data in ticket comments — SSNs, card numbers, passwords, API keys — and lets agents redact it before it spreads through workflows, integrations, or AI summaries.
Most teams have a process for closing tickets correctly. Almost none of them actually enforce it. ResolveReady adds a required checklist before agents can solve — no triggers, no workarounds, no hoping they remember.
Logs when sensitive tickets are opened — VIP conversations, billing issues, escalations — with a short internal note, tags, and a view log field. Lightweight visibility without turning every ticket into an audit trail.
Escalations fail when the next team doesn't have enough context. Escalation Guard puts a structured form between the agent and the escalation — required fields, routing tags, and a clean internal note automatically added to the ticket.
Principles
The goal is not to make tools feel bigger than they are. Support ops teams have enough complexity. The job is to reduce it, not add to it.
No external systems to manage, no new logins to hand out, no data leaving the account unless you choose to send it somewhere.
If a Zendesk admin can't figure out what it does in the first five minutes, it needs another pass.
Tags, notes, and fields that plug into Explore, views, triggers, and the workflows your team already uses.
About
I've spent years working inside support operations teams, building internal tooling to fill gaps the marketplace didn't cover. Rollout Control came from needing more than a 50/50 split when testing workflow changes. PII Shield and Access Monitor came from teams that needed lightweight data controls without paying for a full enterprise security add-on. Quick Links came from URL builders that were always just slightly wrong for how support actually works.
ASA Labs is where those tools live now — built to be installed in an afternoon, maintained by a Zendesk admin, and useful on day one.
Contact
If you have a question about an app, a feature request, or a support ops problem that keeps coming up — reach out.