Technical support
Technical problems, solved, or ready to fix.
When something in your product isn’t working, the team works through it with your customer and puts it right wherever it can. What needs your engineers reaches them with everything they need to fix it.
What we do
Support for the problems that need someone who knows how it works. Hired, trained and coached by us, working in your systems whenever your customers need it.
L1, L2, or both
However your support is split, the team can take first line (L1), second line (L2) or both, on its own or beside your own people.
As far as you want it to go
Help with set-up and connection only, or every fault the team can work through, and repairs arranged. Changing your product’s code stays with your engineers.
Where a problem ends
Put right by the team. Written up when it can’t be.
Wherever the team can put a problem right, it does. What needs your engineers reaches them confirmed and written up, and the team stays with the customer until it’s fixed.
Smart home brand · Phone
“The doorbell won’t connect to our wifi.”
Invoicing software · Email
“Our invoices have stopped reaching the accounts.”
Software company · Chat
“Our automated emails stopped after we changed plan.”
Field service app · In the app
“The app closes every time I add a photo.”
Worked through with the customer
Put right with the customer
- The doorbell, connected with a router setting on the call
- The invoices, reconnected and the missing ones brought across
- The emails, a setting put back. Not a fault
Recreated and confirmed
A fault in the app, written up for your engineers
The app closes when a photo is added
- Where
- Android, since this week’s update
- Steps
- Open a job, add a photo, choose the camera
- Expected
- The camera opens
- Happens
- The app closes
- Customer
- Told it’s being looked into
Fixed in the next update, and the customers who reported it told.
What we’d take on
Whatever your product, and wherever it goes wrong.
Each kind of problem, worked from the first reply to the end in the systems you already use.
Up and running.
A device connected, an account set up or a new feature working, step by step with the customer.
- Devices paired and connected
- Accounts and settings set up
- Walked through in plain words
- Checked it works before the conversation ends
Phone · Saturday morning
A new smart thermostat
- Connected to the home wifi
- The heating schedule set up with them
- Checked
- The heating came on as planned
Working, and the customer shown how
Worked out, and put right.
An error message, a setting in the wrong place, a permission someone changed. The team finds the cause and puts it right with the customer.
- Error messages traced to their cause
- Settings and permissions checked and corrected
- The customer shown what changed
- What keeps coming up, in your reporting
Email · Monday
Reports showing last month’s figures
- Cause
- A date setting changed by a colleague
- Put back, with the customer
- Shown
- Where the setting lives, for next time
Fixed, and recorded in your helpdesk
Joined up again.
When your product stops talking to the software a customer runs beside it, the team checks the connection end to end, reconnects it and brings across anything that was missed.
- The connection and its settings checked
- Reconnected with the customer
- Anything missed brought across
- A fault in the other software explained, with what to ask them
Chat · Thursday
Orders not reaching the accounts
- Cause
- The connection had expired
- Reconnected with the customer
- The missing orders brought across
Working again, and recorded in your helpdesk
Confirmed, and ready to fix.
When something really is broken, the team recreates it and writes it up for your engineers, with everything they need to fix it. Then it keeps the customers who reported it updated, and tells them when it’s fixed.
- Recreated and confirmed
- Written up with the steps and what was expected
- The customers who reported it kept updated
- Each of them told when it’s fixed
In the app · Wednesday
An export that stops halfway
- Recreated by the team
- Sent to
- Your engineers, with the steps
- Customers told it’s being fixed
Fixed in Friday’s release, and everyone told
Everyone answered at once.
When something stops working for many customers at once, or a release changes how things work, the team answers everyone with the same clear update and tells them when it’s back.
- One clear update, agreed with you
- The same answer for everyone who gets in touch
- Kept up to date while it’s being fixed
- Told when it’s back, without having to ask
Every channel · Tuesday evening
Dashboards not loading after a release
- The same update on chat, email and social
- The same answer for everyone
- Back
- Everyone told, without asking
Working again, and nobody left wondering
Arranged when it needs one.
When working through a fault on a device shows it needs a repair or a replacement, the team checks the warranty and arranges what your policy gives.
- The fault worked through first
- The warranty and proof of purchase checked
- A repair, replacement or return arranged
- The customer kept up to date until it’s sorted
Phone · Monday
A robot vacuum that won’t charge
- The dock and contacts checked with them
- Under warranty
- Arranged
- A replacement dock, on its way
Sorted, and recorded in your system
Off your plate. Still in view.
Everything it takes to run the team, day to day, becomes ours. You keep a clear view of how it’s going.
Yours
What’s yours, and what you see
- Your product, and what gets fixed when
- Your systems, and every case recorded in them
- Regular reviews with the person who owns your service
- Reporting on why your customers get in touch
Ours
Everything it takes to run the team
- Working through every problem, whenever it arrives
- Recreating faults and writing them up
- Finding, hiring and training the team
- The rota, and cover when someone is off
- Coaching and day-to-day management
- Reviewing real cases
How the team is led
Coached where it matters most.
Team leads spend their time with the team, not buried in admin. The reviewing, the planning and the training are shared with people whose job they are.
- Time with the teamOne-to-ones, time to practise, and time to learn what’s new in your product, not squeezed in around the queue.
- Reviewed on how it was solvedWhether they found the cause and not just the symptom, checked it was fixed, explained it in plain words and wrote it up so anyone could pick it up.
- Focused on what each person needsEach person’s coaching centres on where they need it most, from knowing the product in depth to explaining something technical simply. Reviews of real work are one part of that, not the whole of it.
Quality review
Invoices not syncing · Email
- Found the cause, not just the symptom
- Checked it was fixed with the customer
- In plain words
- Written up for the next person
Coaching pointAsk which accounts software they use before suggesting a reconnect.
Ways to work with us.
Whichever suits your product, and the problems your customers bring.
A dedicated teamPeople who work only on your product, sized to the problems that come in.
Alongside your own supportL1 with us and L2 with your people, or the other way round, working as one.
Evenings, weekends, busy spellsWhen your own people are offline, or in the days after a launch.
Shared coverPart of a trained person’s time, for a smaller number of cases.
How we start.
We start from what you already have. Where you already have a way of working through problems, the team works to it. Anything missing, we’ll help you build.
Book a call- We find out how your support worksYour product, what customers need help with, how faults reach your engineers today, and what’s already in place.
- We help you build anything missingTroubleshooting guides, how a fault is written up and where it goes. We work on it with you, and it lives in your systems.
- We recruit the teamPeople hired for your account, at home with technology and good at explaining it.
- They’re trainedOn your product and how your customers use it, from your material or material we help you build.
- A pilot, if you’d like oneThe team takes on part of the work first, such as one product or the hours your people are offline, and we review it together before they take on the rest.
- We go live, and keep improvingWhy customers are getting in touch, what’s behind it, and what to change.
Where the team works.
The right place depends on your customers, the languages they speak and how deep the work goes. You choose where your work is done. We lay out the options and give our view.

