OpenCreators in one minute
- Use chat for relevant questions, agreed intake, fulfillment coordination, and order context.
- Unread indicators can appear in navigation and the browser tab when new messages arrive.
- Keep passwords, payment credentials, verification codes, and unnecessary private data out of chat.
OpenCreators includes authenticated chat surfaces for creator and customer conversations. A conversation list shows peers and recent activity; the active panel shows the message history, product or order context where available, and a composer for new messages.
Chat is most useful when it supports a clearly defined product. It can clarify a missing detail, collect agreed inputs, and coordinate fulfillment. It should not replace an accurate public description or become a channel for unrelated sensitive information.
Starting a conversation
A public creator or product path can lead a signed-in user toward chat. If the visitor is not authenticated, the product can ask them to log in before entering a protected conversation. The chat route identifies the peer and loads the relevant conversation state.
Ask one focused question that cannot be answered from the listing. Include the product name and the decision you need to make, but avoid posting personal or payment information merely to get a faster response.
Unread and browser signals
The interface tracks unread conversations and can place an unread marker on navigation. The web app also updates the browser favicon when unread IM state exists, giving a visible signal even when the chat page is not selected.
Opening a conversation should update read state through the actual message lifecycle. A visual badge is a convenience, not a durable record of whether a contractual message was delivered or accepted.
Product and order context
Chat messages can include a product context card, such as an order-paid item with image, title, type, duration, short description, price, and time when that data is available. The card should use the correct design state and product source rather than a generic white box.
Use the context card to identify the transaction, then discuss only the agreed fulfillment. If the buyer wants a different service, create or purchase the appropriate product instead of silently altering the original order.
Writing and privacy
The composer supports multiline text and can expand over the conversation. The expanded composer should overlay the message area instead of permanently pushing the history upward, preserving reading position while the user writes.
Share only information required for the product. Never send passwords, one-time codes, complete payment details, identity documents, or private third-party data unless a secure and explicitly authorized workflow requires it.
Frequently asked questions
Why is there a dot on the browser tab?
OpenCreators can change the favicon to signal unread instant messages. It is a visual reminder to return to chat.
Can chat replace the product description?
No. Important scope, price, format, and buyer expectations should be visible before purchase. Chat is for clarification and coordination.