What Are Media Messages? A Guide for Businesses
Media messages share non-text content such as images, video, audio and documents in a conversation. Product photos, user guides and return documents can help explain or resolve a customer's request. Supported formats and file limits vary by channel. This guide covers the key concepts, setup checks and criteria for choosing an approach that fits your business.
Which content type should you use?
- Images: Use for product photos or size charts. Check that the product is correct and the resolution is readable.
- Video: Use for setup or usage instructions. Check file limits and playback on mobile devices.
- Documents: Use for catalogs or return forms. Check the version and access permissions.
- Audio: Use for spoken explanations on supported channels. Consider the recipient's preferences and clarity.
Location sharing and interactive buttons can also form part of a rich messaging experience, although they may be offered as technically separate message types. Do not assume every format supported by one channel also works on another.
How do you build a media messaging workflow?
- Identify the information the customer needs.
- Select content from an up-to-date, authorized source.
- For personalized documents, verify that the recipient matches the record.
- Check the channel's supported file types and sizes.
- Send the content with a brief explanation.
- If delivery fails, offer an appropriate alternative link or agent assistance.
Text or media?
Text may be enough for a short status update. Add media when a visual detail, an instruction or a document is needed. Sending a large file with every reply can create unnecessary friction. Text messages also have channel-specific length limits; check the limits for text and media separately.
Example business use cases
- E-commerce: Product images, size charts and return instructions.
- Hospitality: Room images or pre-arrival information documents.
- Technical support: Understanding an issue through screenshots and sharing the correct user guide.
- Business support: Sending the document needed for a specific request to an authorized recipient.
Instead of making every file available for automatic delivery, define which source can be shared, for which request and with which recipient. Personalized documents in particular require record matching and access controls.
Connect media sharing to your workflows with Palmate
In Palmate, a suitable sharing workflow can be designed around the customer request, channel and source system. The scope of automated delivery depends on the capabilities supported by the channel and integration. Review the channel and integration options, then let's assess your needs using a sample product image and support document.
Customer communication on WhatsApp and e-commerce automation are use cases this workflow can support. Starting with a small set of frequently used content helps expose issues such as incorrect files, outdated versions and failed delivery.
Book a demo to explore the right use case for your business.

Senior Software Developer
As a Software Developer at Palmate, Mustafa focuses on building scalable, high-performance products that turn complex AI capabilities into intuitive user experiences. He contributes to Palmate’s central AI platform, real-time embeddable chat widget, and web infrastructure. His background includes full-stack development for Canada-based DCBank.ca, covering digital identity verification, banking workflows, and card payment systems, as well as frontend development for Akinon’s marketplace platform. At Palmate, he applies this experience across React, TypeScript, Next.js, real-time web technologies, and LLM-driven product development.
Frequently Asked Questions
Answers to common questions on this topic.
Are media messages the same as MMS?
Can I send PDFs or videos on every channel?
Can media messages be sent automatically?
Will sending media always increase sales?
How should personalized documents be shared?
