Skip to content

News

What shipped.

Public product notes, version by version. The same changelog as workspace News — written for the open site.

Releases

RSS
  1. Latestv1.143.4

    Order questions stay in chat, and handoff waits for a clear intent

    Status, change, cancel, and checkout questions no longer get the wholesale team template. Shop chat asks a short follow-up when the intent is unclear, and still hands off when the customer asks for a person.

    Fixed

    • Order status, cancel or change, and checkout are labelled intents with generic examples, so a “where is my order” or “cancel my order” turn is not treated as wholesale.
    • A wholesale or booking team template is used only when that intent leads by a clear score margin. If the lead is thin, the model reply is kept, and a clarifying question is sent instead of handing off.
    • Handoff customer copy follows the final reason. An explicit ask for a person still hands off as a customer request, not wholesale, including Gulf Arabic “I want to talk to a staff member”.

    Open this version

  2. v1.143.3

    Kayan checks shop facts from this turn

    A shop reply is checked against this turn’s knowledge and catalog, even after a long product search. Hedged sentences and Arabic price formats are read correctly, and a failed check can rewrite once.

    Fixed

    • Kayan still sees shop knowledge when a catalog search returns a long product list, so a delivery fee written only in knowledge is not dropped.
    • The checker judges prices, stock, hours, and address only. An English customer with an English reply is not failed for language, and missing extra details are not a failure.
    • A rejected reply can be rewritten once. A checker outage still sends the draft. The reason stays on the turn log.
    • A hedged line such as “I don’t have confirmed delivery information” is not treated as a delivery claim.
    • Arabic-Indic and Gulf prices such as ٥٩.٥٠٠ are read as 59.500, including fils phrasing, and a percent token is not treated as a price.

    Open this version

  3. v1.143.2

    Kayan does not start a run when it is off

    Customer messages on a workspace with Kayan off no longer open a stuck run or hand the thread to the team. Every run ends in a terminal status, and stale running rows close after 15 minutes.

    Fixed

    • When Kayan is off, an inbound customer message does not open a Kayan run and does not hand the thread to the team.
    • A Kayan run always ends as completed, blocked, failed, or superseded. A run still marked running after 15 minutes is closed as abandoned.

    Open this version

  4. v1.143.1

    Messenger inbox replies keep photos and the right label

    Staff image replies on Messenger reach the customer, a human reply is not shown again as Kayan, the footer matches whether Kayan is on, and a closed messaging window is blocked before send.

    Fixed

    • Messenger human replies send attached JPEGs and other shop catalog images, including several in one message, by uploading the file Meta can fetch instead of dropping the photo and keeping only the caption.
    • A staff reply is not duplicated in the thread as a Kayan bubble with rating buttons when Meta echoes the same text back to the app.
    • The inbox reply footer shows Kayan off, a person handling the thread, or Kayan active, matching the workspace setting instead of always saying Kayan is active.
    • Inbox warns and blocks a freeform Messenger or Instagram reply after the 24-hour messaging window. Human Agent send stays off unless that Meta permission is enabled.

    Open this version

  5. 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.

    Open this version