C!HATTED! conversations with control.
C!HATTED! is the messaging layer of the BRANDED! application family: private conversations, groups, replies, reactions, profiles, translation, attachments, privacy controls, disappearing behavior, custom appearance, website support, and account recovery — presented in one focused communication experience.
Can you send the final version here?
Yes — attaching it now. I also translated the notes inline so nobody has to leave the thread.
Perfect. Keep this conversation pinned.
Be a person, not a phone number.
C!HATTED! is account-based. People can create an identity, sign in, recover access, choose what is public, and find one another by @username. Company-connected users can carry the same identity into BRANDED! without turning every conversation into a corporate interface.
@username discovery
Search for a specific username and open a conversation directly. Private profiles stay protected behind sign-in rules.
Public profile fields
Profiles can expose the information a user intends to share while withholding private account data from other participants.
Password recovery
Verified-email recovery restores access without forcing the user out of the C!HATTED! experience.
Aliases
You can assign your own local alias to a profile so the name shown in your conversation can be more meaningful to you.
Open a participant profile without losing your place.
Profile information can be expanded from inside the conversation, keeping the message context visible and avoiding a disruptive trip to a separate account page.
Your inbox is a workspace.
C!HATTED! treats the conversation list as a control surface. Chats can be pinned, archived, temporarily locked, or permanently exploded. Inside a conversation, the header menu keeps behavioral controls close to the thread without crowding the message area.
Ana Belle • Office
The core actions stay in the conversation controls so they are available on desktop, mobile web, and the Android app without covering the content.
Keep the critical chats visible
Pin up to four conversations so your most important threads stay at the top of the list.
Clear without deleting
Archive removes a conversation from the everyday view while keeping it available for later access.
Temporary controlled access
Lock can restrict a conversation after a short viewing period, adding a deliberate privacy step around sensitive chats.
Delete the conversation everywhere
Explode is the destructive option: the conversation is removed from the account experience across devices and server storage.
Everything important happens inline.
Replies, edits, deletes, reactions, read state, translation, attachments and participant details are built around the message itself. The goal is simple: stay in the conversation and keep context visible.
Reply to a specific message
Reply quoting keeps the referenced message visibly connected to the response. On touch devices, swipe-to-reply provides a faster path into the same behavior.
Edit within 3 minutes
Sent messages can be corrected for three minutes. The conversation clearly marks the result as Edited so the message history stays transparent.
Message actions
Long-press or open the message action row to reach Reply, Delete, additional actions, read state and the Edited indicator when applicable.
Emoji reactions
Add lightweight feedback directly to a message. Reaction summaries are grouped so the thread remains readable instead of becoming a separate activity stream.
Read receipts
When enabled for the conversation, message state can show whether a message has been read while preserving the conversation’s existing visual rhythm.
Search inside the chat
Conversation history search is scoped to the current thread with previous/next navigation, making older messages easier to revisit without global noise.
Reply • Delete • + • Read • Edited
The state and actions a user needs are grouped around the message. The Edited marker only appears when a message has actually been changed.
Shared spaces with clear ownership.
Groups support conversation avatars, editable names, participant management and administrators. Groups are private by default, and public-facing group/profile pages do not expose a member list.
Group avatar & name
Give the conversation a recognizable identity so people can distinguish a project, family, team or support room at a glance.
At least one admin
Group administration is explicit. A group cannot be left without an administrator responsible for participant-level controls.
Participant control
Admins can manage who belongs to the room without turning normal members into account administrators.
Private by default
Public visibility is a deliberate choice. Even when a public page exists, the member list is not exposed to public visitors.
Make C!HATTED! look like yours.
C!HATTED! supports a customizable visual layer: conversation colors, backgrounds and theme settings designed to carry across desktop, mobile web and Android. Individual conversation appearance can distinguish one chat from another without changing what the other participant sees.
Colors
Adjust the visual language of the chat surface while keeping message readability and contrast as the priority.
Background images
Choose image-backed chat surfaces so conversations can feel visually distinct instead of relying only on accent colors.
Per-conversation identity
Individual chat customization gives a specific conversation its own appearance without requiring a global theme change.
Translate without breaking the conversation.
Translation belongs next to the message, not in a separate workflow. C!HATTED! is designed to surface an instant inline translation while preserving the original message and the surrounding conversational context.
The meaning appears where the message already lives.
A user can understand a message in another language without copying it into a separate translator or leaving the chat. The original stays available for comparison.
“Te envío la versión final ahora.”
“I’m sending you the final version now.”
Privacy is a behavior, not a badge.
C!HATTED! combines account security with conversation-level controls: privacy-aware profiles, protected notifications, screenshot restrictions on supported Android contexts, lock behavior, auto-delete and destructive conversation removal.
Screenshot prevention
On supported Android app surfaces, ordinary users are prevented from taking screenshots of protected C!HATTED! content.
Generic background notifications
When content is hidden from the foreground, notifications avoid exposing the message body on the device lock screen or notification shade.
Auto-delete
Conversation-level auto-delete controls allow the chat to remove content according to the chosen disappearing-message behavior.
Lock
Lock adds a timed privacy layer around a conversation and can immediately re-protect the thread when the user exits.
Explode
For the strongest deletion action, explode removes the conversation across the user’s devices and the service-side copy.
Private profiles
Private-profile information is not treated as public directory content. Sign-in and visibility rules apply before details are exposed.
Share more than text.
Attachments live inside the same privacy model as the conversation. C!HATTED! can preserve file context, enforce attachment access, and support forwarding workflows without requiring a separate file-sharing product for normal conversational exchanges.
Attachments
Send files as part of the thread so the discussion and the material stay connected.
Attachment privacy
File access follows conversation/account authorization instead of becoming a permanently public link by default.
Forwarding
Supported messages and attachments can be forwarded through controlled C!HATTED! workflows when sharing is appropriate.
Context preserved
Replies, reactions and message state remain attached to the surrounding conversation rather than being split into separate feeds.
Know something happened. Reveal content only when appropriate.
C!HATTED! notifications are designed to balance immediacy and privacy. Desktop and Android experiences can surface new activity while keeping sensitive background notification content generic.
“New C!HATTED! message” can be enough.
The notification can alert the user without reproducing a private message outside the protected app surface. Opening C!HATTED! restores the full conversation context.
Account recovery stays inside the product.
C!HATTED! supports verified-email account recovery, service email for password reset and invitation flows, and platform-aware install/update prompts so the user can recover or continue on the device they are actually using.
Turn an external website into a C!HATTED! doorway.
C!HATTED! can be embedded as a support experience on another website. A visitor can start a support conversation without signing into C!HATTED!, while the configured recipient answers from the normal C!HATTED! account.
The support widget opens a focused C!HATTED! window while the surrounding website remains visible.
No visitor sign-in required
The website visitor can begin the support exchange directly from the embedded window.
Return link continuity
The support flow can provide a return-to-conversation link so the visitor can resume later instead of starting over.
Recipient uses normal C!HATTED!
The company-side participant answers from their standard C!HATTED! account instead of a disconnected support console.
C!HATTED! stays focused, even inside BRANDED!.
Company users may reach C!HATTED! through the broader BRANDED! system, and certain BRANDED! workflows can produce C!HATTED! conversations or support messages. The overlap is about continuity of identity and communication — not turning every chat into a dashboard.
Shared company identity
A company seat can use the BRANDED! account environment and still communicate through the dedicated C!HATTED! messaging experience.
Support routing
Website support and supported BRANDED! workflows can route communication into C!HATTED! so the recipient handles the conversation in one place.
Service email overlap
Verification, invitations and password recovery can use a BRANDED!-verified mail connection as the C!HATTED! service sender when configured for the account environment.
Company public pages
C!HATTED! can appear as a support or contact channel without exposing internal company chat membership publicly.
Workflow replies
Some BRANDED! modules can initiate or mirror a communication into C!HATTED!, letting the recipient continue the actual conversation in the messaging layer.
Separate mental model
BRANDED! is the broader business environment; C!HATTED! is the conversation environment. The interfaces are intentionally distinct even when the accounts overlap.
Same conversation. Device-aware controls.
C!HATTED! can be used from desktop browsers, an installable desktop/PWA experience, mobile web, and the Android C!HATTED! application. Download and update controls adapt to the platform so users are not offered the wrong client.
Browser access
Use the conversation interface directly from a supported desktop browser.
PWA / standalone
Desktop users can install the application experience and receive a desktop-specific update path.
Responsive interface
Conversation controls, swipe reply and mobile layout behavior are designed for touch-sized screens.
C!HATTED! app
Android users receive Android-oriented install/update prompts and supported device privacy behaviors such as screenshot blocking.
The complete user-facing map.
This table condenses the user-visible C!HATTED! capabilities covered throughout the presentation. Internal oversight is excluded by design.
| Capability | What the user gets | Where it lives |
|---|---|---|
| @username search | Find people and open a chat | Conversation entry / people search |
| Public & private profile rules | Controlled identity visibility | Profile / quick profile |
| Aliases | Your local name for another profile | Participant profile |
| 1:1 conversations | Direct private messaging | Conversation list |
| Groups | Private-by-default multi-person chats | Group conversation |
| Group admins | Participant and group controls | Group settings |
| Reply / swipe reply | Contextual message replies | Message actions / touch gesture |
| Edit for 3 minutes | Correct a recent message | Message actions |
| Edited indicator | Transparent message history | Message metadata |
| Delete | Remove individual messages | Message actions |
| Emoji reactions | Lightweight response without a new message | Message surface |
| Read receipts | Conversation-level read state | Conversation controls |
| History search | Find prior messages in the current chat | Conversation search |
| Attachments | Share files in context | Composer / thread |
| Attachment privacy | Authorized access instead of default public links | File delivery path |
| Forwarding | Controlled message/file forwarding | Message actions |
| Pin | Keep up to four chats prioritized | Conversation list / controls |
| Archive | Hide without deleting | Conversation controls |
| Lock | Timed re-protection of sensitive chat access | Conversation controls |
| Auto-delete | Disappearing-message behavior | Conversation controls |
| Explode | Destructive conversation removal across devices/server | Conversation controls |
| Inline translation | Translated meaning without leaving the thread | Message surface |
| Global appearance | Personalized colors and backgrounds | C!HATTED! settings |
| Per-chat appearance | Different look for individual conversations | Conversation customization |
| Generic background notifications | Activity alerts without message-body exposure | Device notifications |
| Screenshot blocking | Protected Android app content | Android app |
| Password recovery | Verified-email reset | Account access |
| One-time invitations | Service-email onboarding path | Invitation workflow |
| Website support embed | Visitor-to-C!HATTED! support conversation | External website + recipient account |
| Return-to-conversation | Resume an embedded support thread later | Support flow |
| BRANDED! identity overlap | Business account continuity | BRANDED! / C!HATTED! entry points |
| Platform-aware install/update | Right client for desktop or Android | Install controls |
“C!HATTED! is designed so the conversation stays the center of the product.”