US billing types

|

View as Markdown

In the United States, RCS messages are billed as one of two types:

  • Rich messages
  • Rich media messages

Message classification depends on whether the content is text-only with basic actions or contains media and advanced suggested actions.

Type

Description

Rich message

An application-to-person (A2P) or person-to-application (P2A) message that:

  • Contains only text.
  • Bills in segments of 160 UTF-8 bytes.
  • Can contain suggested replies (A2P only).
  • Can contain the following suggested actions:

A rich card that only contains a title and/or description is not considered a text-only rich message.

NOTE

Text-only P2A messages are charged in 160-byte segments.

Rich media message

An application-to-person (A2P) or person-to-application (P2A) message that:

A rich media message can include suggested replies and suggested actions, such as Dial phone and Open URL (Browser). If the message contains any multimedia content, it is automatically classified as a rich media message.

Messages with only text are also classified as rich media messages if they include one or more supported suggested actions. In such cases, they are not treated as simple rich messages.

NOTE

P2A billing: If a P2A message contains a file, it is billed as a rich media MO message.

NOTE

Some carriers charge for P2A messages. Text-only P2A messages are billed in segments, following the same segmentation rules applied to A2P messages.

The following message types are billed as P2A:

  • Real MO messages: Sent when an end user manually sends a message directly to a sender.
  • Quick reply MO messages: Sent when an end user selects a Reply suggestion button.
  • Request location MO messages: Sent when an end user shares their location after selecting a Request location suggestion button.

If a P2A message contains a file, it is billed as a rich media MO message.



Track US billing with webhooks

For messages in the United States, the trafficType field returns values that map to the US billing types:

trafficType valueBilling type
RICHRich message
RICH_MEDIARich media message
A2P_INTERACTIVE_SESSIONA2P Interactive Session (conversational senders only)
P2A_INTERACTIVE_SESSIONP2A Interactive Session (conversational senders only)

Segment counts for rich messages: Rich messages in the US bill in 160-byte segments, and delivery reports and inbound webhooks report how many segments each message used.

FieldWebhookDescription
messageCountReceive RCS delivery reportsNumber of 160-byte segments the outbound Rich MT message used. Found at results[].messageCount in the delivery report payload.
rcsCountReceive RCS inbound messageNumber of segments an inbound Rich MO message contains. Found at results[].rcsCount. Can be greater than 1 for Rich messages in the US.


US Interactive Session

US Interactive Session is a session-based billing model for conversational RCS senders in the United States. It uses different criteria than global A2P and P2A conversation billing.

A2P and P2A session classification

Interactive Sessions are classified by direction based on who sends the first message in the session:

  • A2P Interactive Session: The business (sender) sends the first message in the session. The trafficType is A2P_INTERACTIVE_SESSION and the conversation.type is INTERACTIVE_SESSION_A2P.
  • P2A Interactive Session: The end user sends the first message in the session. The trafficType is P2A_INTERACTIVE_SESSION and the conversation.type is INTERACTIVE_SESSION_P2A.

The session trigger criteria (4 qualifying messages, at least 2 P2A and 1 A2P, within 24 hours) remain the same regardless of classification. The classification determines which trafficType value appears in webhooks and how the session is priced.

NOTE

The directional classification affects billing and reporting only. Both A2P and P2A Interactive Sessions use the same trigger criteria and 24-hour session window behavior.

MO message qualifications

Only specific person-to-application (P2A) actions count toward the Interactive Session trigger:

  • The end user sends a free-text or file reply.
  • The end user taps a suggested reply.
  • The end user shares their location.

The following actions do not count toward the trigger:

  • Clicking an Open URL, Add to calendar, or similar suggested action button.
  • Tapping Request location without completing the location share.
  • Typing notifications.
  • Delivery receipts.
  • Seen receipts.
  • Read receipts.

An Interactive Session starts when all of the following criteria are met:

  • 4 qualifying messages are exchanged within a 24-hour period
  • At least 2 person-to-application (P2A) messages
  • At least 1 application-to-person (A2P) message
  • Messages can occur in any order

When these criteria are met, a 24-hour free messaging window opens, anchored to the first of those 4 messages. All messages within this window are part of the Interactive Session and are not charged individually.

NOTE

