Support & operations · Practice guide

Monitor whether visitors can complete an enquiry

Illustrative situation

An uptime monitor reports success whenever the homepage responds, while the enquiry form has been failing since a dependency changed. A homepage availability check may miss a broken enquiry form. Monitor the journey the business relies on, using approved test arrangements that do not create real enquiries or expose personal details. Confirm the check detects the intended failure.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

What this means for your practice

Monitor the important enquiry task using approved checks with fictional activity that does not create real work or expose personal information. Confirm that the check detects the failure it is meant to reveal.

An example to discuss with your team

Break a form dependency in an authorised test environment and confirm the monitor detects the failure while the homepage remains available.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

How to review the arrangement

Ask the supplier to break a form dependency in an authorised test environment while leaving the homepage working. Does the right owner receive a useful alert? Agree how false alarms are reviewed. The practice needs confidence about the important task, not simply evidence that one page responds.

Agree what the check is meant to prove

A check should follow enough of the enquiry task to detect the failure you care about. Opening the form page may not reveal that sending has stopped working. Ask the supplier to explain the chosen approach and its limits in terms of what a visitor can complete.

Use approved fictional inputs and test destinations so automated checks do not create real enquiries or messages. In an authorised test setup, deliberately make the relevant connection unavailable and confirm that the check notices. Then see whether the alert reaches someone who can act and explains which part of the task failed. Agree how false alarms are reviewed, including cases where the monitoring tool itself is blocked or cannot complete a step. The practice needs an understandable signal about the service, with a response route. Adding a monitor without testing that complete arrangement can create reassuring reports that miss the original problem.

How to check the result

Measure detection time for the monitored journey and false-alert frequency.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.