How to raise a concern
A concern should include the issue, affected page or service, relevant date, screenshots or supporting evidence where helpful, contact details and the outcome being requested.
Acknowledgement and review
Concerns should be acknowledged and reviewed by an appropriate person. The review should consider the facts, relevant policy, applicable agreement, customer history and evidence available.
Different routes
Privacy, security, billing, contractual, accessibility and technical concerns may need different review routes. A matter connected to a signed agreement should be assessed under that agreement where applicable.
Escalation
If a concern cannot be resolved at first review, it may be escalated internally or referred to the relevant contractual, legal or regulatory process.
Record keeping
A proportionate record may be kept of the concern, investigation, response and outcome for business, legal, security or service improvement purposes.
Expected response information
A useful response may explain what was reviewed, what was found, whether any action will be taken and whether the issue needs another route such as privacy, security, contract management or billing review.
Unreasonable or abusive complaints
Complaints should be raised professionally. Abusive, threatening, discriminatory, repetitive or bad-faith communications may be limited or refused where necessary to protect staff and service operations.
Learning from complaints
Complaints can identify unclear content, poor communication, technical issues, accessibility problems or process gaps. Where appropriate, outcomes should be used to improve policies, website content, training or service workflows.