The L3 Ticket Pack
Up to 10 escalated faults a month taken into your code by a senior engineer. You get the cause with the evidence behind it, and small fixes arrive as pull requests for your team to review and merge.
Your support team has reproduced the bug. They can show it happening but not why, so the ticket waits on a developer's list until the sprint has room, and your customer waits with it.
Send it to us. A senior engineer from our India team reads your code and logs, runs the product from source in your staging environment, and comes back with the cause and the evidence for it. Where the fix is small, you also get a pull request with a test that fails before the change and passes after it.
Your team reviews, merges and deploys. We can read production but cannot change it, and each escalation stops at four engineer-hours, so you can see what every escalation cost and where the time went.
What's included
- Up to 10 escalations a month, each with up to four hours of a senior engineer, and a written report on every one, including those where the cause stays hidden
- A first response from an engineer within four working hours of our L3 shift and findings within three working days, with every miss and its reason in your monthly report
- Causes backed by log lines, traces and code paths, and marked established, probable or not established, so your team knows how far to trust each one
- Small fixes sent as pull requests with a test that proves them, passing your own linter and test suite before you see them
- Read-only production: we read your logs, metrics and infrastructure, and change nothing there
- Recurring causes counted against last month, so you can see which part of the product keeps breaking
How it works
- 01
Book and send access
Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.
- 02
We do the work
An experienced employee who specialises in this task works through it, and asks before anything outside the scope.
- 03
Delivered with evidence
You get everything listed on this page, with a written account of what was done.
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
- Access to your code: up to three repositories on GitHub, GitLab, Bitbucket, Azure Repos or self-hosted Git, with permission to push branches named l3/ (or work from a fork) and your main branch protected
- A staging or local setup where our engineer can run the product from source, with any secrets it needs already in your own secret store
- Read-only access to your error tracker and logs, plus a viewer role on your cloud account or cluster if you want infrastructure checked
- A second line that reproduces faults before escalating: our L2 Ticket Pack or your own support team, with up to five named people who may escalate
- An engineering contact who reviews our pull requests and decides what happens when an escalation reaches four hours
Who it's for
A software company on PHP, Python or Node whose support team can reproduce faults but not explain them, and whose developers keep losing sprint days to the investigation.
Questions
What makes an escalation third-line?
To find the cause, someone has to read your code, look below your application at server, database or queue logs, or run the product from source. Your second line must have done its part first: the fault reproduced, or tried three times with what they saw written down. Anything else goes back to you with a note saying where it belongs, and it does not use one of your ten. Your monthly report lists the accepted and the returned.
Will you fix the bug and deploy it?
We write small fixes, up to about 150 lines across five files, as a pull request with a test. Your team reviews, merges and deploys it through your own pipeline. Bigger fixes, such as a refactor, a data migration or a framework upgrade, come as a written plan for a Developer Day, and server changes come as exact instructions for your team or The Server Admin Day. We do not write to production, and that includes restarting a server during an outage.
What happens when four hours isn't enough?
Our engineer stops and files what they have: what is established, what is ruled out and what is left. You choose whether to close it, continue for four more hours (using one more of your ten), or take the findings to a Developer Day as the starting point. Each problem can be continued once. A fault that has resisted eight hours of senior engineering needs planned time.
When do your engineers work?
Weekdays, 14:00 to 22:00 Philippine time, which is 11:30 to 19:30 in India. That covers the working day in India and the Gulf, and the morning in the UK and Europe. For Australia, New Zealand and North America it falls overnight: raise an escalation in your day and the findings are usually waiting the next morning, but nobody can help you live during an outage. We commit to response and findings times and not to a resolution time, because the fix ships through your pipeline.
How does the month work, and when is a dedicated developer cheaper?
Month one is the setup month at six escalations. Our engineer gets your product running, writes notes on how it fits together, and you receive an onboarding record instead of a report. From month two you have ten, and unused escalations do not roll over. If you use all ten two months running, a dedicated developer from US$1,199 a month will usually cost you less, and we will tell you so.
Often booked alongside
- 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.
A$90 From A$45 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.
A$180 From A$90 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.
A$345 From A$172.50 on a plan