Yes. SleekAI's custom-table data source maps wp_mailster_subscribers, wp_mailster_lists, the campaign post type, and wp_mailster_actions into named variables. Variables resolve at request time, so a campaign sent moments ago appears in the next answer without any sync layer or background job.

Yes. The Wizard maps mailster_amazon_ses_options into the system message. The bot can confirm the active AWS region, the throttle in emails per second, and whether the access keys are configured, all without exposing the raw credentials to the model.

You need an account with at least one supported provider. SleekAI works with OpenAI, Anthropic, Google, and OpenRouter, so an admin-only newsletter bot can use a small cheap model for short metrics queries. Usage and billing stay with your provider account, not with SleekAI.

Not usually. The data is admin-only. Set display conditions to wp-admin URLs for the administrator and editor roles, so end users never see the bot. Customer-facing bots can run separately on the public site with different data sources.

Only the data you map into the system message reaches the model. Skip the raw access keys and map only a boolean for configuration state plus the region. The credentials stay in wp_options while the bot still answers integration-health questions and configuration summaries.

Yes. Mailster keeps segmentation rules per list and per campaign in the campaign post meta. SleekAI maps postmeta by key, so the bot can summarise which conditions a campaign used and which subscribers match them when an admin asks for clarification.

For very large installs, push aggregate counts and per-list summaries into the prompt instead of raw rows. SleekAI also supports OpenAI Files vector stores of up to one gigabyte per file, which lets the bot retrieve specific subscribers or campaign chunks at query time.

Yes. Conversation logging stores each user message, the assistant reply, the model name, tokens used, and the originating page URL. Inside wp-admin those URLs map cleanly to Mailster screens, which gives leadership visibility into how the team uses the bot.