How to use the Product Cross Sell Recommender.
Cross-sells should complement the actual product and customer task. A matching name is not proof that an accessory fits.
Make the workflow fit your task.
Identify the main product's requirements and the customer's next likely need. Compare candidate accessories against those specifications, recommending a match only where the supplied evidence supports it.
- What you provide
- Supplied catalog and use-case relationships.
- What you get
- Relevant complementary-product suggestions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Lamp L1 requires an E27 bulb and permits up to 8 W. Bulb B1: E27, 6 W. Bulb B2: E14, 6 W. Compare only the supplied fitting and wattage requirements.
Completed example
B1: matches the E27 fitting and is within the supplied 8 W maximum. B2: fitting mismatch; E14 does not meet the supplied E27 requirement. Candidate: B1 on the two stated checks. Other compatibility requirements, if any, have not been supplied or verified.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can a matching product name prove accessory compatibility?
No. Check the required connector, size, model or other relevant specification. Names can be similar across incompatible variants.
Why is a cross-sell useful in theory but wrong for this item?
Recheck the exact variant and included components. The customer may already have the accessory or need a different specification.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