what happens if I click no on an answer that the system suggests

Clicking no removes the answer from the submitted overview

If you click no, the suggested answer disappears from the set going to your customer's portal. Nothing else happens automatically: the system does not make any changes to the chain file, and no alternative is filled in. You then decide yourself how to proceed: leave the field empty, manually type a different answer, or update the file first so that the suggestion is correct the next time.

Clicking no is therefore not a correction of the file, but a correction of this one answer in this one list. If the no is due to an incorrectly linked source — for example because the establishment address of the company is outdated, or because the number of employees is no longer current — then you update that source data in the file itself. After that, the suggestion will be correct at the next questionnaire, without you having to figure it out again yourself. If the no is due to the question, not the answer — for example a question that asks something slightly different than what the file contains — then it remains your entry, per list, per time.

Why this is at your submission, not with us

This follows from the division of roles that recurs on every page of Supplia: the system recognizes questions and suggests answers from one chain file, but the confirmation per answer — yes or no — lies with the entrepreneur, and the submission to your customer's portal is done by the entrepreneur himself. Supplia does not log in to a third party's portal and does not assess any answer substantively. A no-click is therefore a choice in your workflow, not an action that has consequences elsewhere. For sensitive fields, such as something related to ISO 9001 certification or an ongoing insurance file, the same route applies: click no, and decide yourself what goes to your customer instead.