Billing types
Type | Description |
---|---|
Basic message | An application-to-person (A2P) message that
Conversational agents only: |
Single message | An application-to-person (A2P) message that
Conversational agents only: |
A2P conversation | Conversational agents only: |
P2A conversation | Conversational agents only: |
Mobile terminated (A2P) session scenarios
A2P scenario 1
The brand sends a message (MT 1) to the end user, to which the end user responds with MO 1, triggering session billing. The session lasts 24 hours, starting from the end user's response (MO 1). The first message from the brand (MT 1) is also included in session billing.
![RCS A2P Scenario 1](https://infobip-cdn-h0h7ekhqhgh4hgau.a02.azurefd.net/1g8x60m5haaeebc38sw9etdnqwq2orfxs6yjtxwklw767cqz71/a2p-scenario-1.png)
A2P scenario 2
The brand sent a message to which the end user never responded. The message is being billed as single/basic.
![RCS A2P Scenario 2](https://infobip-cdn-h0h7ekhqhgh4hgau.a02.azurefd.net/1g8x60m5haaeebc38sw9etdnqwq2orfxs6yjtxwklw767cqz71/a2p-scenario-2.png)
A2P scenario 3
The brand sent two messages within 24 hours. Each time a brand sends a message, the time period resets and starts again for the next 24 hours. That means that MT1 will be billed as a single message. The rest of the communication is within the scope of the session (which lasts 24 hours).
![RCS A2P Scenario 3](https://infobip-cdn-h0h7ekhqhgh4hgau.a02.azurefd.net/1g8x60m5haaeebc38sw9etdnqwq2orfxs6yjtxwklw767cqz71/rbm_session_03.png)
A2P scenario 4
The brand sent a message (MT 1) to which the end user (MO 1) responded after 24 hours. This MT1 message is being billed as single/basic. In this case, the end user's response (MO 1) has not triggered any session or any type of billing. This is only because MT 2 also occurred after 24 hours of the MO 1 message. So, after the second MT2 message from the brand, the session procedure is the same as in scenario 1.
![RCS A2P Scenario 4](https://infobip-cdn-h0h7ekhqhgh4hgau.a02.azurefd.net/1g8x60m5haaeebc38sw9etdnqwq2orfxs6yjtxwklw767cqz71/rbm_session_04.png)
Mobile originated (P2A) session scenarios
P2A scenario 1
Here, we have an example of P2A communication, which means that the end user initiated the communication. In this situation, a 24-hour window session starts with an MOx message prior to A2P, and all A2P messages from that point are billed as a session (until the 24-hour window runs out).
Before MO1, there were no MTx messages or ongoing sessions in the previous 24 hours.
![RCS P2A Scenario 1](https://infobip-cdn-h0h7ekhqhgh4hgau.a02.azurefd.net/1g8x60m5haaeebc38sw9etdnqwq2orfxs6yjtxwklw767cqz71/rbm_session_05.png)
P2A scenario 2
In the case of multiple MO messages, only the last MO message (in this case, MO3) prior to MT1 will start the 24-hour window session, and the same logic applies as in P2A scenario 1.
- MO1 - 9:00 - 24-hour window begins
- MO2 - 10:00 - 24-our window begins
- MO3 - 11:00 - 24-hour window begins
- MT1 - 24:00 - first message
- MO4 - 9:00 next day
- MT2 - 10:59:59 - 24-hour session ends
![RCS P2A Scenario 2](https://infobip-cdn-h0h7ekhqhgh4hgau.a02.azurefd.net/1g8x60m5haaeebc38sw9etdnqwq2orfxs6yjtxwklw767cqz71/rbm_session_06.png)
P2A scenario 3
This scenario covers situation where there was no response to Brand message (MT 1) in 24-hour period. Even though the end user responded (MO 1) after some point, this response was after first 24 hour session period, which means this is the beginning of P2A session now.
![RCS P2A Scenario 3](https://infobip-cdn-h0h7ekhqhgh4hgau.a02.azurefd.net/1g8x60m5haaeebc38sw9etdnqwq2orfxs6yjtxwklw767cqz71/rbm_session_07.png)