Introduction
This page provides guidelines for clients wishing to implement Premium SMS (PSMS) services on bespoke applications.
Please note that the sending of spam messages is strictly prohibited. The end user must have opted-in to receive marketing messages and other SMS communications
Overview
The Triangle SMS Suite is a feature rich, robust and scalable two-way SMS delivery platform. Through which clients can have access to PSMS services. Clients may interface with the platform by either using the on-line SMS Suite or creating applications using our SMS API. For a number of reasons such as:
- Contracts
- Billing Mechanisms
- Number portability
There are additional requirements on how clients should handle PSMS traffic via a bespoke platform. These requirements can be summarised in two parts.
- It is advisable that subscribers order each service by sending an MO message to the designated short code. The benefit of this is that it confirms the originating network to the application allowing correct association of number/network for the outgoing MT billed SMS.
- The ordered service must be sent out using the correct Operator, Tariff, Profile and Originator.
MO Message (Mobile Originated)
In order to identify the originating Network and short code of of MO messages, clients will be provided with a list of 'Network Identifier' values, that will be passed to the client application.
MT Messages (Mobile Terminated)
Linking the customers mobile number with its corresponding network identifier will allow MT messages to be sent using the correct required values, failure to provide a correct identifier may result in the message not being billed.
Requirements
Below are some useful indicators on what is possible on various networks.
MT Parameters
- Virgin messages are sent along the same connection as T-Mobile.
- WAP push messages must not be sent as billable, they must use a zero rated tariff.
- An unknown delivery report will be returned on the Three network if we receive no notification from the network within 12 hours. Please set an expiry time of 7 days for Three messages.
Age Verification
Both Orange and O2 require all service providers to age verify subscribers on all adult short codes.
- When an Orange subscriber submits an MO to an adult short code this will go through the automatic Age Verification process. If successful the MO will be passed on. If the end users is not age verified then an MO containing the text 'keyword AGEVERIFY' will be sent to the client. We recommend when you receive this AGEVERIFY message that you send a zero rated message to the customer encouraging them to age verify and resubmit the MO. Do not retry billable messages to the customer in this circumstance.
Free message text: Orange Content Control has blocked access to this service. To access this service Pre-Pay users please dial 450, Contract users please dial 150. Thanks.
On O2 there are 4 age verification states for O2 subscribers:
- Age Verified
- Previously failed to age verify
- Previously had parental lock applied
- Has never age verified/unknown age verification status
If a subscriber is age verified the MT message shall be delivered immediately. Service Providers with adult short codes shall receive 1 of 4 PTT codes for subscribers that are not age verified. These are specified in the PTT technical guide. For each age verification PTT code, service providers are required to submit a MT message using the 'zero tariff' ProfileID.
External Links
| 
