Direct messages

Messages from people who agreed to hear from you.

The inbox is only worth opening if getting into it took something.

Live on Google Play · Android only
CHiiRO / message

The gate is the feature

Friction in precisely the right place.

On most professional networks anyone can message anyone, which sounds like openness and functions as a tax. The result is an inbox where the ratio of pitch to conversation is so bad that people stop opening it, and the genuinely useful message — the one from someone who read your profile and has the exact answer — dies in a pile of templated outreach. CHiiRO puts a gate in front: you can message someone once they have accepted your connection request. It is a small amount of friction in precisely the right place, and it is why a CHiiRO message is worth reading.

What it's built on

An open protocol, not a black box.

Direct messages run on an open messaging protocol rather than a proprietary black box, with real-time delivery, typing indicators and read receipts. That choice matters for a reason that has nothing to do with features: an open protocol is inspectable, and it means the messaging layer is a standard piece of infrastructure with a public specification rather than something we ask you to take on faith.

Not end-to-end encrypted. Said plainly.

Messages are not end-to-end encrypted. The operator can read message content on the server. We are telling you this plainly on a marketing page because the alternative — writing "secure messaging" and letting you assume the stronger thing — is the sentence that everybody else writes and that we won't. If end-to-end encryption is a requirement for the conversation you're about to have, have it somewhere else, and read our security page first to know exactly where every line is drawn.

Real-TimeTyping IndicatorsRead ReceiptsOpen ProtocolConnection GateNo TemplatesNo SequencesNo Bulk SendReal-TimeTyping IndicatorsRead ReceiptsOpen ProtocolConnection GateNo TemplatesNo SequencesNo Bulk Send

Starting a conversation

From a person, not from a compose screen.

A conversation starts from a person — their profile, or your connections list — not from a blank compose screen. You find the person, you connect, they accept, you write. That ordering is deliberate: it means every conversation begins with a reason, and the reason is visible to both people before the first message. Conversations sync across the app in real time, and the messages list stays usable even when the real-time layer is having a bad day.

What we're not building

No sequences. No templates. No bulk send.

No read-receipt-driven follow-up nudges. No "your message was seen 3 days ago, try again" prompts. No sequences, no templates, no bulk send, no CRM integration that turns members into a list. The product decision here is simple and permanent: CHiiRO's messaging is for conversations, and every feature that makes outreach cheaper at scale makes the inbox worse for everyone in it.

What you get

01

Open your inbox knowing everything in it came from someone you agreed to hear from.

02

Reach the person who can actually answer, without your message competing with fifty pitches.

03

Know exactly what is and isn't protected, instead of trusting an adjective.

04

Never receive a templated sequence, because the product makes sending one impossible.

Questions and answers

Q.Can anyone message me on CHiiRO?

No. Direct messaging is limited to people whose connection request you accepted, or whose request you sent and they accepted. Someone who is not a connection cannot open a conversation with you, which is deliberate and is what keeps the inbox usable.

Q.Are CHiiRO messages end-to-end encrypted?

No. Messages are not end-to-end encrypted, and the operator can read message content on the server. CHiiRO states this plainly rather than using the phrase "secure messaging", which most people read as end-to-end encryption.

Q.What is CHiiRO messaging built on?

An open, standardised messaging protocol rather than a proprietary system, with real-time delivery, typing indicators and read receipts. Using a public specification means the messaging layer is inspectable infrastructure rather than something members are asked to take on trust.

Q.How do I start a conversation on CHiiRO?

From a person — their profile or your connections list. Send a connection request; once it is accepted, you can message. There is no blank compose screen that lets you pick any member, because messaging is gated on an accepted connection.

Q.Why does CHiiRO limit who can message you?

Because an inbox anyone can reach becomes an inbox nobody opens. Requiring an accepted connection puts a small amount of friction in front of outreach and none in front of conversation, which is the trade that keeps a genuinely useful message from being buried.

Live on Google Play

Install CHiiRO on Google Play