Yes. When the member is logged in, SleekAI can include their level, status, transactions, active subscription, and next renewal date in the system message. The model only ever receives data for the current user, so a logged-in member cannot read another member's record. You decide which fields end up in the prompt.

Yes. MemberPress access rules are stored as posts that link a tier to content, and SleekAI can read them as a data source. The bot can answer which level unlocks a specific course, post type, or category, and explain what would change if the member upgraded or downgraded.

Yes. Display conditions support membership level and billing state, so the bot can be limited to active Pro or Lifetime members and hidden from free or expired accounts. A separate public bot can run on the same site with no access to membership data.

No. The bot's prompt only contains the fields you mapped for the currently logged-in user. There is no global query that exposes other members, and SleekAI never includes an entire transactions table in the request. You stay in control of which fields surface and which don't.

Yes. MemberPress group memberships and sub-accounts are stored as standard MemberPress data with their own meta. SleekAI can include the parent group, the active sub-accounts, and the seats remaining if you map those fields, so the bot can answer questions specific to a corporate plan.

Conversations are logged inside WordPress with the user, model, token usage, and page URL attached. Support leads can review the log to spot tone, accuracy, or repeated questions and feed those back into the system message or your access rule descriptions.

It can describe them. SleekAI exposes the member's current price, billing cycle, and renewal date, and the bot can use those to explain how the next charge would change if they switched tiers under your configured rules. The actual switch still happens through MemberPress, the bot just removes the guesswork before the member clicks.

Yes. Display conditions can target the MemberPress account page and any sub-pages, so the bot lives where members already manage their plan. Combined with the JS API, you can also trigger the bot from a custom button next to the renewal or invoice list.