Chat

In plain words: Reach: Chat family

Partial 1 min read 1 glossary terms 8 connected pages
The short version written for the Snayu team

How Reach represents a chat message for one exact conversation and how Discord, Telegram and WhatsApp Business each build it with their own identifiers and rules.

Why read it: Read this before working on chat message preparation or adding a chat provider.
  1. 1Discord supports bounded channel reads and text sends with mentions suppressed.
  2. 2Telegram supports bot text sends only; there is no per-chat history read.
  3. 3WhatsApp prepares business text candidates; opt-in, service window and spend checks remain for later transport.

Partial Request preparation works; live chat delivery is not implemented.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

Prepare a notice or reply for one conversation. A channel, bot chat and business recipient can share that intent while retaining different audiences, identifiers and access rules.

ChatTarget names the local connection, exact conversation_id and optional reply_to_id. ConnectedPolicy closes the selected account, target allowlist, operation and bounds. A provider user, role or chat ID does not become local authority.

Provider Conversation Prepared operations
Discord Numeric channel under the selected bot connection. Bounded channel-message reads and text sends, with mentions suppressed and exact reply references.
Telegram Numeric chat addressed by the selected bot. Text sends with previews disabled and no markup parser selected. No chat-history read.
WhatsApp Recipient addressed from the selected business phone. Free-form business text candidates. No personal-chat access, history read or automatic template substitution.

A Discord reply fails if its referenced message has disappeared. Its nonce binds the complete preparation: exact retries retain it, while changed text, reply or preparation time changes it. This bounded provider correlation is not a durable delivery guarantee.

Telegram's bot-wide update stream cannot implement a conversation-scoped read. WhatsApp's current service window, recipient permission, opt-out, AI-market eligibility and spend remain prerequisites for later transport, not facts established by constructing a payload.

The existing Discord operator profile keeps its own development scope. Connected preparation supplies the shared serial GraphStep Map and finite WUPHF plan; neither transfers an account's permissions to another conversation.

Reach