Website technical support

Typical support requests

Support and maintenance work together

Maintenance is proactive: updates, backups and checks carried out on a schedule to prevent problems. Support is reactive: help when something happens or a question arises. A well-maintained site needs less support, and good support records reveal what maintenance should focus on. Many businesses combine both in one arrangement, but it helps to understand the difference when comparing offers.

Without maintenance, support tends to become a series of emergencies.

Asking for help effectively

Urgent and non-urgent

• Urgent

  Site down, checkout failing, forms not delivering, security concern.

• Important

  Feature broken for some users, error on a key page.

• Routine

  Questions, small changes, cosmetic issues.

How a support request is handled

1. 01

   Request

   Issue reported through the agreed channel.

   Output: Logged request

2. 02

   Triage

   Urgency assessed and acknowledged.

   Output: Priority set

3. 03

   Resolve

   Fix, answer or plan agreed.

   Output: Resolution

4. 04

   Close

   Outcome explained and recorded.

   Output: Support history

Agree expectations in writing

Response times matter most when something is urgent. Rather than assuming, agree in writing how requests are made, when they are acknowledged, what counts as urgent and whether help is available outside working hours. Realistic, written expectations are more useful than vague promises of fast help.

Support that teaches

Good support does not only fix things; it helps your team avoid the same problem next time. When the answer to a request is something you could do yourselves, such as resizing an image before upload or resetting a user's password, a short explanation or screen recording builds confidence and reduces future requests. Over time, support should shift from routine questions to genuinely technical issues.

Ask whether your provider is happy to explain as well as do.

When the problem is somewhere else

Website problems are not always caused by the website. Hosting outages, email provider issues, payment gateway faults, expired domains and browser updates can all appear as 'the website is broken'. A support provider who can identify where a problem really lies, and help you raise it with the right company, saves time and frustration even when they cannot fix it directly.

The value of a support log

A record of requests, causes and fixes builds into a useful history. It helps diagnose recurring problems, shows where the site needs investment and gives a new provider context if you ever change. Keep it somewhere you can access, not only in the provider's system.

Keeping contacts current

Make sure the people who might need support know how to request it, and that the provider knows who can approve work. A short contact sheet, updated when staff change, avoids delays in an urgent situation.

Security concerns

If you suspect the site has been compromised, for example strange pages appearing, unexpected redirects or warnings from browsers or your host, treat it as urgent. Change passwords, tell your support provider immediately and avoid deleting evidence that could help identify what happened. A support arrangement should state how security incidents are handled.

Choosing an arrangement

Businesses that rarely need help may prefer to pay per request; those with regular questions or a busy shop often prefer a monthly arrangement with agreed priorities. Combining support with maintenance usually gives the best value, because prevention and response are handled by the same people who know the site.