Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
FAQ
Tracker Errors
Telegram Errors
Telegram Errors
Error 400 — Telegram
Error 403 — Telegram
FAQs
  1. FAQ
  2. Telegram Errors
  3. Error 403 — Telegram

Error 403 — Telegram

Error code 403 from Telegram means that Telegram does not allow the bot to perform the action. It happens in two common cases: the bot tries to message first in a private chat without an active sessio

Updated September 25, 20263 min
Error code 403 from Telegram means that Telegram does not allow the bot to perform the action. It happens in two common cases: the bot tries to message first in a private chat without an active session, and the recipient's account is deactivated or deleted. These are different causes — the diagnostics and fixes are different too.



Forbidden: Bot can't initiate conversation with a user

The bot cannot message the user first. This is a technical Telegram limitation, protection against spam.
When the bot has permission to message first at all
After the bot accepts a request to join a channel, a 5-minute window opens during which the bot can send any message to the lead. After that, an incoming message from the lead is required (or a tap on an inline button of type keyboard) so the bot can message again. Without this, Telegram returns 403.

How to fix it

If the error occurs on Push Messages, the lead has been silent for more than 5 minutes after the subscription event. Move the Push to a point when the lead has already written something to the bot, or disable it for the specific funnel.
If you use the Invite + DM setup (accepting the request + a separate bot for communication), the DM bot needs incoming contact. Make sure the first step in the funnel is an action that prompts the lead to write (Send Message with an inline button of type keyboard, or an explicit CTA “tap the button to continue”). More details — Invite + DM — Hybrid Scenario.
For mailings to an old lead base via How Mass Broadcasts Work — Telegram will let the message through only to leads who have an active dialog with the bot. For leads without a dialog, Mailings will return 403 — this is normal.



Forbidden: user is deactivated

The recipient's Telegram account is deactivated, deleted, or blocked on Telegram's side. For the bot, it no longer exists — sending any message returns 403.
Sometimes this restriction applies only to one session or to a couple of chats, not to the entire account — Telegram uses different levels of blocks. In this situation, some messages go through, while others return 403 on the same bot.

What to do

There is nothing to fix — the lead is unavailable. In Messenger set their Status = Blocked or Stopped so the bot does not try to send them messages again.
If 403 deactivated occurs in bulk (several percent of leads in a campaign), this is normal. Part of the audience always leaves Telegram between subscribing and the actual touchpoint. Account for this in the funnel: Push Messages — Re-engaging Silent Users with a long delay usually produces more 403s than with a short one.
If 403 deactivated occurs for a lead you are having a dialog with right now, it may be a temporary restriction on a specific session. Wait 1–2 hours and try again.
Preventing 403 in a funnel
Build the flow so that the first message is sent immediately after the event (Subscribe / Contact). Do not set Delay > 5 minutes before the first touch. If you need a long pause, use a button of type keyboard in the first message: the lead will tap it, the communication window will “reset”, and the next step will be able to send even a day later.



FAQ

From the Telegram event about joining a channel (chat_member) that the Invite bot receives. From that moment, any bot that has permission to write in this chat has a 5-minute window for the first message.

Buttons of type keyboard (at the bottom of the screen) — the lead's tap is counted as an incoming message, and the communication window reopens. Buttons inline with callback — no, they do not reset the 5-minute timer. If the goal is to extend communication, use keyboard. More details — Send message — sending a prepared message.

There may be two reasons: (1) the lead has multiple Telegram sessions, and one of them is temporarily blocked by Telegram — messages are delivered to some of the devices. (2) the lead deleted and restored their account — the old link to user_id is no longer valid.

Reduce the delay before the first push. If you plan to send a message after a day or more, add an intermediate step with an inline keyboard button (“Learn more”) that opens the chat window. After the lead clicks it, the next push will be sent without a 403. See Push Messages — Re-engaging Silent Users.

In Messenger each chat has a status — a lead with a 403 will automatically get Status = Blocked or Status = Error. In User filtering — 11 parameters you can filter out these leads and exclude them from subsequent broadcasts.



Related

Error 400 — Telegram
Error code 400 from Telegram occurs in two typical cases: an account spam block (PEER_FLOOD) and exceeding the media caption length limit (caption is too long). These are different errors with the sam
Push Messages — Re-engaging Silent Users
Push messages are delayed messages that are sent if a lead does not respond at the current step. This is a nurturing tool: the first reminder after 10 minutes, the second after an hour, the third the
недоступна
Invite + DM — Hybrid Scenario
The hybrid “Invite + DM” scenario is a classic traffic arbitrage setup. The user clicks an ad, lands on a landing page, goes to a bait Telegram channel, submits a join request, Invite Bot approves it,
Chat Status — conversation statuses
Status is the main technical parameter of a conversation. It shows the current state of the chat and determines: who responds to the user — AI or an operator whether Push Messages (Global/Step push) a

Was this article helpful?

BackError 400 — Telegram

On this page

  • Forbidden: Bot can't initiate conversation with a user
  • How to fix it
  • Forbidden: user is deactivated
  • What to do
  • FAQ
  • Related