Home / Work / Veyra · Software & AI

61% of support tickets resolved without a human for Veyra.

61%
of tickets resolved without a human
8 min
median first response, down from 4 h
–34%
cost per ticket
10 wk
to production
Client
Veyra
Industry
SaaS
Service line
Software & AI development
Timeline
10 weeks, 2026
Stack
TypeScript · Python · LLM APIs · Zendesk
Budget band
$50K to $150K
Team
3 people

Support headcount was growing faster than revenue

Veyra's support queue grew with every new customer. Eighty per cent of tickets were the same six questions, but each one still needed a human to read the account, check the billing record and write a reply.

The plan on the table was to double the support team. We proposed resolving the repeatable ones instead.

An agent that answers, and knows when not to

We built a triage agent inside the existing helpdesk. It reads the ticket, pulls the account and billing context, and answers directly when it can cite a policy or a record. Anything ambiguous routes to a human with the context already attached.

The threshold is tunable and observable: every routing decision is logged with its confidence and its evidence, so the team can see exactly why a ticket went where it went.

support-copilot
Ticket triage61% auto
The review console: every routing decision with its confidence and the evidence behind it.
support-triage · this hour
11:40:02  #8341 refund status: account and billing record read
11:40:03  policy cited, reply drafted and sent
11:41:17  #8343 duplicate charge: ambiguous, confidence low
11:41:17  routed to a person, context attached
no refund or cancellation without a human
Two tickets, two outcomes. Both decisions are logged either way.

The queue stopped growing with the customer count

Measured across 90 days in production against the previous quarter, from Veyra's helpdesk export.

MeasureBeforeAfter
Tickets resolved without a human0%61%
Median first response4 hours8 minutes
Cost per ticketbaseline–34%
CSAT4.4 / 54.5 / 5

In their words

We were about to hire six people. Instead the queue shrank and the team spends its day on the tickets that actually need a person.
JO
Jonas Ortega
Head of Support, Veyra

What we would do next

Proactive outreach: the same context layer can spot accounts heading for a problem before they write in. Scoped at $30K to $50K, 6 weeks.

Nothing here is committed. It is the honest answer to the question the client asked at handover, and the estimate we gave for it.

Scope a phase like this

Team on this project

PS
Priya Shah
AI engineer · agent and evaluation harness
AN
Alex Novak
Product lead · routing thresholds and rollout
TL
Tomas Lind
Designer · the agent review console

The same people who scoped it built it. No handover to a delivery pod.

Related work

Questions about this project

Anything below the confidence threshold routes to a human by default, and every answer is reviewable. Agents never take a destructive action — refunds and cancellations always need a person.

Have a product like this to build?

Thirty minutes answers fit and gives you a rough number. Alex Novak, delivery director, replies within one business day, and the written plan with a fixed price usually follows within a week.

Get an estimate