Send a reviewed private image message

Open a private conversation, choose Private operational texts, then Private image messages and MMS receipts. Image messages use the same verified phone permission and operational opt-out rules as private texts. A stored phone number alone never permits delivery.

Prepare your images

Upload a JPEG or PNG up to 8 MB, add a useful description and approve its displayed storage/processing reservation. The workspace must already be enrolled in metered usage with sufficient spending capacity. The original remains private. A durable job decodes the file, removes embedded metadata and prepares a static message image of no more than 600 KB. A renamed unsupported file does not become a supported image.

Refresh processing and receipts to see the current state. An interrupted upload retains its original request, file checksum, description and approved charge. Resume original upload requires that same file and approval. If the original is safely stored but processing needs attention, use Retry image processing. A retry reuses the retained artifact and original usage reservation. An already-funded original request can be resumed if the workspace later disables usage spending; that recovery does not enable new uploads or new charges.

Descriptions belong to the original image record. Upload a new reviewed source for a materially different reference. The image library is scoped to this inquiry; it is separate from professional gallery delivery, guest media and other businesses’ files.

Review the sender and recipient

An owner or administrator records Sender image capability after checking that the configured provider number supports MMS. Ordinary SMS approval does not imply MMS support. A changed provider generation requires a fresh capability review. This control records a decision; actual provider registration and activation happen separately.

Select an active, verified phone permission with a currently reviewed MMS sender. Recipient quiet hours, expiry, opt-out and conversation pause still apply. An archived or merged original inquiry keeps its history but cannot send new messages.

Approve the complete message

Write the message, optionally insert approved source fields, and choose one to three processed images. Use Earlier and Later to set the exact delivery order. For example, send a fictional venue meeting-point diagram first, followed by the agreed portrait palette, with a sentence explaining when the recipient needs each reference.

Review exact image message shows the fully resolved text, business branding, reply instructions, opt-out text, recipient, sender, ordered images, timing and maximum MMS charge. Expand Reviewed source fields to inspect the values used. Storage costs are separate from the delivery quote. A message is not queued until you approve this exact review.

Scheduling uses the chosen IANA timezone. Ambiguous or nonexistent local times at daylight-saving changes require another choice. The recipient’s permitted delivery window can move the dispatch time. Carrier delivery and device display are separate from the application’s dispatch time, and a carrier may present images differently.

Read the original receipt and recover safely

The delivery retains its approved text, image order, quote and original receipt. Contact edits, disclosure-policy changes, removed images, revoked membership, changed sender capability or withdrawn consent hold a stale delivery. Prepare a fresh review after resolving the current source; an approved message is never silently rewritten.

Stop further delivery and image retrieval stops work that has not been sent and revokes later protected image retrieval. It cannot erase an image already delivered to a device. Check original provider receipt reconciles an existing known provider message ID. An uncertain attempt without a confirmed ID is not automatically retransmitted.

Protected image URLs are bearer grants for the original provider attempt, lasting no more than 24 hours and never beyond that delivery’s expiry. Each retrieval checks the original scope and current access, and the private originals do not become public assets. The normal workspace previews require a current account session.

Retain an incoming image deliberately

A verified reply first records its signed image metadata. Supported image metadata appears only after it resolves to this specific private conversation. Choose Approve retaining image to approve a maximum storage cost based on the 8 MB limit. The downloaded file must match the signed media type and size limits; the actual retained-file charge cannot exceed that approved ceiling.

Retained files pass through the same private storage and processing checks as outgoing images. A lost response resumes the original request and approving person. Recovery first checks whether the original private object was safely stored; retrieving the provider’s original again still requires that same approval. There is no automatic new download. Unsupported media assigned to this conversation remains metadata for review. Unassigned or guest media stays outside this client’s page; the application does not guess which client owns it or blindly download its URL.

Remove a retained image to revoke protected access and schedule private and provider-side cleanup. Original message text, approved descriptions, ordering and operational receipt history remain. This cannot recall copies already retained by the carrier or a recipient’s device. Unreferenced uploads and retained incoming originals and processed images normally expire after 30 days. Queueing an approved outgoing delivery extends its referenced images to 180 days. The current record shows the exact expiry.

Activation boundaries

US MMS is separately metered and requires a reviewed MMS-capable sender, private storage, media workers, provider callbacks, encryption and enrolled usage. Local rehearsals use original synthetic drawings and deterministic provider responses. They do not establish registration, carrier delivery, international MMS support, video support or production activation.