How to send feedback on a help article
The "Was this article helpful?" form under every help page. What happens to it, what is worth writing in it, and when it is not the right channel.
Every help centre page ends with the question Was this article helpful? and two buttons. This is not a marketing survey — it is the shortest route to telling us that the description does not match what you see on screen.
How to do it
Find the form
It is at the bottom of every help page: feature descriptions, guides, compliance documents and problem descriptions. You do not have to be signed in — it works on the public pages too.
Choose Yes, it helped or Not quite
Two buttons: Yes, it helped and Not quite. The click alone is already a signal — you do not have to write anything. After Yes, it helped you will see Thanks — glad it helped. and that is the end of it.
After Not quite, add what was missing
A field appears with the hint What was missing? (optional, max 500 characters) and the buttons Send and Skip. The rating is saved the moment you click, so even after Skip the signal reaches us.
Three things are the most helpful, in this order:
- What you were trying to do — one sentence.
- Where the article parted company with the screen — for example "step 3 talks about a button I do not have". That tells us the documentation is not keeping up with the application.
- What was missing — the question you arrived with and did not find an answer to.
Do not put data in there
The field holds 500 characters and goes into a shared collection of documentation feedback. Do not enter passwords, codes from messages, or patient data. If the matter needs a specific record named, that means it is not a documentation matter — see the next section.
What happens to it
We record: the page address, the rating, the comment text, the language and the moment it was sent. Alongside them we record a digest of the network address and a browser marker — needed to spot abuse. The digest is computed separately for each day, so it cannot be turned back into an address or used to tie feedback from different days together.
The form does not collect an e-mail address and there is no way to reply to it. If you expect an answer, file a report rather than feedback.
When this is not the right channel
- The app is down and you cannot work — the Give feedback button in the panel, or
support@heltio.pl. - A suspected personal data breach — never through this form. There is a separate procedure.
- A specific symptom in the app — first check whether there is already a description in troubleshooting.
- An idea for a new feature — the Give feedback form in the panel, type Feature request.
When something does not work
You've sent a lot of feedback already — try again later or use the contact form.
What this means: One connection can send a limited amount of feedback per hour. A safeguard against flooding the form.
Something went wrong. Please try again in a moment.
What this means: Saving the feedback failed.
Clicking Yes is worth it too
A positive rating is just as useful as a negative one: it tells us what not to touch when the text is next rebuilt. One click is enough.
Related
- How to report a problem and what to attach — when the matter concerns the app, not the text.
- Reporting bugs and feedback — the form in the Heltio panel.