Yes. Basic group, profile, and post indexing works on free and paid PeepSo. The free edition exposes the same peepso_groups, peepso_users, and post tables that the paid version does, so SleekAI's integration covers both. Paid PeepSo features like advanced moderation or premium add-ons are picked up automatically when present, but the core bot experience requires only the free edition to start.

Only if you opt in. By default, private group content is excluded from the bot's context. SleekAI respects the PeepSo visibility rules that govern the front end, so a private group's posts and members never leak into a public-facing bot. If you want a bot to operate inside a private group with full context, scope it to that group with display conditions on group membership and treat the bot as an internal tool.

Yes. When the visitor is logged in, the bot uses the PeepSo display name in the opener. Combined with profile fields and group memberships, the welcome line can mention the member's primary group, their interests, or the recent thread they engaged with. That personalization sets the tone for the rest of the conversation and makes the bot feel like part of the community rather than a generic widget.

Yes. PeepSo Chat handles human-to-human DMs, while SleekAI handles AI replies through its own widget. The two coexist; they do not interfere. Members can DM each other through PeepSo Chat for personal conversations and use the SleekAI bot for community-wide questions like group recommendations or rule clarifications. The bot does not try to replace PeepSo Chat; it adds a parallel surface for the questions a human DM is wrong for.

Comments can be indexed alongside posts so the bot includes thread context, not just the original post. That matters for community discussions where the canonical answer often lives in a comment rather than the top-level post. Visibility rules apply: comments on private posts stay private. The result is a bot that surfaces the actual community conversation rather than an out-of-context snippet from a single post.

Yes. Multibot support lets you run a different bot per group or per page. A common pattern is a global welcome bot for the homepage and per-group bots for high-traffic groups, each with prompts tuned to that group's culture and rules. Display conditions on group membership, user role, and page template decide which bot loads where, and the bots stay independent in their conversation logs and configuration.

No. The bot describes what to do next and links to the right PeepSo screen, but it never writes to the community on the user's behalf. That guardrail is essential for community trust; a bot that posted automatically would damage relationships faster than the integration could deliver value. PeepSo handles every write that involves identity, moderation, or notification; SleekAI handles the conversation that leads up to the action.

Yes, when WPML, Polylang, or TranslatePress is installed. SleekAI reads the active locale and replies in that language, with community posts in different languages feeding the bot's context per locale. Multilingual communities should configure per-language welcome copy in the chat widget and review conversation logs per language to spot quality differences. The locale signal comes from the multilingual plugin; the bot consumes it without separate setup.