MADE FOR YOUR USERS
Give each community a messaging experience that fits how its members get to know one another.
First conversations
Keep a shared interest close to the opening messages while your app decides when a match can chat.
Shared interests
Let matches share a photo or voice note about the things they enjoy.
Long-distance
Use messages and history so people can reply when they are available. Add calling when both are ready.
Mature communities
Customize the conversation interface and controls to fit your community’s preferences.
RELATED CUSTOMER STORY
WITH brings voice and video conversations into its dating app so matches can get to know each other beyond their text exchanges. The published case describes its Tencent RTC calling integration.
Related dating case: the story covers voice and video calling within the matching journey; it does not identify WITH’s text messaging provider.
CHOOSE WITH CONFIDENCE
See how messaging fits your product and what your application connects.
| Your requirement | How it is delivered | What to plan for |
|---|---|---|
| Match conversations | One-to-one messaging and custom UI | Your backend supplies matches and messaging eligibility. |
| Photos and voice notes | Rich message types | Apply content policies and check client support. |
| Returning users | History, unread state and offline push | Configure retention and discreet notification content. |
| Blocking and reports | Blocklist APIs and application workflows | Your team handles report review, appeals and unmatch rules. |
| Voice and video dates | Separate Tencent RTC Call integration | Add invitation, consent and pricing for calls. |
THREE STEPS TO YOUR FIRST CONVERSATION
Connect match permissions, embed messaging and test the full relationship lifecycle.
BUDGET BEFORE YOU BUILD
Budget for your dating chat SDK integration. Plan for messaging MAU and the features your dating community needs.
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
Estimate messaging users, history and media usage. Include your matching integration, review workflows and any additional voice or video service.
A dating chat SDK supplies messaging components for conversations inside a dating app. Tencent RTC provides client SDKs, UI Kits and backend APIs; your app supplies profiles, matching and eligibility rules.
Your application owns matching, discovery and subscriptions. Authorize messages through your backend after a mutual match and recheck permissions when the relationship changes.
Treat unmatching and blocking as separate events. Update your server-side messaging permissions and use supported blocklists for unwanted contact. Define history and retention behavior explicitly.
Audio messages can be part of the Chat experience. Voice and video calls use a separate Call integration with invitation, consent and product pricing to review.
Use fictional test accounts to check blocked users, revoked matches, reporting, notification previews and message history. Confirm that backend checks enforce the same rules as the interface.
Let your matchmaking backend authorize a conversation after a match. Connect authenticated profiles and revoke or restrict access when users block, report or unmatch.
Messaging and calling use separate product integrations. Open the dating calling guide to plan permissions, call invitations and the transition from a match conversation.
