Tribulant Newsletters is a long-running self-hosted newsletter plugin with mailing lists, double opt-in, campaigns, autoresponders, queues, and statistics. It stores everything in its own set of tables under the WordPress database, including subscribers, list memberships, queue items, and campaign history. Subscribers and editors both ask very specific questions about that data.

SleekAI reads Tribulant's tables directly. Subscribers, list memberships, scheduled campaigns, and statistics all map into named variables that the chatbot uses on each turn. A logged-in subscriber can ask which mailing lists they are on, when the next campaign is due, and how to switch to a less frequent list. The bot reads the subscriber's actual row, the actual list metadata, and Tribulant's campaign queue rather than guessing from an external help article.

Multibot lets a site run several chatbots at once. A public chatbot on the signup page can explain lists and frequency. A logged-in chatbot in the subscription preference area can read the visitor's own membership and act on it. An admin chatbot inside WP Admin can read campaign queue and history tables for the editorial team. All three coexist on one Tribulant install with one provider key.

Tribulant Newsletters has been a self-hosted newsletter option for WordPress for over a decade. Many of the sites running it are membership clubs, niche publishers, and small businesses that prefer not to send their list to an external ESP. The data lives inside their own database, which is also where the visitor-facing site lives.

That means the chatbot story for Tribulant should be tight. Subscribers should be able to ask which lists they are on without leaving the page. Editors should be able to ask about last week's campaign without flipping tabs.

New visitors should be able to ask what a given list is about and how often it sends. A generic chatbot does none of this because it cannot read Tribulant's tables. SleekAI does.

It maps the relevant tables into variables that resolve on each turn, scopes access per chatbot via display conditions and user role, and triggers Tribulant's own methods for any change so that confirmation emails and double-opt-in still apply. The conversation log lives next to Tribulant's own logs, the provider key stays under the site owner's control, and the whole setup feels native to the plugin rather than bolted on.