Website support services answer a question that tends to surface right after launch. Who do you contact when the booking form stops working or your holiday hours still say you’re open?
Ask for a named first point of contact and written coverage for the website tasks you expect. “We do support” is easy to say when the site is behaving itself.
Know who gets the first call
Start with three common situations. A new staff photo goes to whoever handles content edits. A page that won’t load needs someone who can tell whether the problem is with the host, WordPress, or the page itself. A booking tool that stopped taking appointments may need help from the tool vendor, too.
One company can handle several roles. What matters is who takes responsibility for the first check and who follows up if a second provider needs to get involved.
- Hosting keeps the website’s server running. Ask who handles outages and what the host’s backups cover.
- Maintenance covers scheduled work such as software updates, backups, and routine checks. Confirm what’s included in your plan and who tests the site afterward.
- Website support covers the edits and fixes your agreement names. Ask how the provider handles issues that turn into larger projects.

Get a concrete definition of “included”
Use requests you can picture actually sending. Can I change our Saturday hours? Replace six product photos? Add a service page? Get help when our quote form sends to the wrong person?
Ask whether updates come with a monthly allowance, what counts against it, and how the team prices work outside the plan. A small text edit and a new service page may pass through the same help desk with very different price tags.
For technical coverage, ask who runs updates, how often backups happen, how long they’re kept, and who can restore the site. WordPress explains that a complete backup covers both the site files and its database. If you take orders or bookings online, ask how a restore would affect anything submitted after the backup was taken.
Ask how urgent requests move
Get the support hours, the usual response time, and the procedure for an outage outside those hours. Ask when you can expect an acknowledgment and how the team will keep you informed if the fix takes longer. An estimate for the first reply and an estimate for the repair answer different questions.
Use a clear subject line and include the page link, what you were trying to do, what you saw, and when it started. For content edits, include the approved wording or image and the date it needs to go live. One complete request usually beats six follow-up emails with “one more thing” in the subject.

Keep access and ownership straight
Record who owns the domain, hosting account, WordPress site, and any booking or payment tool the site relies on. Keep a current business contact on each account so renewals and service notices reach the right person.
Use separate accounts and give people the access they need for their work. WordPress’ role settings let you give a content editor and a site administrator different permissions. Ask the provider who removes access when a staff member or vendor leaves.
Write down the plan before launch
Keep the support contact, business hours, coverage, urgent issue process, and backup responsibilities in one place your team can find. If you’re still planning the site, include it with the launch checklist and agree who owns the handoff.
Gravity Junction offers website support to its hosting clients. See our hosting and care plans for the hosting side, or visit Gravity Junction’s website support page to see how to request help.




