Channels
PartialDriving the system from a phone. Telegram and WhatsApp are configured; each is received and answered by the same gateway.
You do not have to be at the machine. An intent can arrive from a messaging app, be handled by an agent, and be answered on the channel it came from.
Who receives and who answers
| Channel | Received by | Answered by | Where it goes today |
|---|---|---|---|
| Telegram | OpenFang | OpenFang | An operations agent in OpenFang — not through the Brain |
| OpenClaw | OpenClaw | The sales station’s own OpenClaw agent; the standalone OpenClaw gateway is configured but not running | |
| Notifications | — | Sent directly by the job runner | Results from the job queue are delivered as messages |
OpenFang has 42 channel adapters in its code, of which one is configured: Telegram. WhatsApp runs through OpenClaw, a separate messaging gateway. Both accept messages only from allowlisted senders.
One system, several front doors
The design is that every channel feeds the same routing and execution path, so a messaging app, the desktop application and voice are interchangeable clients and there is no separate mobile product. Today that is only partly true: Telegram goes straight to an agent rather than through the Brain, and voice is not working.