ONYX
Docs

Onyx Chat

Use account-linked conversations where chat is available.

Onyx Chat gives you one unified inbox for messages, calls, groups, communities, service conversations, and fallback communication.

Message another Onyx user with end-to-end encrypted text, media, voice calls, and video calls. When you need to reach someone outside Onyx, SMS or phone-call fallback keeps the conversation useful with the actions that communication type supports.

The goal is simple: you should be able to reach the person, group, community, or service you need without rebuilding the conversation in another app.

Unified inbox

Conversation preview

Select a thread to see available actions, delivery status, encryption notes, and fallback behavior.

Maya Chen

End-to-end encrypted

Delivered

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.

Unified Inbox

Onyx Chat keeps personal conversations, group threads, community spaces, service conversations, and requests in one place.

Each conversation stays tied to the thread, participants, and permissions. If a contact changes devices, joins Onyx later, adds a number, or moves through changing network conditions, the conversation can continue from the thread that already holds the context.

The inbox separates direct messages, groups, communities, and service conversations so large spaces do not drown out personal communication.

Direct And Group Conversations

Direct conversations help you reach one person through your Onyx identity, number, or approved contact path.

Group conversations let multiple people share messages, media, files, calls, payment-linked actions, and conversation updates. Supported Onyx-native conversations use end-to-end encryption for messages, media, voice calls, and video calls.

Some people may only be reachable through SMS or phone calling. In those cases, the conversation can continue with the actions supported by fallback communication.

Calls

Onyx Chat treats calls as part of the conversation.

You can use encrypted voice and video calls with supported Onyx contacts. If internet calling is unavailable and phone calling is supported, the conversation can use phone-network fallback instead.

Call history, missed calls, reconnect attempts, and call outcomes stay attached to the thread so the conversation remains understandable.

Fallback Communication

Fallback communication keeps reach from becoming an all-or-nothing choice.

An Onyx-native conversation can support encrypted messaging, media, stickers, calls, and richer actions. SMS fallback may support text only. Phone-call fallback supports calling but not attachments. Degraded network conditions can temporarily limit larger uploads or video calling.

Onyx Chat uses plain delivery status and available actions to help you understand what you can do next.

Trusted Reach And Requests

Unknown contacts do not automatically enter the main inbox.

A new conversation can arrive as an accepted thread, a request, a restricted conversation, or a blocked contact based on contact context, trust signals, and account settings.

Requests show sender identity, mutual context, contact source, and a limited preview. You can accept, decline, block, or report the request before it enters your primary inbox.

This protects communication without forcing every conversation into a public profile or open messaging model.

Media And Attachments

Onyx Chat supports text, images, video, files, voice memos, stickers, payment requests, service cards, call events, and system messages.

Availability depends on the conversation type, fallback communication, file size, community permissions, network conditions, and device capability. Large uploads can take longer when network conditions change.

Stickers work in supported Onyx-native conversations. SMS and phone-call fallback do not support stickers.

Search And Discovery

Search helps you find conversations, contacts, communities, channels, files, links, media, and service conversations.

Discovery starts from contacts, usernames, QR codes, invite links, communities, or phone numbers. Onyx evaluates contact context, trust state, and permissions before enabling a new conversation.

Notifications

Onyx Chat supports default, muted, priority, and digest-style notification behavior.

Communities and larger channels can reduce noise with muted defaults, batched delivery, mention prioritization, announcement priority, and role-aware notifications.

You control which conversations deserve immediate attention and which can wait.

Payments Inside Chat

Some conversations support payment-linked actions such as payment requests, payment confirmations, service cards, appointment cards, status cards, or identity-sharing actions.

Payment actions stay connected to the conversation context. Eligibility, verification, country support, and account state affect which actions are available.

What Can Vary

Chat capability varies by conversation type, fallback communication, country, trust state, community permissions, verification state, number support, network conditions, and device capability.

Those limits should only matter when they change what you can do. The product should keep the conversation understandable and make the next available action clear.