Quick answer
Agree support roles before a website incident by building a supplier contact tree. For each supplier, such as the host, developer, domain and email provider, record what it is responsible for, the primary contact, the escalation route and who updates customers. Ask each supplier to confirm its line, and test the details.
- If responsibility is unclear, ask each supplier in writing instead of assuming where its boundary lies.
- Make sure more than one person at your business holds the contact details, rather than one person’s head.
- Decide who talks to customers and approves the message; supplier updates are inputs, and your business owns the message.
When a website incident crosses the host, the developer and the email provider, nobody knows who to call first. A contact tree names each supplier’s responsibility, primary contact and escalation route before the incident happens. This is for owners and operations managers.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. A website incident crosses the boundaries of the host, developer and email provider.
What happens. The owner lists each supplier, what it is responsible for and who updates customers, then tests the contact details.
Responsibility boundaries
List every supplier involved in the website and what each is responsible for: hosting, code, domain, email. Use the supplier and responsibility fields. If responsibility is unclear, ask each supplier in writing instead of assuming.
Escalation paths
Record the primary contact and an escalation route for each, including out-of-hours options if the contract offers any. Use the primary contact and escalation route fields. Check the details are current and that more than one person at your business holds them.
Communication ownership
Decide who talks to customers, and who approves what is said. Use the customer update owner field. Supplier updates are inputs; your business owns the message.
Supplier incident contact tree
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| Supplier | Responsibility | Primary contact | Escalation route | Customer update owner |
|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Supplier | Responsibility | Primary contact | Escalation route | Customer update owner |
|---|---|---|---|---|
| Hosting provider | Server availability and backups (per contract) | Support line named in contract | Provider escalation contact | Operations manager |
Working through the completed row
The row covers the hosting provider’s responsibility for server availability and backups per contract, a named support line, a provider escalation contact and the operations manager as customer-update owner.
Common mistakes
- Assuming a supplier knows its boundary.
- Keeping contacts in one person’s head.
- Not deciding who tells customers.
Questions to settle before you rely on it
- Which suppliers touch the site?
- Who contacts each, and in what order?
- Who tells customers?
How you know it is complete
The tree is complete when each supplier has a responsibility, contact, escalation route and update owner. Record who reviewed it and the date.
Where you may not have the answer
Two suppliers each say the fault lies with the other. Keep a record of what each said and escalate to the person who holds both contracts. The handoff, not a guess, is the correct next step.
Your next action
Draft the tree for your site and ask each supplier to confirm their line.
Ask Web Design Davao to review this workflow and scope the website or marketing support required. Secure web hosting arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Domains and hosting can be held in the client’s name or managed by Web Design Davao, depending on the client’s requirements. Either way, record who holds each login and who can recover it.
- Preventative website maintenance includes keeping plugins up to date and reviewing website code for known vulnerabilities. This reduces exposure to attack; it does not guarantee a site cannot be compromised. See website updates and uptime monitoring.
Frequently asked questions
Do I need a formal agreement?
A written understanding of roles helps even where contracts are separate.
Who should be accountable?
A named person in the business.
What if providers disagree about the cause?
Collect evidence and keep one coordinator.
How often should I review the plan?
At least yearly and whenever providers change.