Choosing a channel
Web3 runs on three channels and they are not interchangeable. Which one you pick changes whether your message is read, and it should be decided per contact rather than per campaign.
The short answer
| Channel | Coverage | How reliable the field is | Default use |
|---|---|---|---|
| X (Twitter) | 98.9% | Self-supplied by the person and confirmed to resolve to a live public profile during enrichment | Your default. Nearly everyone has one and it is right. |
| 70.4% | Self-supplied. Not cross-checked against the person's name. | Formal asks, enterprise buyers, anyone whose X is personal rather than professional. | |
| Telegram | 31.5% | Inferred from a username match. About 6% of checkable matches are the wrong person. | Best response rates in Web3 when correct. Verify before using. |
99.5% of contacts are reachable on at least one of these; 83.2% on two or more, which means you usually have a fallback.
Why X is the default
Not because it is the best place to have a conversation — Telegram usually is — but because it is the field you can trust. It is present on 98.9% of records, it was supplied by the person themselves, and enrichment confirmed the profile exists and is live. Nothing else in the dataset has all three properties.
It also carries something the other channels do not: the bio. You get a public, current-ish statement of what the person does, which is the raw material for a first line that does not read like a template. That is worth more than the marginal open rate of a different inbox.
The weakness is that DMs from strangers are frequently unread, and a closed DM setting means no delivery at all. Which is why the second channel matters.
When LinkedIn beats X
Use LinkedIn when the ask is formal, when the company is enterprise rather than crypto-native, or when the person's X bio reads personal rather than professional.
A person whose X bio is memes and market takes and whose LinkedIn says Director of Partnerships is telling you which account is for work. Believe the bio.
LinkedIn also has the useful property that a connection request with a note is a low-cost, socially normal opener in enterprise contexts where an unsolicited DM is not. The trade-off is speed: replies take days rather than hours.
Coverage is 70.4%, so roughly three in ten contacts will not have this option.
When Telegram is worth the extra work
Telegram is where Web3 business development actually happens. It is where deals get discussed, where introductions get made, and where people answer quickly. If you can reach the right person there, it is the strongest channel of the three.
The catch is the word right. These handles are inferred from a username match rather than confirmed, so a Telegram-first strategy on unverified handles means a small but real share of your outreach lands on strangers.
Our recommendation is specific: use Telegram for contacts where the handle carries independent supporting evidence, and X for everyone else. That subset is smaller than the 31.5% headline, but it is the portion where the channel's advantage is real rather than theoretical. The verification guide is a thirty-second check.
A decision you can run down a column
- Does the X bio publish a Telegram handle — a
t.melink or a stated@handle? Use that. It is self-declared and it is the best evidence available. - Does the Telegram profile share a distinctive detail with the X bio — same employer, same project, same full name? Use Telegram.
- Is the ask formal, or is the company enterprise-shaped, and is LinkedIn present? Use LinkedIn.
- Otherwise — use X. It applies to nearly everyone and it is the field least likely to be wrong.
Multi-channel, and how to do it without being a nuisance
83.2% of contacts are reachable two ways, which tempts people into sending the same message twice. Don't — the recipient sees both, and it reads as automation.
If you follow up on a second channel after silence, acknowledge it and make the second message shorter than the first. "Tried X last week, thought I'd try here" is honest and costs nothing. The version that damages you is the identical paragraph arriving in two inboxes.
What the channel does not fix
Channel choice is a second-order decision. A specific, short, well-aimed message on the wrong channel outperforms a generic one on the right channel, every time. If your outreach is not getting replies, the message is the more likely cause than the inbox — the quickstart covers how to structure it.
What we don't know
We publish coverage and field reliability because we measure those directly. We do not publish per-channel response rates, because we would be extrapolating from our own outbound to your offer and audience, and that number would not survive contact with your use case. Anyone quoting you a Web3 cold-outreach response rate as a general fact is quoting a number they cannot substantiate.