# Telegram and WhatsApp

Set up messaging Lines, distinguish them from workflow action connections, and verify delivery with a real conversation.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active Lines | 2 | 5 | 15 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## Set up a Telegram Line

Create or select the Telegram bot you want people to contact. In Chatigram, create a Telegram Line and complete the protected setup. After saving, check the Line’s connection state and any remaining instructions.

Assign an enabled conversation workflow. Open the bot as a customer, start a fresh conversation, and send a message. For a team-supported Line, check both Telegram and your Chatigram Inbox. With [Private AI mode](/channels/private-ai/) enabled, conversations stay out of Inbox and human agents cannot view or reply.

For BotFather setup, multiple bot connections, and Member replies, follow [Telegram bots for support and automation](/channels/telegram-bots/). For the prepared group-automation setup, use [the official Telegram Group Manager](/recipes/telegram-group-manager/).

> A bot connected elsewhere may have a competing message-delivery configuration. If messages stop arriving, check which application is currently receiving them before reconnecting.

## Set up a WhatsApp Line

Choose WhatsApp when creating a Line and complete the business connection setup shown in the application. Provider requirements and messaging restrictions depend on your WhatsApp business configuration.

Test inbound and outbound behavior with an appropriate test recipient. An account connection alone does not verify that the intended business number can receive customer messages or send the response your workflow expects.

## Line messages or app actions?

Use **Send Text Message**, **Send Image Message**, and **Send File Message** when replying in the current Chatigram conversation. These nodes rely on that conversation’s context.

Use Telegram or Meta integration actions when your workflow needs a provider-specific action, such as working with a group or an identified external resource. Select a compatible App Connection in that action’s inspector.

## Handle attachments

Configure **Receive Message** for the message types you expect: text, audio, image, video, or file. Its branches depend on the selected types. Use the attachment’s Message ID with the relevant processing node; do not assume every incoming attachment is text.

Read [images and audio](/ai/images-audio/) for a complete processing path and fallback guidance.

## Delivery checks

If a message is missing, confirm the Line connection, recipient or chat, provider permissions, workflow trigger, and assignment. Check whether the provider rejected the request or the workflow is waiting for another message. Inspect the destination before retrying a send.