Noptin stores subscribers and campaigns inside WordPress. Subscribers live in Noptin's own tables, with tags, custom fields, and source attribution. Campaigns and automation triggers are stored as custom posts with their own meta. SleekAI's data-source wizard maps subscriber records and campaign metadata, so the bot can know whether the current visitor is subscribed, which tags they carry, and what recent campaigns went out.

That changes what the bot can do. For a known subscriber, it can confirm what list they're on, when the last campaign was sent to them, and how to unsubscribe (without inventing a link). For an unknown visitor, the bot can ask the right qualifying questions, then create a Noptin subscriber via the REST endpoint with the right tags applied, so the lead lands in the same automation flows as a regular signup form would have produced.

Display conditions scope the bot by post type, taxonomy term, user role, logged-in state, and URL pattern, so a marketing bot on landing pages can capture leads while a separate bot on the account area handles subscription preferences for existing readers. Every conversation is logged inside WordPress with model, token usage, and page URL, so the marketing lead can audit answers before scaling the bot beyond a small set of pages.

Most newsletter signups happen on a thin sliver of pages with a one-size-fits-all form. A generic chatbot dropped on the same site can't say what the last issue was about, doesn't know whether the visitor is already subscribed, and can't add a developer-only tag for a visitor who clearly came in through engineering content. Noptin already supports tag-based segmentation and per-list automation, but the conversation layer on top of that segmentation is usually missing.

SleekAI fills the gap by exposing subscriber status, tags, and campaign metadata to the assistant, and by giving the conversation a clean handle to create a new subscriber with the right tag when the visitor commits. The result is a chat that can pitch the newsletter accurately, segment leads at the point of capture, and answer preference questions for existing readers without sending them on a tour of the help docs. The marketing lead also gets a quiet log of which audience segments come up most often, which is the cheapest way to know whether the editorial calendar is matched to the audience the site actually has.