Yes. SleekAI maps the sendlayer_settings option from wp_options into the chatbot's system message. The bot can read the API key state, the default from address and name, the reply-to, and the logging toggle, all at request time without any sync step or background job.

Yes. SendLayer's plugin keeps a log of every send, either in a dedicated table or in a log post type, depending on the version. SleekAI's data sources support both. The bot can answer per-recipient and per-subject queries with the live timestamp and SendLayer status.

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

Not usually. The data is admin-only by nature. Set display conditions to wp-admin URLs for the administrator role so only the people who manage email delivery see it. End-user-facing bots can run separately on the public site with different data sources.

Only the variables you map into the system message reach the model. If you only map a boolean for whether the API key is set and never the key itself, the secret stays in wp_options. Map a redacted token like the last four characters if you want a visual confirmation in the chat.

Yes. WP Mail SMTP can route through SendLayer as a mailer. SleekAI maps both the WP Mail SMTP options and the SendLayer plugin options when they coexist, so the bot can confirm which mailer is currently active and where the from address is being set.

Variables resolve at request time, so a send recorded one second ago is included in the next answer. There is no separate AI sync layer. If logging is disabled in the SendLayer settings, the bot can still read sendlayer_settings but not historical sends.

Yes. Conversation logging stores each user message, the assistant reply, the model name, tokens used, and the originating page URL. Because the bot runs inside wp-admin, those URLs map clearly to admin screens, which is useful when reviewing the log later.