The L2 Ticket Pack
Up to 40 of your customers' technical tickets a month investigated properly — logs read, the fault reproduced in a test account, and every one written up so your engineers start from evidence.
A customer reports that something is broken. Nobody can tell from the ticket whether it is a bug, a misconfiguration or a misunderstanding, so it lands on an engineer who spends forty minutes finding out before the real work can start.
We take that queue. Responders with system-administration backgrounds read the logs you nominate, inspect the integration, and try to make the fault happen in a test account — three times, from a clean start — before anybody says a word about a cause.
What reaches your tracker is a reproduction: steps, environment, evidence, and an honest note where it would not reproduce. We change nothing in your product and write no code. The fix stays yours; the triage that makes it fast is what you are buying.
What's included
- Up to 40 technical tickets a month, counted by rules published before you buy — and a fault that refuses to reproduce still gets the full write-up, because that is a finding
- A first response from a person within four working hours, or two on the lane you define, with every miss and its reason printed in your monthly report
- Faults reproduced in a test account, three attempts from a clean state, and filed in your tracker to the same standard our QA testers write to
- Logs and integrations read, never touched — every access is read-only, and the full list comes back to you the day you ask for it
- A known-issue register kept current, so four responders describe the same fault the same way instead of four ways
- A promise matrix you approve before the first ticket, so nobody admits fault, promises a release date, or names a cause we cannot prove
- Recurring faults counted and set beside last month — the page that tells you what to fix rather than what to staff
How it works
- 01
Book it
Pay the fixed price and tell us what you need. No scoping call first.
- 02
We deliver
An experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in The Orchard.
- 03
Hand-off
You get everything listed on this page, with notes on what was done, and a walkthrough if you want one.
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
- Documentation for your product (a knowledge base or troubleshooting notes) and a test account outside production where we can reproduce faults. We cannot start without both
- A seat for us in your help desk, created by you, the queues we should work, and the tracker where reproduced faults go: Jira, Linear, GitHub or similar
- Read-only access to any application logs you want us to check, and the channel for The L3 Ticket Pack if you hold it
- Your published policies and help centre, the name our replies carry, and your decisions on what we may say without asking
- A person who takes our escalations during our hours, a backup, and your own definition of a ticket that must jump the queue
Who does it
A salaried Cherry VAs specialist with more than ten years in the field, working from a runbook we have been refining since 2007, supervised by senior management and never a marketplace contractor. You will see who is assigned, and can message them about this task directly in The Orchard.
Who it's for
A software or IT business whose engineers keep getting pulled off the product to decode support tickets that arrive half-described.
FAQ
What makes a ticket second-line?
Four things, and they are checks rather than opinions. Answering it needs evidence that is not on the person's own record, such as a log or a stack trace. Or it needs the fault reproduced before an honest answer exists. Or it needs a look at your configuration — API keys, webhooks, DNS, single sign-on, an import mapping. Or a documented answer has already been given and did not work. Any one of those and the ticket is ours; none of them and it belongs in a first-line queue at a quarter of the price. Every ticket is tagged with the trigger that fired and your monthly report prints the counts.
Do you fix bugs in our product?
No, and that boundary is what makes the write-up worth reading. We diagnose, reproduce and document, so your developers receive a confirmed fault with steps rather than a complaint to decode. Every access we hold is read-only: no code, no production configuration, no feature flags, no database writes. The one exception is a rule you write yourself with an objective trigger and a fixed action inside your product's own interface, and every execution is listed in your report. If your developers need the cause found in the code, The L3 Ticket Pack puts a senior engineer into your source with our write-up, and small fixes come back as pull requests.
What do you need from us before you start?
Two things, and without either we will not start. A knowledge base or troubleshooting documentation, and a test account that is not production. A responder investigating an undocumented product with nowhere safe to reproduce is guessing in your name, and guessing in your name is the most damaging thing this service could do. If you have neither, the honest first step is a Technical Support Agent Day or two spent writing that material from your own ticket history — real work with a real output, and we would rather say it now than in month two.
Do we need the L1 pack as well?
Only if your easy tickets are still landing here. This pack stands alone, and a simple question that arrives in it gets answered rather than bounced back — but it spends one of your forty. Forty technical tickets cost US$750; a hundred and fifty routine ones cost US$710, which is about four dollars a ticket against nineteen. Your report shows the share every month, and if more than a third of your second-line queue turns out to be first-line questions, we will say so instead of quietly billing you for the wrong product.
How does the month work, and when should we hire an engineer instead?
We work weekdays, 06:00 to 22:00 Philippine time, with a first response from a person within four working hours — never a resolution time, because the fix runs in your product on your schedule. There is no weekend or North American business-hours cover. Month one is the setup month at 26 tickets with an onboarding record instead of a report. Past about 65 technical tickets a month, a dedicated agent from us, from US$1,199 a month, costs less than this pack, and we would rather tell you than let you find out.
Related services
- Websites
The Article Enhancement
Images, a chart, real quotes and sourced statistics added to one finished article of up to 1,500 words, each figure linked to where it came from. Your sentences stay as you wrote them.
$60 From $30 on a plan
- Websites
The Blog Article
One new blog article of 800 to 1,500 words, written from your brief, edited by hand and checked fact by fact. It comes with images and sourced figures, and its search and link-sharing details are filled in.
$120 From $60 on a plan
- Websites
The Chat Support Starter
Live chat on your website in your colours, set up in your own tawk.to, Crisp, Tidio or HubSpot account, tested end to end, with your team trained to answer it from a browser or their phones.
$230 From $115 on a plan