You email your website provider to change a clinic time. A friendly reply arrives quickly. But when you check the website later, the old time is still there. Your request has been answered. Your problem has not.
That is the distinction worth looking at when you choose GP website provider support: how a request becomes a completed update. A prompt reply matters, but the useful result is accurate information on your website. Here is what to ask, how our own team works, and a simple way to test the service before you commit.
A quick reply is only the first step
A change request can take several routes. The person reading your email might edit the website themselves, or they might pass it to a colleague. More technical work may need a developer. None of those arrangements is automatically wrong. What matters is whether someone owns your request and keeps you informed until it is finished.
- Response time: how long you wait for a reply.
- Completion time: how long you wait for the requested change to appear on your website.
Providers may use “resolution time” for the second measure, but check what they mean. Closing a support ticket is not necessarily the same as confirming that an update is live and correct. Ask what happens between the first reply and the finished change, and how you will know the work is done.
How our support team handles website updates
At Tree View Designs, our support team includes the people who edit practice websites. For a routine content update, the person who reads your email will usually make the change themselves. You can send the information you need updated without turning a small task into a website project.
The team is led by Adrian Terry. Requests are recorded so there is a history to refer back to, and work that needs code changes goes to a developer. The aim is straightforward: a clear route from your request to the person who can act on it.
Our HubSpot records show 14,356 tickets created between 18 August 2025 and 17 August 2026. Of those, 11,842 were classified as site updates — around 82.5%. These figures cover tickets across our pipelines, not just the support queue. They describe requests relating to website updates, rather than a count of completed changes or a promise about turnaround times.
That volume helps explain why everyday content changes deserve attention when you compare providers. A new website is one part of the relationship. Keeping it useful after launch is the ongoing work.
There is a package distinction too. Routine content updates are included with our Premium package; Basic covers hosting, security and technical support. Our desk operates during UK business hours. Check what each package includes so you are comparing the service your practice actually needs.
Small changes matter to patients
An old clinic time, a broken prescription link or unclear appointment instructions can send a patient down the wrong path. Even when the website is technically working, its information can still need attention.
In the 2026 GP Patient Survey, 30.8% of patients said their last contact with their practice was online or through the NHS App. That includes more than website use alone, but it shows why clear, current digital information matters to everyday access.
For practices in England, website information also forms part of contractual requirements. We cover the detail in our guide to what the GP contract requires of your website. For choosing support, the practical point is simple: establish who keeps information current and how you request an update when something changes.
Try one small change before you decide
A practical example can make a support conversation much more useful. Choose an ordinary task: changing a clinic time, updating a staff name or replacing a line of text. It should be the kind of request your team would genuinely send, with the wording and page clearly identified.
- With your current provider: send a real update through the usual support channel. Note when you send it, when you hear back and when the change appears.
- With a prospective provider: ask them to demonstrate the same process on a demo website. Ask whether the demonstration reflects their normal service and what turnaround you should expect.
- Check the result: is the wording correct, does it read properly on a phone, and did someone confirm completion? If clarification was needed, was it easy to provide?
One example cannot prove how every request will be handled, but it gives you something concrete to discuss. Ask how urgent corrections are prioritised, what happens outside support hours, and which work needs a separate quote. Clear answers are more useful than an impressive response-time headline.
Choose support that fits your practice
Some practices prefer to make small edits themselves. Others want to email a request and have someone take care of it. Both can work. Think about who has the time, confidence and responsibility to keep your website up to date, including when your usual website contact is away.
If you want managed updates, look for clear ownership, an understandable process and confirmation that the work is complete. Our support page explains how to contact our team. If you are comparing providers, our guide to choosing a GP website provider covers the wider questions.
Not sure what needs attention on your current website? Our free website audit checks it against NHS England's benchmarking tool and WCAG 2.2 AA, with findings you can use to decide what to tackle next.
