Tell your form what matters.

Start with the right fields.

Open your project’s Configuration tab and expand Form setup. Set the form name, allowed field names and allowed website origins. A project supports one to four fields and one to eight rules.

Field IDs connect your saved configuration to the actual inputs on your website. Use simple lowercase names such as description or delivery_method. Explicitly map the non-sensitive fields your checks need. Leave passwords, payment details and sensitive personal information out of the mapping.

Allowed origins must be exact, such as https://www.example.com, with no path, trailing slash or wildcard. Add staging separately. To use the app’s Playground, also allow the dashboard’s origin.

Rules evaluate the mapped answers together. For example, “new” as a bicycle’s condition may conflict with a description of a cracked frame. A field target controls where feedback appears, not which answers the rule can consider.

Start with a useful set of questions.

Select Starter packs, choose a pack and review its questions before adding them. The app includes Packaging quote, Support request, Project brief, Product listing and Transport enquiry.

A pack adds editable rules while keeping your current rules, fields and website settings. It does not connect new inputs for you. Check that each question makes sense for the fields you have mapped, remove overlapping rules and stay within the eight-rule limit.

Give each rule one clear job.

Create a rule and write what it should check. The names below match the app’s editor.

For a quality score, the first criterion is score 0. With three criteria, the scale is 0–2; a threshold of 1.5 is allowed. Reordering the criteria changes the scale, so review the threshold afterward. The editor supports dragging and keyboard controls for ordering.

Advanced settings contains the rule type, unique identifier and, for Yes / no and Category match, a confidence threshold from 0.7 to 1. Higher values require more certainty. The configuration names for these rule types are noul, choice and score.

A clear failure shows your visitor message. An uncertain evaluation asks for clarification. A service failure returns unavailable; it does not count as a passed rule. Start with the supplied thresholds and test representative examples before adjusting them.

Sound like a helpful person.

In Suggestion for the visitor, write what someone should add or clarify when the rule does not pass. Messages can contain 3–240 characters. The editor’s preview shows the wording without running an evaluation.

• Ask for a detail the visitor can actually provide.
• Keep quantity, dimensions and material in separate rules so each suggestion matches a specific missing detail.
• Make the wording optional and helpful. Visitors keep control of their answers.

With several mapped fields, choose Show suggestion below to place each rule’s message. The first mapped field is the default. The SDK creates compact feedback directly below the target field; you do not need to add a results container.

Give people time to finish the thought.

Choose the delay under Form setup → Suggestion timing.

Typing restarts the timer. Leaving a field does not bypass the pause or trigger an extra evaluation for an unchanged answer. Feedback starts after an edit; the normal connection does not evaluate untouched fields on page load.

Save the setting, then reload the connected page so the SDK picks up the new delay. New input clears stale feedback, and an old response cannot replace suggestions for a newer answer.

Write suggestions in your visitor’s language.

Choose English or Italian as the default in Form setup. Write each rule’s main visitor message in that language. Open Translations inside each rule to add the other language.

A language becomes available only when every rule has its translation. If the requested language is missing or unsupported, all messages use the project default. Translations are written by you; they do not change the checks or thresholds. Changing the default language uses existing translations as the main messages. Fill any empty suggestions before saving.

The widget’s Auto setting follows the form document’s <html lang>, including changes made by a language switcher. You can also choose an explicit locale. Switching existing feedback does not run another evaluation. See the SDK language guide for examples and embedded-form behavior.

Install once. Adjust in FormLint.

Save your configuration, then use Playground to test incomplete, complete and ambiguous examples through the live service. Test feedback placement and languages as well as the content of each suggestion. Open the Playground guide.

Subsequent evaluations use your saved rules and messages. If you rename a field, change a form or move to a new site origin, update the integration mapping and project configuration together. Reload the form after changing timing or connection settings.