The Philippines
Volume and value.A large, experienced talent pool, for teams of any size.

Portugal
European languages.The major European languages, and native or strong English.

Ireland
Specialist and premium work.Specialist roles and premium service, in English and European languages.
Need more than one?Different work in different places, from one provider, on one standard, in one report.
Using more than one locationSecurity and data protection
Your data, protected.
The questions every client asks first, answered plainly.
- Works inside your tools
- Data protection built in
- Managed devices
On your instructions
Your customers' data is used only for your work, as you instruct.
Only the access needed
Set role by role, and shut off the day someone leaves the team.
Never mixed
Each client's information is kept apart from every other's.
Transfers covered
The safeguards your customers' law requires, in place before work crosses borders.
What the price depends on.
Every team is priced for the work it does, so we quote after a conversation, not from a list.
- Where the team worksThe Philippines, Portugal or Ireland, or more than one.
- The languagesEnglish, or other European languages too.
- The hoursIncluding evenings, weekends and other time zones.
- The channelsLive phone and chat need people available in a way email doesn’t.
- Dedicated or sharedAnd how many people the work needs.
- How deep the work goesFirst line, second line, or both.
Where this fits
Three ways we work.
The difference is what you end up with. This page is part of the third, and they join up.
Plan it · Consultancy
Work out what to change
How problems reach your engineers today, where the time goes, and what to fix first. You end up with a plan.
ConsultancyBuild it · Set-up
Put the tools in place
Your helpdesk, the troubleshooting guides your team works from, and reporting on why customers get in touch. You end up with a set-up your own people can run.
Set-upRun it · Delivery
A team that puts problems right
We recruit and manage the team, and run your technical support as part of your business. You end up with problems put right, and faults ready to fix.
This page
Specialist teams
The rest of our specialist teams.
Technical support is one part of it. These are the other specialist teams we run.
Specialist teams
Onboarding, customer success, technical support and premium service.
- Onboarding and successGetting customers started, and keeping them with you.
- Premium and VIP serviceA higher level of care for your most valued customers.
Questions, answered.
The things businesses are likely to ask first.
How do we get started?
With a conversation about your operation and what you need. From there, we work out together where we can help and what comes next.Book a call
Can you take on L2, or only L1?
Both. The team can take first line, second line or the two together, and the split can change as it learns your product.
Can first and second line be in different places?
Yes. The everyday problems could come from the Philippines, for example, and the deeper work from a specialist team in Ireland, on one standard and in one report. You choose where your work is done.Using more than one location
Will the team understand our product well enough?
Yes. Before it takes on a single case, the team is trained on your product and how your customers use it. It keeps learning as your product changes.
Will the team change anything in our code?
No. The team works in your product the way your own support people do. Fixing the product stays with your engineers, and the team makes sure what reaches them is ready to fix.
How will our engineers hear about faults?
However they hear about them now. Each fault is written up with everything they need to fix it, and the team follows it through until it’s fixed.
Can the team answer our everyday questions too?
Yes. That’s customer service, and the same team can do both.Customer service
How do we know how it’s going?
You have one person who owns your service, knows your business and is the one you talk to. How often you meet depends on the work and its size. It might be a short weekly call, a monthly look at the figures and what our quality reviews found, and a quarterly conversation about where your business is going. Anything urgent doesn’t wait for the next call. And you get regular reporting on how the work is going, what we’ve found and what we’re doing about it.Reporting
Is there a minimum size?
No. The work doesn’t need a whole team of its own. It can be part of a team that works for several businesses, or a team of any size built around your work.
Will the team work in our systems?
Yes. The team works in whatever you already use. And if you don’t have the right tools yet, we can help you work out what you need.Set-up
Who it suits
Anyone whose customers need it working.
Most of all, businesses whose engineers keep being pulled away from building to answer support.
- Software and SaaSSettings, errors and connections put right, and faults written up for your engineers.
- AppsProblems in the app worked through, and bugs recreated and written up.
- Media, streaming and publishingSign-in, playback and device problems worked through with your subscribers.
- Electronics, appliance and smart home brandsSet-up and connection help, faults worked through and repairs arranged.
- Games studiosTechnical problems with the game put right, and bugs written up for your developers.
Let's talk.
Tell us what's going on. If we're not the right fit, we'll point you to someone we trust.
Book a call








