On this page
What our technical support is
Technical support is direct access to an engineer who knows your websites, applications, servers and integrations, for questions, problems and urgent issues. You reach a named person by WhatsApp, email or phone, and that person already has the context: how the system is built, where it is hosted, what changed recently and what went wrong last time.
There is no first-line script and no explaining your problem three times to different people. The engineer you speak to is the one who investigates.
Support covers the whole stack we have agreed to look after — the website or application, the server it runs on, and the integrations that connect it to payment gateways, CRMs, messaging platforms or your ERP. When a problem crosses those boundaries, which many do, one engineer follows it through rather than handing it between separate providers who each say the fault lies elsewhere.
Who it’s for
Businesses whose operations depend on software but who do not employ their own full-time engineers. A clinic whose booking system must work every morning, an e-commerce store whose checkout cannot be down during a sale, a real estate agency whose portal and lead forms feed its sales team, a SaaS startup that needs backup engineering capacity, or a manufacturer whose web orders sync with its ERP.
- You have no clear person to call when the site or system stops working.
- Your previous developer or agency is slow to respond or no longer available.
- Every issue starts with re-explaining how the system works.
- Problems wait until someone “has time”, with no agreed response.
What’s included
- A named engineer who learns your system and remains your main contact.
- Agreed response times by priority, written into the support agreement.
- Multiple channels — WhatsApp, email or phone, whichever suits the situation.
- Diagnosis and resolution of incidents, from outages to misbehaving features.
- Guidance for your team on using, configuring or extending the system.
- A system record — access details stored securely, architecture notes and a history of incidents and changes.
- Optional out-of-hours cover where your business needs it.
How it works
- Onboarding. We review your systems, collect access securely and document the architecture, integrations and known issues.
- Agreement. We agree priority levels, response targets, channels and working hours, and put them in writing.
- Raising an issue. You contact your engineer directly, with as much detail as you have.
- Response and triage. We acknowledge, assess impact and agree priority with you.
- Resolution. We restore service first where needed, then fix the underlying cause.
- Follow-up. You get a short explanation of what happened and anything that should be done to prevent a repeat.
Response times and priorities
Response times are agreed with you rather than set by a generic template. A business that trades online at weekends needs different cover from one whose system is used only during office hours. Typical priority levels distinguish between a full outage, a key feature broken, a minor fault and a general question, each with its own target.
What affects scope and effort
The main factors are the number and complexity of systems covered, the hours of cover needed, the response times you require, and the current condition of the systems. Well-maintained systems generate fewer incidents, which is why support is often combined with Long-Term Maintenance. Inherited systems with little documentation need a more thorough onboarding before support can be fully effective. Out-of-hours cover, where your business needs it, is agreed in writing along with the response times that apply to it.
Common mistakes
- Waiting for an emergency before finding a support provider, so onboarding happens mid-crisis.
- Keeping server, domain and hosting access with a single person who may become unavailable.
- Reporting issues without times, affected accounts or screenshots, which slows diagnosis.
- Having no written agreement, so expectations differ on both sides.
- Sharing passwords over chat instead of setting up individual, revocable access for the support team.
Frequently asked questions
Will I always speak to the same engineer?
You have a named engineer as your main contact. For cover during leave or out-of-hours, a colleague who has access to the same system notes steps in, so you still don’t have to start from scratch.
How do I contact support?
By WhatsApp, email or phone, as agreed during onboarding. Urgent issues and routine questions can use different channels.
Do you support systems you didn’t build?
Yes. Onboarding includes reviewing and documenting the system, so we understand it before the first issue arrives.
What if the issue is with a third-party service?
We diagnose where the fault lies and, if it is with a vendor such as a hosting provider, payment gateway or messaging API, we work with them on your behalf where possible.
What do you need from us to get started?
Access to the systems we will support, any existing documentation, and a short conversation about how your business uses them and which parts matter most. We collect access securely and document the rest during onboarding.
Talk to us about technical support
A real engineer to reach when something breaks, not a ticket queue and a wait.