What you see on the ticket
The images open right in the message bubble, the GIFs play themselves, the stickers are labeled “Sticker.” Video and audio are uploaded by click to avoid pulling heavy files in vain. Documents are displayed with a name, size and download button. Incoming files are not pumped out in advance: only a link to a file in Telegram is saved when you receive it, and bytes are pulled up when the operator opens the attachment. The ceiling for downloading one file: 20 MB. On the channel-account (MTProto), incoming files are not downloaded at all, only the fact of the attachment is recorded.Sending files by the operator
A single file is attached to one response, the text of the message is signed to it, so the delivery remains one atomic call and is safely repeated when a failure occurs. Sending files works on a bot channel. The channel account does not support sending files to the client: the module will fail with an understandable error, the incoming files are visible as usual.Where the bytes lie
The files uploaded by the operators are stored by the module itself, and the method is selected in the Data Storage card:
For the S3, you set the endpoint, the bucket, the region, the path prefix, and a pair of access keys. The keys are saved to the secure storage and not shown back: empty fields when saved again mean “do not change.” The “Check Connection” button writes the test object into the bundle and deletes it, the error returns with the provider’s response.
Switching the method does not carry old files: each file is read from where it was downloaded, you can safely go to S3 and go back without losing anything.
