Home / Guides

Forwarding Incoming SMS to a Telegram Chat or a Webhook

Updated

When one person uses a phone number, incoming messages land in one place. Teams work differently: a code sent to a project number may need to reach several people, or to be pushed into a system that records it. Forwarding handles this. Instead of checking a phone or a bot by hand, you route incoming SMS to a Telegram chat where the team can read it, or to a webhook that feeds a script, a ticket system or an internal dashboard. This guide covers both routes, what each one is good for, and what to check before you rent a number.

Why forward incoming SMS

A number that only one person can read is a single point of failure. Codes arrive while that person is asleep, in a meeting, or away from the device. In a team, the person who needs the code is often not the person who holds the number.

Forwarding moves the message to a place the team already watches. Two routes cover most cases: a Telegram chat, where people read the text as it arrives, and a webhook, where a server receives the message and acts on it.

Whatever route you pick, the forwarded payload usually carries the same core fields.

  • The sender or the number the message came from
  • The message text, including any code
  • The time the message arrived
  • Which of your numbers received it

Forwarding to a Telegram chat

This route fits teams that already work in Telegram. The message is posted into a group or channel, so anyone with access can read it and act without leaving the app.

If you manage your number in the SMS Activate App Telegram bot, the forwarding target is set in the number settings alongside the other options.

  • Create or pick the chat that should receive the messages
  • Add the bot that manages your number to that chat
  • Open the number settings and set the forwarding target to that chat
  • Send a test message to the number and confirm it appears in the chat
  • Pin the chat or mute the rest so new codes are noticed

Forwarding to a webhook

A webhook is an HTTP endpoint on a server you control. When a message reaches your number, the bot sends a request to that URL with the message data, and your code decides what happens next.

This route fits teams that need records, search, or alerts outside Telegram. It also lets one number feed several systems without anyone copying codes by hand.

Handle the payload defensively, since a code is a credential for a short period.

  • Accept a POST request and read the message fields
  • Answer with a success status so the caller knows the payload was received
  • Route the content to a ticket system, a sheet, a dashboard, or an alert
  • Add a secret token to the URL or the headers so only your bot can call it
  • Use HTTPS and avoid writing full message bodies to shared logs
  • Delete stored codes once they are no longer needed

Chat, webhook, or both

Pick a chat when the workflow is human: someone reads the code and types it into a form. Pick a webhook when the workflow is automated: a script needs the code, or the team needs a searchable log.

Both can work together. A webhook can repost the message into any number of chats, which covers the case where several groups need the same code. That adds a small server to maintain, so use it only when a single chat is not enough.

A few practical questions help you decide.

  • Volume: a few messages a week suit a chat, a steady stream suits a webhook
  • Audience: people in Telegram read a chat, other systems need a webhook
  • Retention: chat history is casual, a webhook writes to storage you control
  • Effort: a chat takes minutes, a webhook needs a server and code

Checks before you rent a number

Forwarding only routes messages. It does not change how a platform treats a number, and it does not promise that any platform will accept it. Confirm the number fits the platform you plan to use before you pay.

The service we recommend is SMS Activate App (sms-activate.app, also available as a Telegram bot). It rents private, not shared, phone numbers for 28 days, with automatic renewal every 28 days while your balance covers it. Renewal can be switched off. Prices start from $8 per 28 days, and numbers are currently available in Australia, Canada, United Kingdom, Israel, Puerto Rico, Sweden, and United States. A number receives SMS and calls, and you manage it on the website or in Telegram. Balance top-up works by bank card or cryptocurrency. Incoming SMS can be forwarded to a Telegram chat or a webhook, which is the setup this guide describes.

The rental fee is non-refundable, so test the number against your platform first. Also plan for the end of a project: switch renewal off so the balance is not spent on a number you no longer need.

Forwarding turns a private number into a shared resource: a Telegram chat for people, a webhook for systems. Choose the route that matches how your team works, and check the number against your platform before you rent it.

Open SMS Activate Appsms-activate.app

Frequently asked questions

Can I send the same message to several chats?

A number has one forwarding target in its settings. If several groups need the same message, point the forwarding at a webhook that reposts the text to each group, or use a single chat that includes everyone who needs the code.

Are forwarded messages safe to post in a group?

Treat a verification code as a credential. Keep the target chat small, remove members who leave the project, and avoid wide audiences. On the webhook side, use HTTPS and a secret token, and delete stored codes after use.

Does forwarding change whether a platform accepts my number?

No. Forwarding only decides where the message is delivered. Acceptance depends on the platform and its rules, so test the number with your platform before you rely on it. The rental fee is non-refundable.

More guides