Onyx Chat is being prepared as one place for direct and group conversations, calling, communities, and service interactions. Available actions may vary by account, conversation, device, and service route.
Native Onyx Chat launch awaits verified end-to-end encryption with keys held on users' devices. The current message service stores content with Onyx and does not meet that launch requirement, so messages should not be treated as unreadable by Onyx.
Calling, attachment, and other conversation actions are planned as part of the Chat experience, with availability based on account, conversation, device, and service route.
Unified inbox
Conversation preview
This preview shows example conversation actions and statuses. Native Onyx Chat launch awaits verified end-to-end encryption with keys held on users' devices.
Maya Chen
Example message
Message
Example action
Voice
Example action
Video
Example action
Pay
Example action
This preview illustrates planned routes; calling and messaging options depend on account and service support.
Planned Unified Inbox
The planned inbox will bring personal conversations, group threads, community spaces, service conversations, and requests together.
The planned experience is designed to keep each conversation tied to its thread, participants, and permissions as contacts change devices, join Onyx, add a number, or move through changing network conditions.
It is intended to separate direct messages, groups, communities, and service conversations so larger spaces do not drown out personal communication.
Direct And Group Conversations
Direct conversations are planned to connect two authenticated accounts through supported Onyx identity, number, or contact paths.
Group and other conversation capabilities depend on account and service state. The current message service stores content with Onyx; native Onyx Chat launch waits for verified device-held end-to-end encryption.
Some people may only be reachable through SMS or phone calling. Supported mobile services can provide those separate communication paths.
Calls
Calling is part of the planned Chat experience, with availability and behavior depending on the account and service route.
Native Onyx Chat launch awaits verified end-to-end encryption with keys held on users' devices.
Fallback Communication
SMS and carrier calling are separate mobile services, with availability based on plan, country, and network support. They do not change how Onyx Chat stores its text messages.
Trusted Reach And Requests
The planned request flow is designed to keep unknown contacts out of the main inbox until the account holder chooses how to respond.
A conversation may be handled as an accepted thread, a request, a restricted conversation, or a blocked contact based on contact context and account settings.
The planned request view includes sender details, contact context, and a limited preview, with options to accept, decline, block, or report before a conversation enters the primary inbox.
This design aims to protect communication without requiring a public profile or open messaging model.
Media And Attachments
Media and file actions are part of the planned Chat experience where supported by the conversation and service route. Native Onyx Chat launch awaits verified end-to-end encryption with keys held on users' devices.
Search And Discovery
The planned search experience is intended to find conversations, contacts, communities, channels, files, links, media, and service conversations.
Discovery is planned around contacts, usernames, QR codes, invite links, communities, and phone numbers. Account context and permissions will determine which conversation actions are available.
Notifications
The planned Chat experience includes default, muted, priority, and digest-style notification options.
Community and larger-channel notification options are intended to reduce noise through muted defaults, batched delivery, mention prioritization, announcement priority, and role-aware settings.
The planned controls let you choose which conversations deserve immediate attention and which can wait.
Payments Inside Chat
Payment-linked actions such as requests, confirmations, service cards, appointment cards, status cards, and identity-sharing actions are part of the planned Chat experience.
The roadmap keeps those actions connected to the conversation context. Eligibility, verification, country support, and account state will affect availability.
What Can Vary
Planned Chat capabilities vary by conversation type, fallback route, country, account permissions, verification state, number support, network conditions, and device capability.
The product is designed to explain relevant limits and make the next available action clear.