Price delivered transport after automatic message conversion

When a messaging provider can convert long text into a different transport, price the provider's recorded protocol and billable units rather than multiplying the original text's inferred segments. A plain-text request with no attachments can still become a single multimedia message, so the API request shape does not establish its billing mode. Check the exact message record and base/carrier breakdown. Preserve any qualification that carrier fees use a current schedule rather than historical invoice charges. If conversion is disabled or unsupported by the destination carrier, the concatenated-text model may still apply.

Applies when: A provider automatically selects a transport for long messages. Keywords: messaging billing transport segments conversion multimedia carrier fees