Yes. Battery compatibility lives in a custom field on each battery SKU and on each car kit, typically a list of model names like Slash 4x4, Granite 4x4, Senton 4x4. The bot joins the two lists on every request and returns batteries that fit the car the shopper is asking about, with the c-rating, connector type, and current stock. There is no invented spec and no wrong connector recommendation.

Yes. Spare parts carry OEM part numbers and a list of compatible kits in WooCommerce custom fields. A Granite 4x4 owner asking for a rear driveshaft gets the AR310487 set with current stock and a backorder ETA if the part is out. The bot does not guess the part number or suggest a part for a different model, because the data path forces it to read the actual compatibility list.

Yes. LiPo air shipping rules sit in an OpenAI Files vector store and the bot quotes the rule that applies to the shopper's country. Watt-hour limits per pack, total cell count per package, and the express courier exceptions are all covered. The shopper gets a real shippable or not answer with the relevant detail rather than a hedged maybe at the bottom of the shipping page.

Yes. Drone categories are separated in WooCommerce by category and tag, and the bot reads those on every request. A question about props for a 5 inch quad gets HQProp and Gemfan suggestions in the FPV freestyle range. A question about a toy quad for an 8 year old gets a different category entirely with a built in camera and brushed motors.

Yes. ESC and motor pairings live in custom fields per SKU. The bot reads the current amp rating of the ESC, the upgraded motor's stall current and continuous draw, and recommends an ESC that has headroom rather than running at the limit. For Spektrum Smart ESCs the bot also notes the firmware version that supports the upgrade.

Conversation logs stay inside your WordPress database. The data path is browser to WordPress to your OpenAI or Anthropic key directly, with no Sleek server in between. For shops that share data with manufacturers for warranty or rebate programs, the chat logs are stored in standard WordPress tables you can export or exclude as needed.

Yes. Warranty terms per brand and the refurb program rules sit in an OpenAI Files vector store. A shopper asking how to file a warranty claim on a Traxxas servo gets the Traxxas process; a Spektrum receiver question gets the Spektrum process. The bot quotes the relevant paragraph and collects the basic order details so a support agent can pick up if escalation is needed.

Generic chatbots run on a vendor server and read your help center, not your WooCommerce catalog or your compatibility custom fields. They cannot answer battery or spare part compatibility questions accurately because they have no link to wp_postmeta. SleekAI runs inside WordPress, reads the same data WooCommerce reads, and runs on your own AI provider key. For an RC store that is a structural advantage rather than a feature toggle.