Yes. SleekAI's Wizard maps any WordPress option key into a named variable in the chatbot's system message. Drop bbpnns_newtopic_recipients, bbpnns_newreply_recipients, bbpnns_notify_anonymous, and the subject and body templates into the prompt, and the bot will answer with the values stored in your wp_options table at request time.

Yes. bbPress Notify saves overrides as postmeta on each forum CPT entry, and SleekAI can read postmeta fields by key. When a user asks about a specific forum, the bot can pull that forum's override list and contrast it with the site-wide default in a single response.

You need an account with at least one supported provider. SleekAI works with OpenAI, Anthropic, Google, and OpenRouter, so a small forum can run a cheap fast model for short answers about settings. Usage and billing stay with your provider, not with SleekAI.

Yes. Display conditions support user role, URL pattern, and post type. A common pattern is one bot inside the wp-admin URL path that answers configuration questions for admin roles, and a separate bot on the public forum that answers member-facing questions about subscriptions and digest emails.

Yes. SleekAI can map the result of wp_roles or a custom callback into the system message. So when a user asks which role gets emailed on a new reply, the bot uses the actual role labels from your install rather than a generic list of WordPress defaults that may not match.

Yes. Conversation logging stores each user message, the assistant reply, the model name, tokens used, and the originating page URL. For bbPress Notify, that URL is typically the plugin settings screen or a specific forum, which gives you context when you read the log later.

Indirectly. SleekAI does not send the notification emails itself, bbPress Notify does that through wp_mail. But the chatbot can read the active SMTP plugin's options and remind users to check its send log when an email is missing, by mapping that plugin's option key into the prompt.

Only the data you map into the system message reaches the model. If you only map opt-in fields like recipient roles and subject templates, no personal email addresses are sent. If you want full audit, conversation logs let you see exactly what context was attached to each request.