FAQ

What are the stages of a website maintenance or repair job?

A website maintenance or repair job usually starts with triage and an initial audit, followed by diagnosis, scope confirmation, remediation, testing and monitoring. Timing depends on the issue, access, third-party systems and severity. Emergency support is available, with typical response times within 4 hours, although ad hoc work outside an SLA is quoted before commencement.

A website maintenance or repair job with Dobble starts by understanding what is broken, how urgent the issue is and which systems are involved. Some problems are simple, such as a broken form, display error or content issue. Others can involve hosting, DNS, security, email delivery, database problems, third-party plugins, payment systems or unauthorised changes.

The first stage is triage. Dobble reviews the symptoms, business impact and urgency of the issue. For example, a website that is offline, hacked, not sending enquiries, or has a broken checkout is treated differently from a lower-priority layout issue or routine maintenance request. For hosting, maintenance, domain and email clients, support is available 24 hours a day, 7 days a week. Emergency support is available, with typical response times within 4 hours. Where a client is outside an SLA, emergency work is charged on an ad hoc basis, with quotes, predictions or capped timing supplied before work begins where applicable.

The second stage is diagnosis. Dobble may review the website, hosting environment, error logs, CMS behaviour, DNS records, email configuration, security alerts, backups, performance data or third-party integrations depending on the issue. For third-party or legacy websites, this stage is particularly important because the cause may sit outside Dobble’s own systems. Examples include plugin conflicts, outdated software, compromised credentials, external APIs, payment gateways, registrar issues or client-side changes.

The third stage is scope confirmation. Once the likely cause and level of work are understood, Dobble can confirm what needs to be repaired, what falls within an existing maintenance or SLA arrangement, and what may need to be quoted separately. This is important because maintenance plans only cover the services included in the client’s selected plan, and issues caused by third-party platforms, unauthorised changes, client actions or external providers may require additional work.

The fourth stage is remediation. Depending on the problem, this may include malware removal, restoring files or data where backups are available, fixing broken forms, repairing checkout issues, correcting display or mobile errors, resolving database problems, improving speed, applying software updates, addressing plugin conflicts where relevant, correcting DNS records or strengthening security settings. Dobble’s approach is practical and technical: the aim is not only to patch the visible symptom, but to understand why it happened and reduce the chance of it happening again where possible.

The fifth stage is testing. Repairs are checked across relevant devices, browsers, forms, workflows and integrations. If the issue affects enquiries, checkout, email notifications or other business-critical functions, those pathways are tested carefully. Where changes are substantial, Dobble may use a secure staging environment before deploying updates to the live website, depending on the nature of the repair and the client’s setup.

The sixth stage is monitoring and prevention. For ongoing maintenance clients, Dobble may configure or review security monitoring, performance monitoring, uptime monitoring, backups, software updates and technical maintenance routines. This preventative approach is designed to reduce the risk of avoidable downtime, security issues and emergency repair costs over time. Dobble’s proprietary Genesis CMS also helps reduce reliance on large third-party plugin stacks for Dobble-built websites, which can lower the risk of plugin conflicts common on some off-the-shelf platforms.

There is no fixed timeline that applies to every maintenance or repair job. Timing depends on the severity of the issue, the quality of access provided, whether backups are available, whether third-party systems are involved, and whether the problem is isolated or part of a wider technical issue. Dobble will explain the likely next steps once the problem has been assessed.

It is also important to set realistic expectations. Maintenance, monitoring and security work can reduce risk, but no provider can guarantee protection against every cyber threat, third-party outage, software vulnerability or interruption. Dobble is responsible for services and systems directly under its control and may assist with third-party issues where practical, although additional charges may apply where the work falls outside the client’s SLA.

Ready to start?

Let's build something that works for your business.

Get a tailored quote or send us your question — the team is here to help.

Get started Ask a question

Keep exploring

Tap to call
Enquire now

Ask Dobble

Ask a question

Send us your question and the Dobble team will get back to you.

Prefer to talk to us directly?

Get in touch

Contact us

Tell us about your project and the Dobble team will be in touch shortly.

Prefer to talk to us directly?