Choose the format that answers the question
Use a photo to show a detail, a short video to demonstrate something, or a document when the recipient needs a copy they can keep. Explain what you are sending in the conversation. Do not make someone download a file just to find out why you contacted them.
For a voice note, include a short text summary when the key information is time-sensitive or easier to read. The person may be somewhere they cannot listen.
Check the file before sending
- Open the file and verify that it is the intended version.
- Crop or remove unrelated personal details from screenshots.
- Keep videos and documents as small as practical while retaining useful detail.
- Use the attachment picker or supported voice-note control in the conversation.
- Review the selected recipient, sending number, and any accompanying text before sending.
Check the message after upload
An uploaded file is not yet a delivered message. Check the attachment’s message state in the conversation. If the upload fails, read the size or format error. If a send is still pending, avoid creating several duplicate sends while it settles.
If a recipient cannot open the file, confirm the type and try a simpler supported format or a permission-checked link to the resource. Do not rename a file extension as a substitute for converting it.
Find media from previous conversations
Open Media in the selected project to browse images, videos, audio, and files sent or received on its numbers. Use Previous and Next to move through older messages with attachments.
Media is a view of conversation files, not a separate collection of reusable message templates. If an item is missing, check the original conversation, the project, and your access to its sending number.
Test media in an integration
First test upload metadata and error handling in the sandbox. Then use a consenting test recipient on the intended channel to check actual playback or download behavior. A simulated upload does not test a real device or media delivery.