What Is 24/7 Critical Incident Cover?

24/7 critical incident cover is an on-call service in which a named engineer stays available outside business hours, including nights, weekends and public holidays, to respond to severe production problems within a guaranteed time. Codersarts offers 24/7 critical incident support as an add-on to Managed Run: if your application goes down, puts data at risk or threatens to send duplicate emails at 3 am on a Sunday, someone responds within 30 minutes.

24/7 Critical Incident Cover at a Glance

Why Business Hours Are Not Enough for Some Apps

A working week of 9 hours a day, 5 days a week covers 45 of the 168 hours in a week. The other 123 hours, about 73% of the week, fall outside business hours. If your application only matters during office hours, that may be fine. Many applications do not work that way:

• Scheduled jobs run overnight, such as content publishing, report generation or data syncs

• Customers are in other timezones, so your night is their working day

• Emails and notifications go out at weekends, and a failure can affect hundreds of recipients

• Payments and orders arrive at any hour, so downtime means lost revenue

• A single failure can repeat, such as a job that keeps retrying and sending duplicates until someone stops it

Business Hours Only vs 24/7 Critical Cover

What Counts as a Critical Incident

24/7 cover is for the problems that cannot wait. Everything else is handled in business hours under Managed Run.

How an Out-of-Hours Incident Is Handled

1. Detection

Monitoring detects the problem automatically, or you report it by phone through the agreed critical-incident line.

2. Paging

An alert pages the on-call engineer directly. Critical alerts do not wait in an inbox.

3. Acknowledgement Within 30 Minutes

The engineer confirms the incident and starts working. You are told who is handling it.

4. Investigation Within 1 Hour

The engineer is actively diagnosing the cause. Where there is a risk of duplicate delivery or data damage, sending and publishing are paused first.

5. Recovery Within 4 Hours

The service is restored by a fix or a safe workaround. If the cause lies with your cloud provider or another platform, we coordinate with them and keep you informed.

6. Root-Cause Note Within 3 Business Days

You receive a short written explanation of what happened, why, and what will stop it happening again.

How Billing Works

The $250 monthly fee pays for availability: a named engineer kept on standby, with paging and escalation in place, every night, weekend and holiday of the month. Work on incidents is handled fairly and transparently:

If the same issue causes repeated incidents, we propose a permanent fix with an estimate, so you are never paying for the same problem twice.

Acknowledgement, Investigation and Recovery: What Each Target Means

Support contracts often blur three different promises. We keep them separate:

Recovery and permanent fix are different on purpose. At night, the priority is getting the service back safely. The deeper fix follows in business hours, with your approval.

Example Incident Timeline

This illustrative timeline shows how a critical incident at night is handled.

How We Communicate During an Incident

• You are told who is handling the incident as soon as it is acknowledged

• You receive updates at key points: cause found, recovery in progress, service restored

• Decisions that affect your business, such as pausing sending or restoring from backup, are explained before they are taken where time allows

• Every incident ends with a written summary, followed by the root-cause note

Preventing Incidents Before They Happen

The best night-time incident is the one that never happens. Under Managed Run, we reduce the chance of out-of-hours emergencies by:

• Alerting on early warning signs, such as disk space, memory growth and repeated job failures

• Applying security and dependency updates in planned maintenance windows

• Testing restores every month, so recovery is fast when it is needed

• Turning every root cause into a permanent fix proposal

24/7 Cover Compared With Building Your Own On-Call Rota

Is Your Application Ready for 24/7 Cover?

On-call cover works best when the basics are in place. Before cover starts, we confirm that:

• Monitoring watches availability, errors, resources, failed jobs and backups

• Alerts route to a paging system, not only to email

• A written runbook explains how to restart, roll back and restore the application

• The on-call engineer has tested access to everything needed during an incident

• Backups have been restored successfully at least once

• You have named who on your side can approve business decisions out of hours

If any of these are missing, we set them up during onboarding or through the Go-Live package before cover begins.

Who Needs 24/7 Critical Incident Cover

Apps With Scheduled or Automated Work

Content publishing, email campaigns, data syncs and AI agents that run while your team sleeps.

Businesses With International Customers

If your users are spread across timezones, there is no quiet time to be down.

Apps That Handle Money or Sensitive Data

Downtime or data loss has a direct cost that is far larger than the monthly fee.

Teams Without Their Own On-Call Rota

Small teams rarely have someone who can be woken at night. We provide that cover without hiring.

Choosing Between Business Hours and 24/7 Cover

Business-hours support is usually enough when your application is used mainly by your own team, runs no important jobs overnight and can wait until the next working day without harming customers. Draft-only pilots often start this way.

24/7 critical cover is usually worth it once your application sends emails, publishes content, takes orders or serves customers outside your working hours. A useful test is to ask what one night of downtime would cost your business, in lost revenue, customer trust or recovery work. If that cost is higher than a month of cover, the add-on pays for itself.

You can start without cover and add it in any month, for example when you switch on live sending or publishing after a pilot.

Requirements for 24/7 Cover

• An active Managed Run retainer, so the on-call engineer knows your application

• Monitoring and alerting set up through our onboarding or the Go-Live Package

• A written recovery runbook for your application

• An agreed critical-incident contact on your side for decisions that need business approval

What 24/7 Cover Does Not Include

• Non-critical requests outside business hours, which are handled on the next working day

• New features or changes made out of hours, unless you request them; those are billed at $75 per hour

• Guaranteed fixes for outages caused by your cloud provider, platform vendors or third-party services, although we respond and coordinate

• Support for systems outside the agreed application scope

Cover is reviewed with you each quarter, using the incident history in your monthly reports, so you only keep it while it adds real value.

Pricing

Cover can be added at the start of Managed Run or at any later month, for example when you switch on live publishing or email sending. See all services in Managed App Operations.

Frequently Asked Questions

Sleep Well While Your App Runs

Tell us when your application does its most important work and who depends on it. We will recommend whether 24/7 cover is worth it for you.