MADE FOR YOUR USERS
Build the conversation around a specific task or relationship, with membership and history rules that match the way people work together.
Project Teams
Give a working group one conversation for updates, photos and files. Mention the right teammate and keep the discussion connected as people join or leave the project. Your app decides who belongs to each team.
Service Groups
Connect a customer, service representative and specialist in a shared group. Exchange the details and attachments they need to resolve a request, while your application controls assignments, access and the service workflow.
Event Groups
Create a conversation for an event’s organizers or participants to share meeting points and last-minute updates. Connect admission to your registration rules, and decide when the group should close after the event.
Friends
Let friends plan a weekend, exchange photos and pick up where they left off. Give them a familiar group experience inside your app, with invitations, membership and message history suited to private conversations.
CUSTOMER SUCCESS STORY
Habby uses Tencent RTC Chat to bring Archero players together around shared interests and help them team up for battles. Players exchange text, emojis and custom messages within the game.
Group member profiles can display player levels and badges, giving people context about the teammates they are talking to.
CHOOSE WITH CONFIDENCE
See how messaging fits your product and what your application connects.
| Your requirement | How it is delivered | What to plan for |
|---|---|---|
| Group types and joining | Work, Public, Meeting, AVChatRoom and Community support different group experiences. | Compare joining, approval and lifecycle behavior. Invitations and open joining are not available in every group type. |
| Roles and member controls | Group management APIs provide role and membership operations, with controls that depend on group type. | Check administrator, mute and removal support before choosing a type. Your app owns business roles and moderation policy. |
| Rich messages and mentions | Chat supports text, media, files, custom messages and group mentions through supported SDK APIs. | Confirm the UI Kit components, message rendering and platform support you need. Connect application-specific actions yourself. |
| History and notifications | History, unread counts and notification settings help members return to a conversation. | Check history retention, new-member visibility and unread support for your group type. Configure platform push separately. |
| Group size and cost | Chat plans define usage quotas, available features and group limits. | Estimate active users, group count and members per group. Check current plan limits instead of assuming unlimited capacity. |
THREE STEPS TO YOUR FIRST CONVERSATION
Connect the group chat API to a ready-made UI Kit or your own interface. Validate the group lifecycle with several test accounts before launch.
BUDGET BEFORE YOU BUILD
Budget for your group chat API integration. Plan around monthly active users and the group features your app needs. Compare the free quota and paid plans before choosing your launch configuration.
CHAT FREE PLAN
Start with the free Chat plan. Monthly usage renews automatically; review feature limits and upgrade requirements as your audience grows.
CHAT STANDARD
For core messaging and group chat. Compare plans for advanced features such as read receipts, translation and community capabilities.
YOUR APPLICATION
Allow for your Chat plan and any applicable excess usage, storage, push and application development. Include the group sizes, retention settings and moderation workflow you expect to support.
SEE THE PRODUCT IN ACTION
Create a Tencent RTC Chat application, integrate a supported SDK or UI Kit and connect your user accounts. Generate UserSig on your server, select a group type, then implement group creation, membership and messaging. A UI Kit gives you a starting interface; the SDK lets you design your own.
Start with how people join, who can manage them and what message history they need. Work suits invitation-based working groups; Public supports approval-based joining; Meeting suits temporary discussions, but its conversation unread count stays at zero. AVChatRoom and Community serve other audience and organization needs. Compare the current group configuration table before choosing.
History behavior depends on the group type and its configuration. Check whether new-member history is supported, how it is enabled and the retention period included in your plan. Test with an account joining after messages have been sent so the result matches your privacy and onboarding requirements.
These controls vary by group type. For example, Work groups do not provide the same administrator and muting controls as Public groups. Review the group configuration table and SDK APIs, then implement the permissions, reporting and escalation policy your application needs.
Chat pricing depends on your plan and usage, including monthly active users. Group count, members per group, message retention and advanced features have plan or group-type limits. The free plan provides a starting quota; check the current pricing and limits pages before estimating your production budget.
Compare supported group types, member limits and message behavior. Define invite-only membership or discovery rules in your backend before connecting the group to your UI.
Use supported membership operations together with your app’s permission model. Check which administrative actions are available for the selected group type and plan.
