---
title: Messaging channels in Support and People
description: "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."
section: comms
order: 50
audience: [user, operator]
sources: [services/nodejs-cloud/lib/support/comms.ts, services/nodejs-cloud/lib/people/comms.ts, services/nodejs-cloud/lib/comms/routes.ts, services/nodejs-cloud/lib/comms/telegram.ts, services/nodejs-cloud/lib/comms/service.ts, services/nodejs-cloud/components/support/Settings.tsx, services/nodejs-cloud/migrations/0179_comms_channels.sql, docs/adr/0061-venom-comms.md]
features: [cloud.page-support]
---

Support and People are the first products that **listen** through Comms. They never talk to a provider: a message
arrives at one of your Comms senders, Comms hands it to the product that sender feeds, and the product answers through
Comms on the same channel. Everything that applies to Comms (your provider account, opt-outs, quiet hours, the
per-minute limit, spend beside your model spend) applies to these messages too.

## Point a number at a product

Open **Support, Settings, Messaging channels** (admins). Every sender you added in
[Settings, Comms](/docs/comms.md#setting-it-up) is listed with a choice:

| Choice | What a message to this sender does |
|---|---|
| **Support inbox** | opens or continues a Support conversation for the person who wrote. An optional **inbox tag** is put on every conversation this number opens, so you can tell the WhatsApp line from the SMS line. |
| **People capture** | is read as something to save to [People](/docs/cloud/people-capture.md): a contact, a card photo, a voice note or a line about someone you met. |
| **Nothing** | feeds no product. The event still reaches the event feed and your webhooks. |

A sender feeds one product. Until an admin routes it, nothing is opened, so adding a provider never fills the inbox by
surprise. A reply to a page ("reply 1 to acknowledge", [Incidents paging](/docs/comms/incidents-paging.md)) and STOP or START
always go to Comms first and never to a product.

## Support

**In.** The first message from a number opens a conversation with the channel, the number and your inbox tag. The
customer is found again by their number (or their Telegram chat), never by anything the message says, so the next
message joins the same conversation while they keep talking (14 days after the last, a new one opens). It reopens a
closed conversation and shows the channel next to each message. A customer whose number is on an **org-shared** person
in [People](/docs/cloud/people.md) is linked to that person. Private and team-only people are never read.

**Files.** Photos, voice notes and documents are kept in your organisation's files and shown in the thread: images
inline, voice notes with a player, everything else as a download (never rendered). Up to three files of 4 MB each per
message; one that cannot be read is listed as not kept, with the reason.

**Out.** The composer answers on the channel the customer last wrote on, from the number they wrote to. A reply you
draft with AI and send, a saved reply, and a message typed by hand all go the same way. Each reply carries **ticks**
that follow the provider's reports: *sending*, *sent*, *delivered*, *read*, or *not sent* with the reason. A reply
inside a conversation the customer started is not held for quiet hours.

**WhatsApp outside the 24-hour window.** Meta allows free-form text only within 24 hours of the customer's last message.
After that the composer shows what is possible:

1. an **approved template**: pick one, fill its parameters, and the reply stays on WhatsApp;
2. otherwise, if your **support profile** (Settings, Comms, Profiles; the built-in one is "WhatsApp, then SMS") has an
   SMS step and the customer has a number, free text goes by **SMS** and the thread gets a note saying so;
3. with neither, the reply is refused in words (409 `template_required`) and nothing is saved.

A WhatsApp send that fails for good also falls back to SMS through the same profile, with the same note.

**Templates** are listed from your provider (Sinch's Template API) with their approval state. **Sync from provider** in
the settings reads them again; only `approved` ones can be sent. `GET /v1/comms/templates` and
`POST /v1/comms/templates/sync` do the same for your apps, and agents read them with `comms_template_list`.

A customer who replied STOP is never messaged: the reply is saved as not sent with that reason.

## Known people and deals

When the customer is an org-shared person, each message they send is also logged for you:

- on the **person's timeline** as a message on the channel (kind *message*, direction in), by "Venom Comms";
- on each **open deal** they are on in [Funnel](/docs/cloud/funnel.md), as a message activity (lost and won deals are left
  alone).

A message from someone who is only a **private** person of a member is never written to that person or to any deal.

## People capture by message

Text or WhatsApp your **capture number** the way you would use the [Telegram bot](/docs/cloud/people-telegram.md): a shared
contact, a `.vcf` file, a photo of a business card or a screenshot, a voice note, or a line such as "met Sarah from Acme,
wants GPU pricing". It goes through the same capture steps as the app and answers with one short confirmation and a link
to each person. `/event` and `/help` work too.

Only **linked** numbers are listened to. On **People, Telegram** (`/people/telegram`), section 3, press **Link this
number**, then send the code to the capture number from your phone (once, within 15 minutes). A member's own verified
phone from [Incidents paging](/docs/comms/incidents-paging.md) also counts. A stranger who writes to the capture number is told how
to link, at most once every ten minutes, and nothing is saved. What you capture is saved as **yours**, private like
everything you add in the app: other members and other organisations never see it.

## Telegram

A Telegram bot is a Comms provider like any other: **Settings, Comms, Add a provider, Telegram bot**, paste the token
from @BotFather, and Venom checks it, registers the webhook and adds the bot as a sender. Route it to Support to answer
customers there, or to People to capture.

**People's existing bot** moved onto Comms without changing anything for you: the token stays sealed where it was, the
webhook address stays the same, and every linked chat keeps working. A bot connected before this change is added to
Comms the first time it receives a message. Disconnecting the bot in People removes its Comms provider as well.

## WhatsApp through Meta

With WhatsApp connected through [Meta's Cloud API](/docs/comms/whatsapp-meta.md), the inbox adds: **Attach** (one file per reply,
up to 2.5 MB, uploaded to Meta), a row of emoji, blue ticks when you open a thread, messages you send from the
WhatsApp Business app on your phone shown in the thread (coexistence), **Add to People** for a customer nobody knows
yet, a green dot on a conversation whose customer wrote last, and a push to the assignee's phone for each new message.
The list refreshes every 10 seconds and the open thread every 5.

## What is not here yet

- Files you attach to a reply on Sinch, SMS or Telegram (only text and templates go out there; WhatsApp through Meta
  takes files).
- A pool of several numbers per country with rotation: a sender can be bound to countries, and Comms picks the one that
  serves the customer's country, but each country still uses one number.
- Sinch's SMS-only API as a second Sinch variant; SMS goes through the Conversation API.

See also: [Venom Comms](/docs/comms.md), [Profiles](/docs/comms/profiles.md), [Compliance](/docs/comms/compliance.md), [Support](/docs/cloud/support.md).
