Yes. Motor compatibility is read from a custom field on each kit, usually a list of impulse codes like A8-3, B6-4, C6-5 for low power and E, F, G for mid power kits. The bot joins this with the motors in stock and returns the combinations that exist in your catalog right now. There is no invented motor code and no pairing the manufacturer does not recommend.

Yes. State by state rules live in an OpenAI Files vector store, and the bot quotes the rule that applies to the shopper based on the address they provide. California, New York, and Massachusetts each have different surcharge and signature rules, and the bot reflects those rather than giving a single generic shipping line that gets overridden at checkout.

Yes. For motor classes H and up the bot checks the logged in customer role for NAR or Tripoli certification level meta. If the customer is not certified or not logged in, the bot explains the certification path before suggesting motors, rather than letting an uncertified flyer add a motor they cannot legally use. This is configurable per shop.

Yes. Each kit carries a skill level attribute in WooCommerce, usually 1 through 5, and the bot reads that on every request. A first time builder gets level 1 ready to fly options first. A repeat customer with a build history of level 3 kits gets pointed to level 4 next steps with a note on what makes the jump harder, usually fin alignment and stronger glues.

Accessories are read from the same WooCommerce catalog with category tags like launch_pad, igniter, recovery, and altimeter. When a shopper finishes a kit conversation the bot can surface the matching launch pad rated for the rocket weight and the right igniter pack. The catalog stays the source of truth, so accessories that are out of stock are not suggested.

Conversation logs stay inside your WordPress database. The data path is browser to WordPress to your OpenAI or Anthropic key directly, no Sleek server in between. For shops that also export customer purchase history for community manufacturer rebate programs, the chat logs are easy to include or exclude from those exports because they sit in a regular WordPress table you control.

Yes. The bot pulls from your published safety content and the NAR safety code via an OpenAI Files vector store. A first time builder asking how far to set up the launch pad, what wind speed is too high, or what kind of field to use gets concrete answers grounded in NAR guidance, with a note to confirm with the local club for any club-specific rules.

Generic chatbots are tuned for support tickets and FAQ pages. They have no link to your WooCommerce catalog or to the motor compatibility custom fields you maintain. SleekAI runs inside WordPress, reads the same tables WooCommerce reads, and runs on your own AI provider key. The result is a shop assistant that talks like a knowledgeable rocketeer rather than a polite FAQ that punts every hard question to a contact form.