Skip to content
All news
v1.143.0

Kayan quotes from what it saw, and can send photos, orders, and limits

Shop chat checks answers against the catalog and knowledge it retrieved this turn. It can send that product’s photos, create or look up the customer’s order, and negotiate only inside shop limits. Unclear questions get a short follow-up.

Improved

  • Prices and specs in a reply must match the product rows, knowledge, and tool results the model actually saw. A currency amount is a live-price conflict only against that product’s live price. Phone numbers, links, maps, distances, and the required shop footer are not treated as catalog claims. Visit invitations the knowledge requires are kept. If the checker itself fails, the turn hands off instead of sending the draft. Internal product ids stay out of customer text. Retrieval keeps the top vector matches instead of a hard 0.35 cut and no longer fills most slots with pinned articles. Product search uses the product-name span of the question and pgvector, not a SQL keyword scan. Provider retries spread out, with an optional fallback key or model from config. Asking for a person in English, Gulf Arabic, or Egyptian Arabic hands off.
  • On storefront web, Messenger, Instagram, and WhatsApp, Kayan can create one confirmed order from live catalog prices, look up that customer’s orders, and cancel or update delivery details only. It can send publicly fetchable catalog photos of the product being discussed, with matching caption, and it respects takeover and send-lock. Price negotiation is off until the shop enables a max discount or min price. Ambiguous matches or missing size, quantity, or checkout details get one short follow-up instead of a guess.