Yes. If your skis publish length, waist width, and recommended ability range, the bot reads them from postmeta and can match a customer's height, weight, and ability to in-stock options. For shops that maintain an in-house length chart (often based on cm under or over height by ability), the bot quotes the chart faithfully. A 178cm intermediate looking for an all-mountain ski gets a length range and two or three in-stock candidates in one reply.

If your skis tag mounting system (flat, system, integrated track) and bindings tag their compatible mount types, the bot can confirm pairs that work and flag ones that do not. A customer asking whether a Marker Griffon will fit a flat-mount ski gets a yes/no answer plus mounting cost if mounting is a separate service. For tech-insert touring bindings, the bot can confirm whether a backcountry ski has the inserts and whether boots in the cart have the matching tech fittings.

The bot quotes boot fitter availability, demo program terms, and rental rates from your published content. It does not write to your calendar directly, but it explains the booking flow: "boot fitting appointments are 90 minutes, booked online at this URL, free with boot purchase." Logs from these conversations are useful for spotting calendar friction ("can I book a same-day appointment" recurring often is a sign the booking UX needs help).

Yes, if those prices are on your services page. The bot can answer "how much is a hot wax" (e.g., 25 EUR) or "what does a base grind cost" (e.g., 55 EUR with edge tune) from the published list. For complex repairs (delaminations, p-tex repairs), the bot describes the process and routes the customer to drop off in-store rather than promising specific repair pricing without seeing the ski.

If your rentals are managed through WooCommerce Bookings or a similar plugin, the bot can read availability for the dates the customer requests. "Are All-Mountain Rentals available for Dec 26 to 30" gets a yes/no with the rate. For shops that do not have rentals on the WooCommerce side (POS-only), the bot quotes the rental rate sheet but advises the customer to call or walk in to reserve.

Yes. If your catalog tags skis by use case (resort all-mountain, freeride, touring, race), the bot scopes recommendations accordingly. A customer asking about backcountry skis gets touring options with tech-insert binding compatibility, weight per ski, and skin-cut availability. Multibot lets you run a separate touring-focused bot on the backcountry category that defaults to weight-conscious recommendations and reminds customers about avalanche education resources.

In your WordPress database. Each message is logged with model name, token usage, and page URL. Nothing routes through Sleek infrastructure: the data path is browser to WordPress to your model provider on your API key. For shops with EU customers, this keeps the data-residency story simple, and customer conversations never appear in a third-party vendor's dataset.

Multibot lets you run several bots with different prompts and display rules. A resort all-mountain bot can focus on length, waist width, and binding ease of use; a backcountry bot can focus on weight, tech inserts, skin compatibility, and avalanche education resources. Display conditions scope each bot to the right category so the right specialist appears at the right moment in the shopper's session.