Sending photos, documents and voice notes
Everything works as you would expect, except one thing that makes your invoice arrive nameless.
You can send photos, videos, documents and voice notes from the inbox, and they arrive as ordinary WhatsApp messages. Most of it needs no explanation. One detail does, and it is the difference between a customer receiving your invoice and receiving an unnamed attachment.
What you can attach
| Type | How | Typical use |
|---|---|---|
| Photos and videos | The attach menu | Product shots, proof of dispatch, a damaged item |
| Documents | The attach menu | Invoices, receipts, price lists, warranties |
| Voice notes | The microphone button | Long explanations, and customers who prefer voice |
Recording is what you would expect: press the microphone, a timer runs, and you either send it or discard it.
The filename detail
This is the one worth knowing. WhatsApp labels a document by the filename it is
sent with — so a file called scan_0093.pdf arrives as
scan_0093.pdf, and one with no usable name arrives looking
untitled.
The customer sees that name in their chat and again in their downloads, possibly months later when they go looking for it. One second of renaming before you upload does more for how professional your business looks than most things you could spend an hour on.
- Good:
Invoice-10482-YourShop.pdf - Bad:
document(3).pdf,IMG_20260828.pdf,final_v2_FINAL.pdf
The same rule applies to documents an automation sends, where the filename is set on the step rather than by hand — worth checking on any flow that sends an invoice or a receipt.
When to use a voice note, and when not to
Voice notes are genuinely useful in two situations: explaining something that would take five paragraphs, and replying to a customer who sent one first. In many markets voice is simply how people prefer to communicate, and matching that is good service.
Three cautions:
- They cannot be skimmed. A customer looking for one detail has to listen to the whole thing.
- They are not searchable by you or by them. Anything that needs to be found again should be text.
- Nothing contractual. Prices, commitments and policies belong in writing.
A good pattern is a voice note for the explanation and a short text message after it with the key facts.
The window applies to attachments too
An attachment is a message, so it is subject to the same 24-hour customer service window as anything else you type, per Meta's sending messages documentation. If the message box is locked you cannot send a photo either.
Inside the window it is free — service conversations have been free and unlimited since 1 November 2024 under Meta's pricing documentation — so there is no cost reason to hesitate over sending a customer the photo they asked for. The states of that lock are in the 24-hour countdown.
Receiving media from customers
Customers send photos constantly — a damaged item, a screenshot of a payment, a picture of the thing they want. Two habits make that useful rather than chaotic:
- Note what the photo showed, in an internal note, so the next person does not have to open it.
- Do not rely on the image as the record. If a customer sends proof of payment, write the reference into a contact field.
A flow can also look at a customer's photo and act on it, which is one of the few genuinely good uses of AI in an automation — described in when to use AI and when to use buttons.
Practical limits
WhatsApp has its own size limits and accepted formats, and they are Meta's rather than your provider's. In practice:
- Compress large documents before sending. A slow download on mobile data is a document nobody opens.
- Prefer PDF for anything a customer might keep.
- Send a photo rather than a screenshot of a photo, which sounds obvious and happens daily.
- Say what the file is in the message alongside it. An attachment with no context gets ignored.
Frequently asked
Can I send several files at once?
Attach them as separate messages, and say what each one is. A customer receiving four unexplained files will open none of them.
Do voice notes cost more?
No. Inside the window, everything you send is free; the charge is for templates outside it.
Can an automation send a document?
Yes, and it can name it — which matters for exactly the reason above.
What if the customer cannot open my file?
Usually a format issue. PDF is the safest choice for anything that must open on every phone.
What attachments are worth sending unprompted
Most attachments are replies to a request. A few are worth sending without being asked, because they prevent a conversation rather than continue one:
| Send | When | Prevents |
|---|---|---|
| A photo of the packed order | High-value or fragile items | Disputes about what was sent |
| The invoice as a named PDF | On confirmation | "Can you send me a receipt?" |
| A size or spec chart | When they are choosing | A return |
| A short product video | Before a considered purchase | Hesitation |
The first row is worth adopting in any business where "that is not what I ordered" happens. It costs one photo inside a conversation that is already free under Meta's pricing documentation.
A naming convention worth agreeing once
- What it is — Invoice, Receipt, Warranty, Pricelist.
- The reference — the order number.
- Your business name.
So: Invoice-10482-YourShop.pdf. Three parts, in that order, and the
customer can find it in six months without opening it. Agree it with the team and it
stops being a decision anybody makes per file.
If the box is locked
You cannot attach anything either — the 24-hour window governs all messages, not just typed ones, per Meta's sending messages documentation. Reaching a customer outside it needs an approved template under Meta's template documentation, and a template can itself carry a document header, which is how automated invoices reach people days later.
Media in an automation, briefly
Everything above is about an agent typing. Flows can send media too, and the same naming rule applies with one difference: the filename is set on the step rather than by whoever picked the file, so it is worth checking on any flow that sends an invoice or a receipt.
A flow can also put an image at the top of a template, which is how an order confirmation carries a product photo. The step-by-step is in every automation step, explained.
A short checklist before you press send
- Is the file named something the customer will understand in six months?
- Is it the right file? Opening it once is cheaper than the conversation afterwards.
- Have you said what it is, in the message beside it?
- Is it small enough to open on mobile data?
- Should this be text instead, so it can be searched later?
Five seconds, and it covers every attachment problem a customer ever reports back — the same read-before-you-send discipline as in drafting a reply with AI.
Voice notes and your records
One consequence worth planning for: a voice note is not searchable, so anything important said in one is effectively lost to your future self. A customer's address given by voice, a price agreed by voice, a delivery date promised by voice — none of those will be findable in six months.
The habit that fixes it costs seconds. After any voice exchange that settled something, write the settled thing down — either as a short message to the customer, which also confirms it, or as an internal note.
That second option is described in internal notes and mentions, and it is the right home for anything the customer does not need to see again.
The short version
Photos, videos and documents go through the attach menu; voice notes through the microphone. Name every document before you send it, because the filename is what the customer sees now and in six months. Attachments obey the same 24-hour window as typed messages, and inside it they cost nothing.
Voice notes are good for explaining and bad for anything anybody will need to find again — so follow one with a short text carrying the facts.
One habit for the whole team
Rename before you upload. It is the only thing on this page that people consistently skip and consistently regret, because the cost lands on the customer weeks later when they go looking for the invoice.
Everything else here is judgement — whether a voice note suits the moment, whether a photo would settle a dispute. The filename is the one rule, and it takes a second.
A note on customer expectations
People send photos and voice notes on WhatsApp constantly, because that is what the app is for. A business that only ever replies in text reads as slightly stiff by comparison, and in several markets it reads as unhelpful.
Matching the medium the customer chose is usually the right instinct — with the one caveat above, that anything either side will need to find again belongs in writing as well.
The same applies in reverse. A customer who sends a voice note is usually comfortable receiving one, and replying in kind is often faster for both of you than typing out something they described in fifteen seconds.