SMS can be sent programmatically from an application using SMS APIs and libraries or SDKs, by using an SMS text messaging add-on or extension to software (e.g. Microsoft Excel), by using an application with in-built SMS text messaging capability or by using a SaaS (software-as-a-service) application through your web browser (e.g. web SMS portal such as the Melrose Labs webSMS). An example of a SaaS application for sending bulk SMS for marketing purposes is portal that allows you to send SMS text marketing that encourages the recipient to make a purchase or perform some other action.
REST calls can be made via HTTPS to send SMS to mobiles, and also to cancel, query and replace previously submitted SMS messages. Webhooks allow for delivery receipts to be sent to your application without the need to poll for the status of messages.
Short Message Peer-to-Peer v3.3, 3.4 and v5 is supported and the SMPP PICS (Protocol Implementation Conformance Statement) showing the level of support is provided. SMPP can be used to establish sessions over which SMS can be submitted (submit_sm PDU), queried (query_sm PDU), replaced and cancelled. Delivery receipts are also sent across these SMPP sessions when messages reach a completion state. Inbound SMS from mobiles (MO SMS) are also sent via SMPP.
Programming or scripting languages such as Python, PHP, Node.js, Go and others can be used with SMS APIs such as SMPP and REST to send and receive SMS.
Web portals enable you to send and receive SMS online. Login using your web browser to the portal and you can quickly send a message to a single person or thousands of people. You can read and reply to messages received from mobile users.
In addition to manually entering the mobile numbers to receive messages, portals can be used with distribution lists and phonebooks to select the people to whom your message is sent. These distribution lists and phonebooks can be connected to external data sources such as corporate staff directories, school management systems and databases.
Portals can show the delivery status of each message sent to a mobile, even when sending to large distribution lists. A message should show in a portal as being delivered within seconds of it being delivered to a mobile.
An inbox in the portal will show messages that have been sent from mobiles to the inbound mobile number associated with the portal account. From the inbox you can normally reply to received messages.