Corthex · Custom products / guided choice
Help someone choose. Keep the product facts exact.
With dimensions, variants and a configurator, a helpful next question matters more than a quick recommendation. Know what is measured, available and authorized.
Original conceptual materials study · no product availability or compatibility claim
01 / Clarify
A number needs a meaning.
“I need a door that is 820 millimetres wide” sounds precise, but the measurement might describe an opening, an existing door leaf or a desired finished dimension. Those are not interchangeable. Before recommending a product, the assistant should establish which measurement the visitor means and which approved specification explains the relationship. It should not invent an installation allowance or turn an uncertain number into a final order size.
Ask a short question that moves the choice forward: which model, which application or what exactly was measured? Keep the answer in the visitor’s language and connect it to the available source. When the product needs specialist confirmation, say what must be checked and who can do it. A deliberate pause for a product expert is better evidence of a bounded service than an unsupported claim that everything will fit.
02 / Verify
An option is not a valid combination.
A store may sell a blue finish and a wide frame without offering that finish for that exact frame. Advice needs product-level compatibility, not a list of attractive attributes assembled from different pages. Use current connected product information where the relevant tool supports it, and approved technical knowledge for the explanation. If the tool does not expose the required constraint, treat it as unknown rather than filling the gap with a plausible combination.
Keep product references consistent as the conversation continues. When the visitor changes a model or measurement, re-check dependent options, price and availability. Do not carry approval for an earlier proposal into a different configuration. A source citation can explain a material property; it cannot by itself prove the current stock or exact configuration price for this visitor’s selection.
03 / Propose, then authorize
A website action is a separate step.
First explain the proposed choice. Then establish whether the host website actually offers the action needed for the current session. A button described in a knowledge article is not an executable action. Corthex’s custom website integration can work with explicitly exposed host actions, but it does not give a generic embed arbitrary control over a configurator. The action must exist, be available and use the intended inputs.
For a change with consequences, obtain specific visitor consent and report the actual result. A cancelled or unavailable action should leave the visitor with an honest explanation, not a success message. Checkout and payment are outside the advisory role described here. Your own installation acceptance test should verify exactly one intended example change and the refusal or cancellation path, using a controlled test environment.
Follow a choice before you connect a store.
This local example illustrates missing dimensions, unsupported combinations and consent. It is not the Corthex product UI or a real catalog.
Fictional product scenario
Example catalog: 820 mm leaf, ivory finish. Other choices require verification; these are not real store options.
Clarify what the measurement refers to. Do not convert an opening size into a product size without the approved specification.
Local simulation only; no store is connected.
Different businesses, different roles
Use customer stories to understand the setup, not to invent an outcome.
MartijnKozijn
Robby’s published story describes product explanation and guidance from the company’s knowledge, with a route to a person. It does not establish WooCommerce use or show an independent cart or checkout action. Read the implementation and the stated measurement limits in context.
Read the story →Deurwebshop
Jan’s story explains a configuration-oriented advisory role and the boundaries of available website actions. Use it as a practical setup account. Usage figures are not published here, and the configuration is not evidence of a conversion increase or completed transaction.
Read the story →Ask a product expert to review the failures.
Build a short review set with an unclear measurement, an unavailable finish, a changed model, an unexposed website action and a cancelled proposal. Write down the correct next question and the source or tool needed for each case. Include a clean example that should succeed, but do not let it replace the difficult questions. The person who owns the product specification should review technical correctness before the assistant is exposed to customers.
Start with one product family and a clearly bounded action. Expand only when your sources, option rules and review process can keep up. The useful measure is whether the visitor receives a correct, understandable next step under those conditions. Do not turn a number of conversations into a claim of sales, savings or perfectly fitted products.
For a custom-built store, review the custom storefront connection requirements before choosing the action you want the assistant to support.