Advanced Shipment Tracking stores tracking entries in WooCommerce order meta under the _wc_shipment_tracking_items key, each containing a tracking provider slug, tracking number, shipped date, and a generated Track link from AST's 950+ carrier list. SleekAI maps those fields into the chatbot's system message, alongside the order's status, line items, and shipping address from wp_wc_orders (or wp_postmeta on legacy stores).

That turns every "where is my order" question into a one-shot answer. A shopper enters their order number and email, the bot confirms the order, then reads back the carrier, tracking number, shipped date, and a direct link to the carrier site. Partially Shipped orders get split out per tracking entry, so a customer who got two boxes sees both numbers without paging through emails.

Display conditions scope the support bot to the My Account area and order confirmation pages, so visitors browsing the catalog never see internal logistics chatter. Conversation logs capture every WISMO ask with model name and token usage, useful when stores want to feed the most common questions back into saved presets or measure where AI is actually clearing tickets versus where a human still has to step in.

Most WooCommerce support tickets are not edge cases. They are WISMO. A shopper places an order, gets the receipt email, waits two days, then writes in asking where the box is.

The data needed to answer is already in WordPress: AST has the carrier and tracking number on the order, WooCommerce has the status, and the carrier site itself has the live position. Sending that ask to a human means someone copies the order number, opens the edit screen, scrolls to the shipment tracking widget, and pastes the link back into the support thread. It is not hard work, but it is repetitive enough that it eats hours per week on a busy store and arrives at midnight on a quiet one.

A chatbot that reads the same AST fields directly answers the question the moment it is asked, without an inbox in between. The store still hears about the genuine problems, like a misrouted box or a refund request, because those questions do not match the WISMO pattern and fall through to a human. Generic chatbots cannot do this.

They sit on top of static FAQ pages and have no idea what _wc_shipment_tracking_items even is. They will cheerfully invent a tracking number, point shoppers at the wrong carrier, or fall back to please contact support, which is exactly what the customer was trying to avoid. The mapping SleekAI does between the bot's system message and the actual AST entry is what closes that gap.

It is also what makes the bot honest when the order genuinely has not shipped yet, because the variable is empty and the instruction tells the model to admit it.