Room

Watchers main functionality is online chat rooms (rooms or chats), that can be public and private. Chats can be integrated to any platform: website, mobile apps, or mobile web. Any chat room can include communication via text and, additionally, audio or video live-streaming.

Room Types

Public chats

Any user can participate this type of chats.

Public chats can be platform-driven or influencer-driven and can be opened to the content on the platform in general or to a specific real-time content page or a specific event (we recommend this approach more than a general one, as it creates the context and unites users more intuitively, thus providing better metrics' growth).

A room is automatically created upon opening when a new roomId is received, either via the API or upon the first user entry into the room. Rooms can also be scheduled in advance, allowing access to open at a specified time. Scheduling a room is possible through the back office or the API.

Any number of rooms and participants in rooms is available.

Threads

Threads function as sub-rooms within chats and are displayed as separate entities in the admin panel. They provide a focused space for discussions branching off from specific messages while maintaining a connection to the parent room.

One Thread per Message: while the number of threads within a chat is unlimited, each thread can only be created in response to a single message. Only one thread is allowed per message.

Thread Creation: a thread is initiated by responding to a specific message. Users can access the thread exclusively through the widget attached to the message that prompted its creation.

Message Display in the Admin Panel: messages from a thread are displayed in three locations:

• All Messages Feed: the thread messages appear in the overall feed of all chats, providing a comprehensive view.
• Parent Room Feed: thread messages are visible in the feed of the parent room where the original message is located.
• Thread Room Feed: the thread is displayed as a separate room in the list of rooms, with its own dedicated feed for managing thread-specific discussions.

Private chats

To implement private rooms, provide users on your frontend who should have access to a specific chat with a direct link to open it. This approach enables private room functionality without requiring additional development, if necessary.

For instance, you could display a “Join Chat” button only to users with the appropriate access rights. For example, a VIP room could be available exclusively to VIP users, while others would see a message prompting them to upgrade their status to gain access.

Room Initialization

Watchers offers flexible options for launching rooms, including the use of Room API for advanced scenarios:

Launch Upon User Entry

Room can be initialized automatically when the first user enters. This is typically triggered when:

• A user clicks on a link (button) to the room displayed within a service window or embedded in a user interface.

This method provides immediate access to a room, ensuring that users can interact without delays, ideal for impromptu or casual gatherings.

Scheduled Initialization

Perfect for scheduled events, allowing precise timing. Here’s how to set it up in the admin panel:

• Event ID: specify the event ID in the admin panel.
• Start/End Date and Time: indicate the exact start and end times for the room.

This method ensures that the room is ready and available exactly when needed, making it perfect for pre-planned streams or events. All configurations for scheduling take place within the admin panel for seamless setup and management.

Important Note: a scheduled room will not appear automatically on the partner's platform. Typically, scheduled rooms are used for specific events, and the chat needs to be manually added to the event page on the platform.

API-Based Launch

Using the Room API, rooms can be created or modified programmatically, providing advanced customization options.

• Create Room via API: define room parameters (e.g., roomId, name, about, isSpeak) to create and configure rooms based on specific requirements.
• Schedule and Control Status: use API calls to set startTime and endTime or adjust room status (LIVE, SOON, ENDED) as needed.
  This method provides full control over room setup and timing, ideal for dynamic and automated workflows.

All methods ensure rooms can be launched according to specific needs, enhancing user experience and event flexibility.

Room Access

Chats offer two types of access to users, each providing distinct levels of interaction:

Full Access

Users with full access are fully authorized and can actively participate in the chat.

Read-Only Access

Users with read-only access can view chat content but are restricted from participating in discussions. They cannot:

• Send messages
• React to messages
• Interact with other participants

This mode is suitable for scenarios where users need to observe discussions without actively contributing.