Ask only what changes the recommendation

Begin with the intended use, then ask about genuine constraints. Avoid asking shoppers for technical measurements they are unlikely to know. Explain unfamiliar choices in everyday language and allow uncertainty where appropriate.

Keep recommendations explainable

For each result, identify which source-backed attributes support it. A confidence or match indicator is not a certification and should not replace necessary product checks. Do not present an unsupported accessory or compatibility claim as a fact.

Prepare test cases

Write scenarios for a typical shopper, a niche requirement, conflicting preferences, and no suitable product. A good flow should be able to say that the catalogue has no confirmed match. Use these cases when the module is available to your workspace.

A note on availability

Dashboard labels may currently be in German. Available controls and modules depend on your package and release. If a control described here is missing, check your workspace or contact support.