---
title: Venom Comms
description: "One API for SMS, WhatsApp, RCS, Telegram and phone calls, through your own provider account, with opt-outs, quiet hours, fallback and spend in one place."
section: comms
order: 0
audience: [user, operator, builder, agent]
sources: [services/nodejs-cloud/lib/comms, services/nodejs-cloud/app/(console)/(shell)/settings/comms, services/nodejs-cloud/migrations/0177_comms.sql, services/nodejs-cloud/migrations/0179_comms_channels.sql, docs/adr/0061-venom-comms.md]
features: [cloud.api-integrations]
---

Venom Comms is how your apps, your agents and the other Venom products reach people: a text, a WhatsApp message, an
RCS or Telegram message, or a phone call that reads something out and listens for a key press. It works the way the
model gateway does for AI. You call one API; Comms picks the provider and the sender, falls back when one fails, keeps
your provider keys in the vault, and records each message and call with its cost beside your model spend.

Nothing is sent until your org adds a provider. Comms uses your own account with that provider (Sinch today), your own
SMS gateway, or the built-in **fake** provider that records sends without sending anything, for trying it out.

- [The API](/docs/comms/api.md): `/v1/comms` for messages, calls, conversations, opt-outs and events, and the `comms_*` MCP tools
  for agents.
- [Providers](/docs/comms/providers.md): set up Sinch step by step, or your own Jasmin or Kannel gateway; the fake provider.
- [Profiles](/docs/comms/profiles.md): routing with fallback, such as "SMS now, a call in 5 minutes unless acknowledged".
- [Compliance](/docs/comms/compliance.md): STOP and opt-outs, quiet hours, sender ids per country, WhatsApp's 24-hour window.
- [Incidents paging](/docs/comms/incidents-paging.md): on-call pages by SMS and phone, and verifying a member's number.
- [Support and People](/docs/comms/support-and-people.md): customers on WhatsApp, SMS, RCS and Telegram in the Support inbox, and capturing people by message.

## Setting it up

Open **Settings, Comms** (`/settings/comms`; admins). From top to bottom:

1. **Providers**: add one (its keys are sealed in the vault and never shown again) and copy the webhook URLs it shows
   into the provider's dashboard. Each provider has a priority; a send tries the lowest number first.
2. **Senders**: the numbers and sender ids messages come from, per channel and country. One can be the default for
   its channels.
3. **Profiles**: the built-in `page`, `support` and `notify`, and your own.
4. **Settings**: quiet hours, the default time zone, the per-minute send limit and the voice calls read in.
5. **Opt-outs**, a **test send** (or a test call), and **Simulate** for the fake provider.
6. **Recent messages and calls** with status and cost. An agent's message or call waits here as *Waiting for
   approval* until someone approves or rejects it.

Comms needs the cloud's vault (`VENOM_VAULT_KEYS`). Without it the page says so and no provider can be added.

## What it costs

Each message and call writes a usage row (model `comms/sms`, `comms/whatsapp`, `comms/voice` and so on), so Admin's
usage and cost pages show it. The cost is an estimate from a default price list (per SMS segment, per WhatsApp, RCS or
Telegram message, per call minute) until your provider reports the exact amount; your provider's invoice is the
authority.

Provider callbacks arrive at `POST /api/integrations/comms/{id}/{token}/{route}`, and a call step in your own TTS voice
is fetched from `GET /api/integrations/comms/{id}/{token}/tts/{call}/{step}`. Both are described in
[Providers](/docs/comms/providers.md).


## In this section {#in-this-section}

- [The Comms API](/docs/comms/api.md): Send messages and place calls with /v1/comms and an org API key; read conversations and events; manage opt-outs; and the comms_* MCP tools for agents.
- [Comms providers](/docs/comms/providers.md): Connect your Sinch account step by step, your own Jasmin or Kannel SMS gateway or a Telegram bot, or try Comms with the fake provider; how callbacks are verified and how fallback works.
- [WhatsApp through Meta's Cloud API](/docs/comms/whatsapp-meta.md): Connect your WhatsApp Business number straight to Meta's Cloud API: paste three values and Venom sets up the webhooks, templates and the Support inbox itself. What Meta requires, what it costs, keeping the number on the WhatsApp Business app, and what agents can do.
- [Keep your number on the WhatsApp Business app (coexistence)](/docs/comms/whatsapp-coexistence.md): Connect with Meta keeps your WhatsApp Business app number on your phone and brings the same chats into Venom: what Meta changes in the app first, what you do on the phone, the 24-hour history and contacts sync, messages you send from the phone, and how to disconnect.
- [Email from your own mailbox](/docs/comms/email.md): Connect a mailbox with an app password so Comms and Outreach send email from you. Venom checks the sign-in and the domain's SPF, DKIM and DMARC, paces sends, reads only reply and bounce headers, and puts a one-click unsubscribe in every email.
- [Telegram from your own account](/docs/comms/telegram-personal.md): Send your approved Outreach messages from your own Telegram account through the Venom daemon on your computer. You log in there, Venom Cloud never holds the login, and the daemon keeps the account under Telegram's limits.
- [Comms profiles](/docs/comms/profiles.md): Routing with fallback for messages and calls: the built-in page, support and notify profiles, your own chains, acknowledgements, and which profiles agents may use.
- [Comms compliance](/docs/comms/compliance.md): What Venom Comms enforces for you (STOP and opt-outs, quiet hours in the recipient's time zone, sender-id rules per country, WhatsApp's 24-hour window) and what stays your responsibility.
- [Incidents paging by SMS and phone](/docs/comms/incidents-paging.md): On-call pages that text each member, call them a few minutes later unless someone acknowledged, read the alert in your org's voice, and take 1 to acknowledge or 2 to escalate.
- [Messaging channels in Support and People](/docs/comms/support-and-people.md): Customers write on WhatsApp, SMS, RCS or Telegram and the conversation lands in Support; you capture people by texting a number or a bot. Routing, the WhatsApp 24-hour window and templates, delivery ticks, files, and what stays private.
- [Venom Line, an AI voice agent on your number](/docs/comms/venom-line.md): Let an AI agent answer live calls on your org's number: set up the media bridge on your own orchestrator, pick the agent's knowledge, tools and voice, run local speech models, and see each call's transcript, ticket and latency afterwards.
