← Writing

June 2026

Chert Biztext - spam that people want

Biztext is the business messaging protocol that proactively delivers spam people want. It does this through a single intermediary agent that has context on both the customer and the business and can message across multiple protocols (sms/rcs, imsg, email, etc)

Business messaging currently faces three main problems:
1. It is fragmented. Consumers have to subscribe to a separate 'spam' pipeline for every new business they encounter. It is difficult to keep track of all of them, especially when many can't even share content. This erodes trust and visibility.
2. It lacks consumer context. Static promotional messages don't know what the consumer actually wants. None of the messages are personalized, and they all feel transactional.
3. The protocol is bad. Email and sms/rcs are NOT where the consumer would regularly check their messages. For business messaging to work, it needs to meet the consumer where they already are.

All of this directly impacts visibility and response rate, which explains why spam is spam and why it doesn't work very well right now.

Biztext solves this in a few ways:
1. There is one single contact that the consumer texts and receives notifications from for every business. This is much easier to keep track of.
2. It is personalized for the user. The agent has full context on the user's needs and can therefore deliver only messages relevant to the consumer and in the manner the consumer expects. It is also easier for the businesses - they no longer have to worry about delivery. They can just push out the information and the agent will make the selection.
3. The protocol uses whatever the consumer is already most comfortable with. When onboarding, the consumer selects the interface through which to communicate with the agent. After that, the agent will communicate promotions from that business only via that protocol.

On a grander level, this is a first step towards the future of messaging protocol, where messages are no longer just delivered through sms/imsg/email but instead through an intermediary agent that personalizes messaging, interface, and protocol for both sides depending on context. This is not just a interface change like an email client, since this happens on the delivery layer that affects both sides.

Maybe a HN or Bookface launch to get more opinions. Could be interesting!

Comments (1)

  • GaryJun 27, 2026

    Come to think about it, this also changes the identity layer as well. While messaging does stay tied to existing identities in the form of phone numbers, emails, IDs, etc, the agent itself becomes the defacto identity of the business, and the 'identities' mentioned above simply become transports in the protocol layer. Functionally, the agent, with its dynamic/auto-subscription of channels, becomes the true identity of the business.