SSL outage 2:17 a.m.: e-commerce down. 24/7 chat: we open a ticket, 4–8 h delay. Infra on-call: €49/mo option not subscribed. Lost revenue ~€12,000.
24/7 support separates reception, diagnosis, and infra action.
At 3 a.m., only whoever can reboot your VM counts.
Levels of 24/7
Ticket reception; extended business hours; paid infra on-call; premium managed with credits.
| Promise | Reality | Proof |
|---|---|---|
| 24/7 chat | Script + ticket | Night test |
| Phone | Redirect | Test number |
Inquiry protocol
After-hours ticket on staging. Support matrix per plan. Cross SLA exclusions and status page.
On-call budget
If critical: paid option or managed. Directory francophone support.
The peak: outsource insomnia
Align contract with survivable outage
At 3 a.m. the question is not your phone number but who can act on hypervisor or firewall. If answer is nobody without enterprise option, runbook must assume alone until morning. Many teams discover gap after first SSL or disk saturation outage.
Ask in writing support matrix per plan: night team timezone, languages, engineering escalation delay, service credits if missed. Cross status page and SLA exclusions.
Go further with the inquiry
Apply the article to your concrete case: what volume, what service level, what contractual constraints from clients or regulators? Write answers before opening the pricing page. Request written documents — full grid, DPA, certification scope, renewal terms — not homepage screenshots.
Compare at least two providers via the directory and compare tool on identical thirty-six-month assumptions. Share the short list with whoever signs the contract and whoever operates infrastructure daily. Archive terms dated at subscription so due diligence is defensible later.
Go further with the inquiry
Apply the article to your concrete case: what volume, what service level, what contractual constraints from clients or regulators? Write answers before opening the pricing page. Request written documents — full grid, DPA, certification scope, renewal terms — not homepage screenshots.
Compare at least two providers via the directory and compare tool on identical thirty-six-month assumptions. Share the short list with whoever signs the contract and whoever operates infrastructure daily. Archive terms dated at subscription so due diligence is defensible later.
Align contract with survivable outage
At 3 a.m. the question is not your phone number but who can act on hypervisor or firewall. If answer is nobody without enterprise option, runbook must assume alone until morning. Many teams discover gap after first SSL or disk saturation outage.
Ask in writing support matrix per plan: night team timezone, languages, engineering escalation delay, service credits if missed. Cross status page and SLA exclusions.
Align contract with survivable outage
At 3 a.m. the question is not your phone number but who can act on hypervisor or firewall. If answer is nobody without enterprise option, runbook must assume alone until morning. Many teams discover gap after first SSL or disk saturation outage.
Ask in writing support matrix per plan: night team timezone, languages, engineering escalation delay, service credits if missed. Cross status page and SLA exclusions.
Decide and move forward without blind spots
Start by framing your real scenario on one page: volumes, client constraints, required support level, and a thirty-six-month budget including domain, backup, and essential add-ons. Compare at least two hosts via the directory and compare tool with identical assumptions, archive pricing grids dated on subscription day, then have both the contract signer and daily infrastructure operator validate the short list.
Frequently asked questions
24/7 = on-call?
Often ticket/chat only; L3 on enterprise.
Test before signing?
Night ticket + measure first useful response.
Phone vs ticket?
Phone rare; check scope and language.
Ask sales?
Who is L3 at night, escalation delay, languages, SLA credits.
At 3 a.m., support is measured by first infra action.