Not by default. The WooCommerce Square plugin and most Square WordPress integrations already mirror catalog, inventory, and order data into postmeta. SleekAI reads that. For data not mirrored, a small server-side hook can fetch from Square on demand, but the typical pattern is read-only against the WordPress-side mirror to keep replies fast and predictable.

No. SleekAI is read-only against Square by default. Captures, refunds, and rebooking happen in Square's apps or in the WordPress admin where the plugin exposes those actions. The bot quotes status, confirms refund eligibility against your policy, and notes when a teammate will process it. That preserves Square's payment and tax rules.

Yes, if you sync available slots into WordPress. A common pattern is a small custom post type that holds the next two weeks of open slots per service and staff member, refreshed on a recurring job. The bot reads that and quotes real openings. Booking the slot still happens in Square's own calendar to keep capacity and conflicts correct.

Through the WordPress user logged in on the request, mapped to Square orders or appointments via email or user_id on the order. Logged-out visitors see no order data; they get a pre-sales bot under separate display conditions. An internal admin bot can look up any customer by name or email for support.

Yes, if you mirror per-location inventory. Square supports multiple locations and most plugins write a per-location stock row. SleekAI reads those rows and can name the location with stock left. For pickup-focused merchants, this is the single most valuable answer the bot gives, and it stops the bot from contradicting the till.

Square calculates tax and fees at the point of sale. The bot can quote your published rates from a policy doc but should defer to the receipt for any specific number. Telling the bot to defer rather than estimate is a sensible pinned rule for any commerce chatbot, especially around tax.

Only what you map. SleekAI exposes a defined set of named variables in the system prompt. Full customer profiles or unrelated orders stay out unless you expose them. For public bots, expose only the matched customer's own order status and policy details. Reserve broader data for an internal admin bot under display conditions.

Stock and appointment Q&A is precise; pick a fast model with strong instruction-following and a low temperature. For free-form questions like service descriptions or pre-sales styling advice, a stronger model is worth the cost. SleekAI's BYO-key model picker lets you mix under a single chatbot with routing rules you control.