Problem
When an agent replies with NO_REPLY, the message is briefly sent to Telegram and then deleted. Users see the message flash momentarily before it disappears — creating an awkward "opened mouth then closed it" effect.
Expected Behavior
NO_REPLY responses should be intercepted before being sent to the channel, so no message is ever published or deleted. The user should see nothing at all.
Current Behavior
- Agent responds with
NO_REPLY
- Message is sent to Telegram
- Gateway detects
NO_REPLY and deletes the message
- Users see the message appear and disappear (split-second flash)
Suggestion
Intercept NO_REPLY in the gateway layer before it reaches the Telegram Bot API send call, rather than sending and then deleting after the fact.
Context
This is especially noticeable in group chats where the agent correctly stays silent but the flash makes it look like a deleted message, which can be confusing or distracting to other participants.
Problem
When an agent replies with
NO_REPLY, the message is briefly sent to Telegram and then deleted. Users see the message flash momentarily before it disappears — creating an awkward "opened mouth then closed it" effect.Expected Behavior
NO_REPLYresponses should be intercepted before being sent to the channel, so no message is ever published or deleted. The user should see nothing at all.Current Behavior
NO_REPLYNO_REPLYand deletes the messageSuggestion
Intercept
NO_REPLYin the gateway layer before it reaches the Telegram Bot API send call, rather than sending and then deleting after the fact.Context
This is especially noticeable in group chats where the agent correctly stays silent but the flash makes it look like a deleted message, which can be confusing or distracting to other participants.