Telegram problems

Tapping the connect link does nothing

The most common problem, and it is Telegram's behaviour rather than a fault.

Telegram only delivers the connect code the first time you ever start a bot. If you have started the beres bot before — for any organization, at any time — the link opens the chat and sends nothing.

You can tell this is what happened by the bot's reply, which is one of:

Welcome. To link this chat, open your organization's connect page and paste (send) the "/start …" command it shows. (Tapping the link alone won't work if you've started this bot before.)

This chat is already linked. To link it to a different organization, open that org's connect page and paste (send) the "/start …" command it shows — tapping the link won't work once you've started this bot.

The fix: copy the /start … command shown next to the link on the connect page, paste it into the chat, and send it as a message. That always works.

This is why the Channels panel gives your admin both a link and a raw command. If someone reports the link not working, send them the command.

Bot replies and what they mean

"⚠️ That link is invalid or expired — ask your admin for a new connect link."

Connect links are single-use and expire after 24 hours. If someone else already used it, or it's a day old, it's dead. Ask your admin to generate a fresh one.

"⚠️ This chat is already linked to another organization. Ask an admin to unlink it before linking it again."

One Telegram chat can belong to exactly one organization. An admin of the other organization must remove the chat from their linked list first. This catches people who did a trial under one organization and then joined another.

"⚠️ Your organization has reached its limit of N linked Telegram users."

Your plan caps linked chats. Remove one you no longer use under Settings → Channels, or upgrade. See Billing and plans.

"This chat isn't linked to an organization yet. Open your org's connect link first."

Either you were never linked, or an admin removed your chat. Ask for a new connect link.

"Send an order document (PDF or photo)."

You sent text, a sticker, or a contact. Send a file.

"⚠️ That file is too large. Please send a PDF or image under 10 MB."

Re-save the PDF at lower quality, or split it. Photographing pages separately also works, but send each page as its own message.

"⚠️ Unsupported file type. Please send a PDF, PNG, JPEG, or WebP image."

Word, Excel, and HEIC are not supported. Convert to PDF or JPEG.

One quirk: a WebP sent as a file rather than as a photo is sometimes rejected here even though WebP is supported, because Telegram doesn't always say what type it is. Send it as a photo, or convert to PNG.

"⚠️ I couldn't download that file — please send it again."

A transient network blip. Resend.

Posting into a group or channel does nothing

The bot must be messaged in a direct one-to-one chat. Documents posted into a Telegram channel are ignored completely — no reply, no error, no document. Groups need the bot's privacy mode disabled and are not the supported setup.

If a team habitually shares invoices in a group, each person still needs their own direct chat with the bot.

One person works, another doesn't

Each person needs their own connect link and their own linked chat. A link used by one person doesn't cover the rest of the team — it's single-use.

Everyone stopped working at once

If every chat went quiet simultaneously rather than one person's, that is a service-level problem. Contact support and say all channels are affected — that detail points at a different cause than a single broken link.