WPForms stores the form, sequence, and tag IDs inside the connection JSON under providers.convertkit. SleekAI maps that JSON into a variable your system message can read, so the bot quotes real IDs without anyone needing to log into ConvertKit (now Kit).

Yes. The addon stamps ConvertKit's response on each entry. If the API returned 200 with a subscriber ID, the bot reports the success. If it returned 401 or 400, the bot quotes the error instead of pretending the subscriber synced cleanly.

Not if you scope it correctly. Use display conditions to require administrator or editor role, logged-in state, and /wp-admin/ URLs. The widget will not render outside that scope, and form, sequence, and tag IDs stay inside the dashboard.

Yes. Conditional rules live inside the same providers.convertkit JSON. The bot can describe which rules fire which connection, so a form where consultants go to one sequence and clients go to another stays explainable in chat.

Yes. Multibot mode runs several chatbots on one site. A Newsletter bot, a Product Launch bot, and a Free Course bot can each have their own scoped prompt and conversation log so answers stay relevant to whichever form is being audited.

The bot reads what is in the WPForms connection JSON. If you created a new tag in ConvertKit but did not yet update the form's connection, the bot will say so honestly rather than pretending the tag is being applied automatically.

Yes. ConvertKit rebranded as Kit and the WPForms addon was updated to match. The underlying connection structure stays the same, so SleekAI reads the same providers.convertkit JSON. The bot uses whatever name you prefer in chat.

You need an account with at least one supported provider. SleekAI works with OpenAI, Anthropic, Google, and OpenRouter, so a cheap fast model can handle routine routing questions while a stronger one runs longer audits. Usage and billing live on your provider account, not on SleekAI.