YITH WooCommerce Order Tracking adds four pieces of metadata to each WooCommerce order: ywot_carrier_name, ywot_tracking_code, ywot_pickup_date, and ywot_carrier_url. The admin fills them on the Edit Order screen, the customer sees them on their My Account page. SleekAI can pull those exact fields, plus the order's status, line items, and shipping address from wp_wc_orders or wp_postmeta, into the bot's system message.

That means "where is my order" turns into a one-shot answer. The bot confirms the order number, reads back the carrier name, tracking code, and pickup date, and offers the carrier URL if the customer wants to click through. The Premium version's 480-plus carrier list maps cleanly to a structured carrier slug, so the bot can also explain which carrier handles which country.

Display conditions scope the bot to logged-in shoppers and the My Account area, so guests browsing the catalog never trigger order lookups. Conversation logging captures each ask with model name and token usage, which is useful for stores that want to audit replies, refine presets for repeat questions, or measure how much WISMO load the bot is actually clearing versus what still goes to a human inbox.

Order tracking is the single most common reason customers contact a small WooCommerce store. YITH already solves the data entry side: a default carrier auto-fills, the admin pastes the tracking code on the Edit Order screen, and the customer sees the result on their My Account page. The problem is that customers do not look at the My Account page.

They look at their inbox, panic when they cannot find the email, and write in to ask. Each one of those messages forces the admin to open the order, copy the carrier name and tracking code, and reply, even though every byte of that reply was already in WordPress. A chatbot that reads the same ywot meta fields turns each ask into an instant answer, and the admin only sees the genuinely tricky ones, like a customer who wants the package rerouted or a refund.

Generic chatbots cannot do this. They sit on top of a static knowledge base and have no idea which order ID belongs to which billing email, let alone which carrier YITH assigned. They will either send the customer to the same My Account page they could not find, or invent a tracking number that does not exist.

The honest version that admits the meta is empty only works when the bot can actually read the meta. That is what SleekAI's variable mapping does for YITH, and it is the difference between a deflection number that looks good in a deck and one that actually drops tickets out of the queue.