Onyx Chat is the communication system attached to your Onyx account.
It combines:
- direct messaging
- group conversations
- communities and channels
- voice calls
- video calls
- phone-number messaging fallback
- payment-linked messages
- trusted service conversations
- media and file sharing
Messages, voice calls, and video calls between Onyx users are end-to-end encrypted.
The same conversation can continue across:
- Onyx-native messaging
- SMS fallback
- phone-network calling fallback
- degraded network conditions
- supported connected communication routes
The goal is communication continuity.
You should not need to think about networks, protocols, or providers before reaching someone. The app selects the best available route and only explains limitations when they affect the action you are trying to take.
Unified inbox
Conversation preview
Select a thread to see available actions, delivery status, encryption notes, and fallback behavior.
Maya Chen
End-to-end encrypted
Message
Available in this thread
Voice
Available in this thread
Video
Available in this thread
Pay
Available in this thread
If internet calling or rich messaging is unavailable, the app can show fallback options where supported.
How Conversations Work
A conversation inside Onyx Chat is more than a message list.
Each thread can include:
- messages
- calls
- media
- files
- payment actions
- trust signals
- requests
- notifications
- service updates
- route status
The conversation stays attached to the same relationship even if:
- the recipient switches devices
- the route changes
- fallback messaging activates
- internet calling degrades
- the recipient joins Onyx later
- a number changes state
Conversation Types
Onyx Chat currently supports:
- direct conversations
- group conversations
- communities and channels
- service and business conversations
- request conversations
- phone-number conversations
Some conversations are fully Onyx-native with encrypted messaging, calling, and media.
Other conversations may rely on SMS or phone-network fallback depending on the recipient and available communication route.
Message Types
Supported message types can include:
- text
- images and video
- files
- voice memos
- stickers
- payment requests
- system messages
- call events
- service cards
Not every route supports every message type.
For example:
- SMS fallback may support text only
- phone-network fallback supports calls but not rich media
- degraded routes may temporarily disable larger uploads or video calling
The composer should show route limitations before you send the message.
Message States
Messages can appear as:
- pending
- sent
- delivered
- read
- failed
- unsupported
A failed message does not always mean the conversation failed. Some routes can retry automatically or fall back to another supported communication method.
End-To-End Encryption
Messages, voice calls, and video calls between Onyx users are end-to-end encrypted.
Encryption applies to:
- direct messages
- media attachments
- voice calls
- video calls
- supported group conversations
Fallback routes such as SMS or traditional phone-network calling may not support the same encryption guarantees.
When a conversation falls back to another route, available features and security properties can change depending on the route and recipient capability.
Trusted Reach And Requests
Unknown contacts do not automatically enter the main inbox.
Depending on account relationship and trust state, a conversation can begin as:
- accepted
- request pending
- restricted
- blocked
Request conversations can show:
- sender identity
- mutual context
- trust signals
- contact source
- limited message preview
You can:
- accept
- decline
- block
- report
The request system exists to reduce spam, impersonation, and unwanted reach before the thread enters the primary inbox.
Available Actions And Fallback
Every conversation shows which actions are currently available.
Availability determines:
- which actions are available
- whether rich messaging works
- whether calls are supported
- whether fallback messaging is active
Conversation availability can appear as:
- Onyx-native
- SMS fallback
- phone-call fallback
- degraded
- reconnect required
- disconnected
- migration eligible
Examples:
- an Onyx-native conversation can support encrypted messaging, media, stickers, calls, and actions
- an SMS fallback thread may support text only
- a phone-call fallback may support calling but not attachments
- degraded connections can temporarily disable higher-bandwidth features
Fallback details should only appear when they change what you can do.
Voice And Video Calls
Calls are attached to conversations instead of existing as a separate phone system.
Supported call types can include:
- encrypted voice calls
- encrypted video calls
- phone-network fallback calling
- reconnect calls
- missed calls
Call states can appear as:
- initiating
- ringing
- connecting
- connected
- reconnecting
- degraded
- ended
- missed
- declined
- failed
- cancelled
If internet calling becomes unavailable, the app can offer phone-network fallback where supported.
Communities And Channels
Communities and channels provide larger shared communication spaces inside Onyx Chat.
Communities can include:
- channels
- announcements
- moderated discussions
- member roles
- trusted service spaces
Community features can include:
- owner/admin/moderator roles
- posting permissions
- muted channels
- member restrictions
- pinned announcements
- invite controls
Groups, communities, and channels are treated differently inside the inbox so conversations remain understandable at scale.
Media And Attachments
Supported media can include:
- images
- video
- files
- links
- voice memos
- stickers
Attachment availability depends on:
- conversation availability
- file size
- community permissions
- network conditions
- device capability
Uploads can appear as:
- uploading
- sent
- delivered
- failed
- unavailable
Large uploads or degraded connections can affect delivery timing.
Stickers
The Sticker Engine is part of the communication system.
Sticker support can include:
- system sticker packs
- creator packs
- premium packs
- favorites
- recents
- sticker search
Sticker availability depends on:
- route support
- thread type
- account eligibility
- installed packs
SMS and phone-network fallback routes do not support stickers.
Search And Discovery
Search can include:
- conversations
- contacts
- communities
- channels
- files
- links
- media
- service conversations
Discovery can start from:
- phone contacts
- usernames
- QR codes
- invite links
- communities
- phone numbers
The app evaluates:
- trust state
- relationship state
- communication route
- permissions
before enabling the thread.
Notifications
Notification behavior can include:
- default
- muted
- priority
- digest
Communities and larger channels are designed to reduce notification overload through:
- batching
- mention prioritization
- muted defaults
- role-aware notifications
Notification behavior can vary depending on:
- thread type
- relationship state
- community settings
- device notification permissions
Payments Inside Chat
Some conversations can support payment-linked actions.
Supported actions can include:
- payment requests
- payment confirmations
- service cards
- appointment or status cards
- identity-sharing actions
Payment actions are attached to the conversation and account relationship instead of operating as a separate wallet chat system.
What Can Affect Availability
Chat features can vary depending on:
- communication route
- region
- trust state
- community permissions
- account verification
- number availability
- network conditions
- device capability
Some features may remain unavailable on:
- SMS fallback routes
- phone-call-only routes
- degraded connections
- unsupported regions
- restricted community threads
The app should show unavailable actions before you attempt them.