Back to Docs
File Understanding

Let your agent read the files your customers send

Images, voice notes, videos, PDFs, spreadsheets — when a customer drops a file into the chat, your agent can read it and answer questions about its content.

TL;DR

  1. Nothing to set up. Every agent reads the files your customers send.
  2. Each file stays readable for 28 days after it arrives.
  3. Open the file in any chat to see what the AI understood, and fix it if needed.

A file is processed only when a customer actually sends one — there's no standby cost.

1What it does

When a customer sends a file, your agent receives the attachment and the platform extracts a representation it can read:

Documents

PDF, DOCX, RTF, TXT, Markdown

Full text extraction. Tables and paragraphs preserved.

Spreadsheets & structured

CSV, TSV, XLSX, JSON, XML

Row-by-row flattened so the agent can answer questions like 'what's the price of model X?'.

Images

JPG, PNG, GIF, WEBP

AI vision describes what's in the picture and suggests how it might be useful in the conversation.

Audio

MP3, M4A, WAV, OGG

Transcribed end to end. The agent reads the transcript, not the audio.

Video

MP4, MOV, WEBM

Summary plus key scenes. Good enough to answer 'what does the customer want in this video?'

Stickers

WhatsApp / IG decorative

Stored for the inbox view but not analyzed — they carry no useful content.

2Always on, for 28 days

There is no switch to find. Every agent reads the files customers send, on every channel, from the moment the file arrives.

Each file stays readable for 28 days. After that the agent can no longer read it — the AI-extracted version is removed from its context. The customer's original message and attachment remain in your inbox.

3What happens when a customer sends a file

Customer sends it

WhatsApp, Instagram, or Messenger — the inbound webhook receives the attachment.

Platform reads it

The file is extracted in the background. Usually within 10–30 seconds for documents, longer for big videos.

Agent uses it

On the next reply, the agent has the file's content available and can answer questions about it.

While a file is still being read, the agent sees it as "still processing". If the agent wants to wait for the file before replying, it will. If it would rather acknowledge first and answer in a follow-up, it can — see step 5 below.

4Review what the AI understood

Open any chat (real inbox or Test Chat). On a file message, click the ⌄ chip:

  • For a document or spreadsheet: you'll see the extracted text.
  • For an image: the AI's description plus suggested uses.
  • For audio: the full transcript.
  • For video: a summary plus the key scenes.

Spot a mistake? Click Edit.

Fix the text, save, and the agent will use your corrected version from then on. This is the fastest way to recover from a misread invoice number, a transcription error, or a scanned PDF the AI couldn't parse.

5Acknowledge before reading

Bigger files (long videos, hefty PDFs) can take several seconds to extract. While it waits, your agent can send a quick "Got your file, give me a moment to read it." while it waits — so the customer never wonders if you saw their attachment.

The agent decides when to send it — based on the file size and the context of the conversation. It's not forced on every file.

6Try it in Test Chat

The editor's Test Chat panel has a paperclip button. Click it, pick a file from your computer, and the same upload + extraction flow runs against a private test conversation pinned to that agent.

Real flow, sandbox data

Same bubble, same modal, same AI as production. Ask the agent about the file's contents to see how it would reply to a real customer.

Test files expire fast

Files uploaded through Test Chat live for 1 hour, then they're removed automatically. The 28 days only apply to files your customers send.

You need to have at least one inbox connected (WhatsApp / Instagram / Messenger) to use the Test Chat paperclip. We pin the test conversation to one of your existing inboxes for safety reasons — nothing is ever sent outbound.

7Cost note

A file is processed once, when it arrives.

There's no standby cost — the meter only runs when an inbound message actually carries a file.

FAQ

How long can my agent read a file?

28 days from the moment it arrives. After that the agent no longer sees its content; the original stays in your inbox.

What's the maximum file size?

The agent reads files up to 50 MB. Test Chat uploads are capped at 25 MB to keep the editor responsive.

Does the agent see the literal attachment, or a text version?

For text-bearing files (PDF, DOCX, CSV, etc.) the agent reads the extracted text. For images and videos, the AI generates a description and the agent reads that. For audio, the agent reads a transcript. The original file stays in your inbox view.

Can the customer's image with sensitive data leak somewhere?

Files are stored in your Kronos AI storage scoped to your account and protected by Row Level Security. Extracted text is only visible to your agent and to you in the editor.

What if the extraction fails — bad PDF, corrupted audio, etc.?

The file bubble shows Processing failed. Click it to see the reason. You can paste the contents manually in the Edit textarea and the agent will use that version.

Why does my agent sometimes say 'give me a moment' before answering?

Bigger files take a few seconds to extract. The agent may send a brief acknowledgement so the customer knows it's working on it, then answers once the file is read.

Does this work for follow-ups too?

Yes. Files the agent can read are referenced the same way during a scheduled follow-up turn — if the file is still within its 28 days.

What happens when I cancel my plan?

Operational data including extracted file content is purged on cancellation along with your other agent / conversation data. Your original message and attachment files remain inside your cancellation grace period before final purge.
File Understanding — Kronos AI Docs | Kronos AI