Website Maintenance & Hosting
Host or Developer? Map Who Fixes Which Website Problems
Separate hosting, application, domain and integration responsibilities. Build an escalation map that helps staff reach the right person.
In this guide
The host says the server is online, while the developer says the website cannot connect to a service. Both statements can be true. Support works better when the responsibilities are mapped before an incident.
Divide the system into layers
List domain and DNS, hosting, WordPress, themes/plugins, payment, email and external tools. Record the provider or maintainer responsible for each. “Managed hosting” does not automatically mean every custom application workflow is covered.
Define the first response route
Staff need somewhere to report a symptom without diagnosing it themselves. The initial support contact should know how to collect the URL, time and safe error reference, then involve the appropriate owner. Avoid sending passwords through public help forms.
- Keep verified support contacts accessible.
- Record actual support coverage and exclusions.
- Distinguish response targets from repair estimates.
- Identify who may approve paid or disruptive changes.
- Keep a recovery arrangement for unavailable suppliers.
Use a real-world distinction
A website can return pages while its order emails fail. That may require reviewing the mail integration rather than asking the host to reboot the server. An escalation map helps identify who can access the relevant evidence without promising that every fault has one obvious owner.
Include the map in handover
Review it after changing providers or installing important integrations. Clear boundaries reduce circular conversations and make maintenance scope easier to compare. The useful outcome is an accountable route to investigation, not a vague claim that one subscription covers everything.
Need help putting this into practice?
Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.