If the session criteria are not met, each message is charged individually as a Rich message or Rich media message based on its content. For example, if no end user reply follows an A2P message, no session starts.

Key differences from global billing:

Global modelUS Interactive Session
Directional (A2P or P2A conversation)Non-directional (criteria-based: 4 messages with 2 P2A + 1 A2P)
Session starts from reply messageSession starts from the first message in the 4-message sequence
Available for conversational senders globallyAvailable only for conversational senders in the United States
Single conversation type per sessionSession classified as A2P or P2A based on who sends the first message
IMPORTANT

Interactive Sessions apply only to conversational senders. Non-conversational senders use message-based billing (Rich message or Rich media message) regardless of message volume or timing.


Interactive Session scenarios

Business-initiated session

An Interactive Session is classified as A2P when the business sends the first message, which in this scenario is MT 1. The sender and end user exchange 4 qualifying messages within a 24-hour window (2 A2P + 2 P2A). MO 2, the 4th qualifying message, completes the trigger.

Message flow and session trigger

  • MT 1 (Sender to end user): The sender initiates the conversation.
  • MO 1 (End user to sender): The end user sends the first reply, contributing to the session trigger.
  • MT 2 (Sender to end user): The sender sends a second message.
  • MO 2 (End user to sender): The second end user reply satisfies the composition requirement and completes the session trigger.

How session billing works

  • Session anchor: The session retroactively anchors to MT 1, the earliest message in the sequence.
  • Charged message: MT 1 is the charged message, and its cost is recalculated to A2P_INTERACTIVE_SESSION.
  • Real-time billing: MO 2 receives its billing classification in real time.
  • Retroactive billing events: The remaining 3 messages (MT 1, MO 1, and MT 2) each receive a retroactive Conversation Started event (3 CONVERSATION_STARTED events total).

All messages within the 24-hour session window are part of the Interactive Session and are not charged individually.

