Yes. The Wizard maps gf_form, gf_entry, gf_entry_meta, and the Square rows from gf_addon_feed into named variables your system message can use. Variables resolve at request time, so a new payment or refund webhook from Square shows up in the next answer without re-syncing.

Yes. The Square Add-On stores the failure code and reason on the entry. SleekAI reads that, matches it to the feed's amount and currency, and explains INSUFFICIENT_FUNDS, CVV_FAILURE, GENERIC_DECLINE, and CARD_NOT_SUPPORTED against the actual charge attempt instead of citing generic Square API docs.

Yes. The feed meta records the location_id, so SleekAI exposes it as a variable. When you ask about a specific entry, the bot returns the location name, the feed that posted to it, and the amount. You can also assign one chatbot per location if your team is split that way.

No. The Square Add-On never stores PAN data in WordPress, only the Square payment_id and a last4 reference. SleekAI inherits that boundary. Even an admin asking 'what card did they use' only sees the last4 and the brand string, never the full number or expiry.

Yes. The feed meta records whether the feed is one-time or subscription, plus the linked plan_id. SleekAI exposes those flags so the bot can say 'this is a $39 monthly subscription on plan plan_4hX' rather than treating every charge as a single capture.

Yes. Multibot mode runs several chatbots on one site. Pair each Square feed or form with its own bot scoped by form_id query rule, so the studio booking desk and the merch shop desk see different system prompts and different variable sets in the same WP Admin.

The feed's mode flag (live or sandbox) is part of the feed meta. SleekAI surfaces it in answers so staff doing a dry run see 'this is a sandbox feed' before they panic about a real charge. You can also run separate chatbots for live and sandbox if you prefer the explicit split.

You need an account with at least one supported provider. SleekAI works with OpenAI, Anthropic, Google AI Studio, and OpenRouter, so a cheap fast model can handle charge lookups while a stronger model writes longer summaries. Usage and billing live on your provider account, not on SleekAI.