Sign in

Block sending and inform the operator when telegram does not permit contact

When Telegram refuses a send because the bot is blocked, or cannot yet message the customer, the operator gets a clear, specific explanation instead of a generic failure.

When this happens: Telegram returns 403 Forbidden for a send.

How it works

  • EasyCRM sends a message via sendMessage.
  • EasyCRM returns 403 Forbidden: bot was blocked by the user.
  • Sets Failed. and does not retry automatically.
  • EasyCRM shows in the conversation: This customer has blocked the bot (or hasn't started it) — messages can't be delivered until they message the bot again

Other paths

Bot cannot initiate

EasyCRM returns 403 Forbidden: bot can't initiate conversation with a user for an initiation attempt (UC-19.9 ). Handled identically from step 3.

Good to know

  • A contact-permission failure is recorded with a distinct error code from a transient delivery failure, so the two are never confused in reporting. (FR-19-008, FR-08)
  • A blocked-contact failure is never retried automatically.