I sent a document and nothing came back
Work through these in order — they're arranged by how common they are.
1. Did the bot reply at all?
No reply whatsoever, not even "📥 Received".
- Is this chat linked? An unlinked chat gets "This chat isn't linked to an organization yet." If you got nothing at all instead, you may be messaging in a Telegram channel rather than a direct chat with the bot. Posting into a channel does nothing — no reply, no error, no document. Open a one-to-one chat with the bot and send it there.
- Did you send a file? Text messages get "Send an order document (PDF or photo)."
- Still nothing? Ask your admin to confirm the chat is still in the linked list under Settings → Channels. A removed chat is silently ignored.
2. You got "📥 Received" and then silence
Silence after that reply is normal. beres confirms receipt once and then says nothing on success — results are read from the Inbox, not the chat. It only messages you again if the document could not be read at all, and only after it has retried.
So "nothing came back" usually means it worked. Check your Inbox in beres:
| What you see | What it means | What to do |
|---|---|---|
| Document shows Failed | The document couldn't be read. You should also have received "⚠️ Sorry — I couldn't read that document" in the chat. | On a paid plan, click Retry next to the document (see below). On Free, send it again — ideally a clearer photo or the original PDF. |
| Still Received or Processing after 10+ minutes | Stuck. It is retried automatically, so give it a little longer. | Still stuck after 30 minutes? Contact support. |
| Document shows Needs review or Blocked | It worked, and a person needs to look at it. | Open it and review it. |
| Document is not there at all | It never got in. Go back to step 1. |
Note the failure message only arrives after beres has exhausted its automatic retries, so it can take a few minutes to show up. Until then, silence is not yet a signal.
Retrying a Failed document
On a paid plan, a Failed document shows a Retry button next to its status in the Documents list. It reads the document again from scratch.
You get two retries per document. After that the button is replaced by an explanation: at that point the problem is almost certainly the document itself, and a third identical attempt would fail the same way. Send a clearer photo or the original PDF instead — that arrives as a new document and has a genuine chance of working.
On the Free plan there is no Retry button. Send the document again through Telegram; the new copy counts against your monthly allowance as normal.
Reading a document costs real processing either way, which is why retries are capped rather than unlimited.
3. Your monthly limit is used up
If you got "⚠️ Your organization has reached its monthly document limit (N/N). Ask your admin to upgrade your plan.", intake is paused until your plan resets or is upgraded.
One thing that surprises people: if a paid subscription lapsed, your organization reverts to the free allowance, which is why this message can arrive far earlier in the month than expected. A warning banner appears at the top of every page when that's the cause. Ask your admin to check Settings → Billing & plan.
4. The file was rejected
These replies are explicit about the cause:
- "⚠️ That file is too large. Please send a PDF or image under 10 MB."
- "⚠️ Unsupported file type. Please send a PDF, PNG, JPEG, or WebP image."
- "⚠️ I couldn't download that file — please send it again." — a transient blip; just resend.
5. Nobody in the whole organization is receiving anything
If every chat stopped working at once, rather than one person's, that is a service-level problem, not a user problem. Contact support and say that all channels are affected — that detail matters and points to a different cause than a single broken link.
What to include when contacting support
- The document id, if the document appears in your Inbox (open it; the id is in the page address).
- Roughly when it was sent, and by whom.
- Whether it affects one person or everyone.
- The exact bot reply, if any.