Questions to ask about website support

Open your website support proposal and find the instructions for reporting a problem. Can you tell where to send it, when someone will read it and what happens after the first reply? Write down the missing answers before comparing the monthly price with another provider's offer.

A useful support discussion starts with the website you actually run. Make a short list of the work you expect to request and the systems a customer relies on, including any booking or payment service reached through the site.

Ask what the quoted time measures

Ask the provider to explain its response target in ordinary language. Does it mean an automatic receipt, a person reviewing the request, or someone beginning an investigation? Ask separately how progress updates and estimates for completing the work are handled.

AWS's account-and-billing support example explicitly says its response times cover the first response and do not apply to subsequent replies. That is a description of AWS's service, not a benchmark for a small website provider. It illustrates why the word “response” needs a definition in your own support arrangement.

Confirm the working hours, time zone and holiday coverage. If you report a broken page outside those hours, ask when it enters the queue and how to reach someone if the issue meets the provider's urgent-support criteria. Have the provider describe those criteria using the customer task that is affected.

Walk through work you expect to request

Bring actual requests you anticipate, such as changing opening hours or adding a service page. For each, ask whether it is included, how the work is estimated and who approves any extra cost. Check whether a monthly allowance expires or carries forward and whether investigation time counts toward it.

Then discuss a failure in a customer journey. Choose a route on your site and identify where it leaves your domain. Ask who investigates if the external booking or payment service fails, who contacts that supplier and who keeps you informed. Record which parts your website provider can change and which depend on another company.

Do the same for routine maintenance. Ask which updates and checks the plan includes, how often they happen and what record you receive. If backups are included, ask what they cover and who handles a restoration request. Keep any detailed recovery plan in the operational handover rather than expecting the support description to explain the entire procedure.

Agree how a request moves through the queue

Ask for the request channel and the information the provider needs to start work. A practical report can include the page address, the action attempted, the result and when it happened. Use the provider's secure route for any sensitive details; a screenshot should not expose customer records or credentials.

Name the person in your business who can approve changes, and agree who covers their absence. Ask how the provider records pending questions, estimated costs and approval. For a finished change, decide who checks the relevant customer task on the live website and how completion is recorded.

GOV.UK's support-planning guidance considers enquiry types, handling time, staffing and measurement. For your provider discussion, ask how the proposed coverage fits the requests you expect to send. Keep the answer specific to your website and the support plan being offered.

Keep the answers with the plan

Put the agreed scope, request route, working hours and approval contacts alongside the proposal. Ask the provider to resolve any difference between these answers and the written plan before you accept it. Record who owns the hosting and other accounts needed for support, and how access is removed when the arrangement ends.

After the first completed request, compare the record with what was agreed: when it was acknowledged, what needed approval and how completion was checked. Use that request to identify an unclear responsibility or missing update, and agree the correction with the provider.