Start with a short, useful statement.
Imagine a fictional property business preparing a September statement for Jennifer. The useful content is the statement period, a clear account reference and a small set of relevant entries. It does not need a full customer dossier or unrelated pages.
EXAMPLE — NOT A REAL ACCOUNT
September account statement
Customer: Jennifer Example
Reference: DEMO-STATEMENT
Period: 1–30 September
Message: “Hi Jennifer. Your September statement is attached.”
This is fictional document content. Use the interactive preview to explore how an accompanying image could look.
Prepare, send, review.
- Confirm the recipient and purpose. Check that the customer's number is current and appropriate for account communications. An existing account does not remove privacy obligations.
- Export an image. PDF upload and automatic PDF conversion are not supported. Export the relevant statement page or create a concise image summary in your source system.
- Check small-screen readability. Use clear type, generous spacing and a simple layout. Check the source image and the processed JPEG. Avoid shrinking many rows onto a single page.
- Submit through the dashboard or API. Add the recipient, short message and supported image. Respect the configured attachment, text and final-media limits.
- Keep the reference. Retain your source statement and record the MMS Express message ID in your business process. An image does not replace the original document.
- Review the result. Check the message history. Failed or unresolved results need attention. Sent means submission to the delivery network, not proof of reading.
Several pages need more care.
The service can accept multiple images within its configured limits, or join images vertically in the order you supply. A tall combined image may be difficult to read on a phone. Do not assume that image joining makes an entire PDF suitable for MMS.
Prefer the most useful summary for this channel. If a customer needs a searchable file, a full original or a protected document viewer, provide that through a suitable separate route.
Make the follow-up part of the workflow.
Decide who checks exceptions and what they should do before running a regular statement process. Investigate an uncertain result before sending another copy. For software-driven statements, use a stable idempotency key for each business operation and reconcile by the returned message ID.
For more detail, read document handling and limits, API workflow planning and sensitive-content guidance.
Plan your statement workflow