Channels
Messages from connected platforms run the same permissioned Friday agent turn, then return to the conversation and thread where the request started.
Each supported channel keeps its own token, sender rules, reply model, and destination while sharing Friday's core agent flow.
Chat with Friday from Telegram using a bot connection. Messages run an agent turn and replies are delivered back to the same chat or thread.
Chat with Friday from a Discord server or direct message. Messages run an agent turn and replies are routed back to the originating channel or thread.
Planned adapters follow the same identity, access-policy, thread-routing, and provider boundaries as supported channels.
Planned workspace channel for team conversations, approvals, and assistant delivery back to the original Slack thread.
Planned mobile messaging channel for personal check-ins, quick requests, and assistant replies.
Planned asynchronous channel for brief requests, daily summaries, and follow-up workflows.
A channel request crosses explicit admission and dispatch boundaries before Friday sends anything back.
Receives the platform event and emits a channel inbound message.
Evaluates access policy and decides whether to dispatch, handle, observe, or drop the message.
Allowed messages reach the same permissioned agent flow used by the desktop chat.
The result routes back through the adapter to the original conversation and thread.
Channel access
Use allowlists, pairing, open, or deny policies so you decide who can message Friday from outside the app.