Your community's conversation in the same account that opens the course
Your community's conversation already exists. It just doesn't live with you: it lives in someone else's group, with no searchable history and no way of knowing who in there has already bought.
Here it stays in the same product and under the same login as the content and the paid access. The throttle is enforced on the server, every moderation action leaves a record, and what this chat doesn't do is written in the last section.
Your community already talks. Just in someone else's group.
Your community's conversation isn't standing still. It's in a messaging group, on a chat server, in a social network's DMs. It works — and that's exactly why what's missing goes unnoticed.
Control: you moderate by asking nicely and removing people. History: whatever got answered yesterday sank into the scroll, and whoever joins today starts from zero. Connection: whoever asks a question in the group is the same person who bought your course, but nothing in the group knows that.
Here the conversation stays in the same place as the content, the access, and the profile of whoever's paying. It's the same account, not a separate signup on the side.
One room. With the throttle in your hands.
The community chat is a single room. It isn't thirty channels for you to discover, six months later, that twenty-eight are empty.
Inside it is everything a messaging group has: real-time messages, who's typing, emoji reactions, quoted replies, attached images, editing, and deleting your own message.
What a group doesn't have is the dashboard. You decide whether chat is off, open to moderators only, or unlocked for members. You set the minimum interval between two messages from the same person. And the rule is enforced on the server, before the message is saved — it isn't a screen warning.
Eleven at night, the conversation turns sour. What can you do?
In the group, the scale has two points: warn or remove. Here it has steps.
Mute the person for a period — or indefinitely — with a written reason. Delete a specific message. Clear the history: for the entire room, for the last few hours, or just for one person. If the case is serious, the ban is in the admin dashboard, and the account stops being accepted at platform authentication.
Every action is logged: who moderated, who was moderated, what was done, the reason, and for how long. When the member complains in a DM, the answer is right there on a screen.
A ban doesn't instantly kick out whoever already has chat open. That limit is stated in the last section.
The 1:1 happens one way or another. The question is where.
Two members are going to talk privately. If the product doesn't allow it, they'll swap @ handles and move to another network's DMs — and from that point on, you're not in the conversation anymore.
Direct messages live in a floating dock on any screen in the community: real-time 1:1 conversation, typing indicator, read receipts, and quoted replies. Whoever crosses the line gets blocked by the member themselves, and the block is checked on the server — both when opening the conversation and when sending.
A feed post can be sent as a card inside the conversation. The "look at this" points inside the platform, not to a screenshot.
The direct message composer sends text, quoted replies, and shared posts. Files, no.
The conversation in the same database as paid access.
Whoever writes in the room is the same account that opens the course. When the sale comes in through the webhook of the gateway where you already sell, the product creates the user and unlocks access to the bundle — with the origin recorded: type, external transaction id, and who granted it. There's no parallel signup for the conversation.
Participating earns XP. Each message adds a configurable value to the profile's XP, with a daily cap so it doesn't reward whoever's just making noise, and every grant is logged.
And repeated questions have someone to answer them. You turn on an assistant with its own name, avatar, and personality, fed by a knowledge base that's yours: your texts, your rules, your material. It builds the answer from up to ten active items in the base and the room's last ten messages, has an hourly usage limit, and can run on your own OpenAI key. The reply enters the room tagged as an AI message.
The assistant only steps in when called by name. It doesn't monitor the room or answer on its own.
Before you find out on your own.
This chat isn't a messaging server with your brand on it. Six limits, stated here and not in month two.
It's a single room. There are no channels by topic and no channels by space, and you can't pin a message.
History is saved and scrolls back, but it isn't searchable yet: the platform's search covers posts and people, not messages.
A reply is a single-level quote, not a thread with a side panel.
A new message still doesn't turn into a push notification: push covers comment, like, mention, reply, achievement, follower, and feed event.
Chat messages don't count toward the ranking. The ranking counts posts, comments, and likes; chat XP stays on the profile.
Banning doesn't instantly kick out whoever already has a session open. The account is refused at the next authentication and refresh tokens are invalidated, but the current session continues until it disconnects.
If your operation depends on thirty channels and attachment search, a dedicated messenger does that better. If it depends on the conversation being on the same side as paid access, this is it.
Continues in
Who gets into the community is decided before chat, in the space's permission settings: 03 · Communities →
The phrase "silent for 21 days" is written here, in this room's connection. What that means for reading the data: 05 · Retention →