US Interactive Session Scenario 1: Session triggered with 4 qualifying messages
MessageDirectionQualifyingcanInitiateOriginal trafficTypeUpdated trafficType
MT 1Sender to end userYes (1/4)trueRICH / RICH_MEDIA (charged)A2P_INTERACTIVE_SESSION (charged)
MO 1End user to senderYes (2/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MT 2Sender to end userYes (3/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MO 2End user to senderYes (4/4), completes the triggerfalsenull (not charged)N/A
NOTE

The 24-hour session window starts from MT 1, not from MO 2. All messages exchanged within that window, including MT 1 itself, are part of the session. An Interactive Session is classified as A2P when the business sends the first message, which in this scenario is MT 1.

Insufficient messages

Fewer than 4 qualifying messages are exchanged within a 24-hour period. The trigger condition is not met, and each message is billed individually as a Rich message or Rich media message.

US Interactive Session Scenario 2: Trigger not met with only 3 qualifying messages
MessageDirectionQualifyingcanInitiateOriginal trafficType
MT 1Sender to end userYes (1/4)trueRICH / RICH_MEDIA (charged)
MO 1End user to senderYes (2/4)trueRICH / RICH_MEDIA (charged)
MT 2Sender to end userYes (3/4)trueRICH / RICH_MEDIA (charged)

Only 3 qualifying messages occur within 24 hours. The trigger requires 4, so no session starts.

Window expired

Messages are exchanged, but a gap of more than 24 hours separates early messages from later ones. By the time the 4th message arrives, earlier messages have expired from the rolling 24-hour window. Fewer than 4 qualifying messages remain in scope, so no session starts.

US Interactive Session Scenario 3: 24-hour rolling window expires before trigger is met
MessageTimecanInitiateIn 24h window at MO 2?Original trafficType
MT 1T+0htrueNo, expiredRICH / RICH_MEDIA (charged)
MO 1T+25htrueYesRICH / RICH_MEDIA (charged)
MT 2T+26htrueYesRICH / RICH_MEDIA (charged)
MO 2T+27htrueYesRICH / RICH_MEDIA (charged)

At MO 2, the 24-hour look-back window contains only MO 1, MT 2, and MO 2 (3 qualifying messages). MT 1 has expired, so the trigger is not met.

Non-qualifying actions

Actions such as clicking Open URL or Add to calendar buttons do not count as qualifying messages toward the 4-message session trigger.

US Interactive Session Scenario 4: Non-qualifying events do not count toward trigger
MessageDirectionQualifyingcanInitiateBilling
MT 1Sender to end userYes (1/4)trueRICH / RICH_MEDIA (charged)
MT 2Sender to end userYes (2/4)trueRICH / RICH_MEDIA (charged)
URL click (end user)End user to senderNo, not qualifyingfalsetrafficType = null (not charged)
MO 1End user to senderYes (3/4)trueRICH / RICH_MEDIA (charged)

Qualifying messages total 3 (2 A2P + 1 P2A). The trigger requires at least 2 P2A messages, so it is not met.

Multiple outbound messages

An Interactive Session is classified as A2P when the business sends the first message, which in this scenario is MT 1. The sender sends MT 1, and the end user responds with MO 1. The sender then sends 4 additional MT messages (MT 2 through MT 5) while waiting for another end user response. The end user responds with MO 2, completing the session trigger. All 7 messages occur within a 20-hour window, leaving 4 hours available in the 24-hour Interactive Session window.

Message flow and session trigger

  • MT 1 (Sender to end user): The sender initiates the conversation.
  • MO 1 (End user to sender): The end user sends the first reply, contributing to the session trigger.
  • MT 2 through MT 5 (Sender to end user): The sender sends four additional messages while awaiting another response. MT 3, MT 4, and MT 5 do not advance the trigger progress.
  • MO 2 (End user to sender): The second end user reply satisfies the composition requirement and completes the session trigger.

How session billing works

  • Real-time billing: MO 2 receives its billing data immediately upon completing the session trigger.
  • Retroactive billing events: The preceding 6 messages each receive a retroactive Conversation Started event.
  • Trigger composition: At least 2 of the 4 qualifying messages must be MO messages. Before MO 2, only 1 qualifying MO message had been received, so additional MT messages could not complete the trigger.
US Interactive Session Scenario 5: Multiple outbound messages sent before second inbound completes trigger
MessageDirectionQualifyingcanInitiateOriginal trafficTypeUpdated trafficType
MT 1Sender to end userYes (1/4)trueRICH / RICH_MEDIA (charged)A2P_INTERACTIVE_SESSION (charged)
MO 1End user to senderYes (2/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MT 2Sender to end userYes (3/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MT 3Sender to end userNo (3/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MT 4Sender to end userNo (3/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MT 5Sender to end userNo (3/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MO 2End user to senderYes (4/4), completes the triggerfalsenull (not charged)N/A
NOTE

MO 2 receives its billing data in real time. The remaining 6 messages (MT 1 through MT 5 and MO 1) each receive a retroactive Conversation Started event (6 CONVERSATION_STARTED events total). An Interactive Session is classified as A2P when the business sends the first message, which in this scenario is MT 1.

End-user-initiated session

An Interactive Session is classified as P2A when the end user sends the first message, which in this scenario is MO 1. The end user sends 3 MO messages before the sender responds with MT 1. MT 1 is the 4th qualifying message and completes the trigger.

Message flow and session trigger

  • MO 1 (End user to sender): The end user initiates the conversation.
  • MO 2 (End user to sender): The end user sends a second message, contributing to the session trigger.
  • MO 3 (End user to sender): The end user sends a third message, contributing to the session trigger.
  • MT 1 (Sender to end user): The sender responds with the first outbound message, satisfying the composition requirement and completing the session trigger.

How session billing works

  • Real-time billing: MT 1 completes the trigger and receives its billing classification (P2A_INTERACTIVE_SESSION) and conversation.id in real time. No Conversation Started event is sent for MT 1.
  • Retroactive billing events: Each of the 3 MO messages receives a retroactive Conversation Started event with trafficType set to null (3 CONVERSATION_STARTED events total).
  • Session anchor: The 24-hour session window starts from MO 1, not from MT 1.
US Interactive Session Scenario 6: End user initiates with multiple inbound messages before first outbound
MessageDirectionQualifyingcanInitiateOriginal trafficTypeUpdated trafficType
MO 1End user to senderYes (1/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MO 2End user to senderYes (2/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MO 3End user to senderYes (3/4)trueRICH / RICH_MEDIA (charged)null (not charged)
MT 1Sender to end userYes (4/4), completes the triggerfalseP2A_INTERACTIVE_SESSION (charged, in real time)N/A

Was this page helpful?