Message Send Methods
When you send messages using the TextPower system they can be categorized as various types. This list explains the different types and what they represent:
IMMEDIATE (eventually deprecate all of these to avoid connection timeout problems)
SOAPMSG - Immediate send through current API right to the gateway - no queueing
MESSAGE - Immediate send through the old interface - no queueing (deprecated)
INTL- - Immediate send through international aggregators defined by parameter following the dash in the name
QUEUED (individual and bulk messages put into a queue process for metered spooling to aggregators)
MTQUEUE - Single message queue (individualized messages e.g., TaxAct,, STOP, virtually all utility outage messages)
MLQUEUE - Single message queue (individualized messages throughout 10-digit code - equivalent of MTQUEUE)
QSENDER - Bulk send queue (same message sent to multiple recipients, can contain PowerText variables, e.g., TeamKM)
QLSENDER - Bulk send queue (same as QSENDER but through a 10-digit code)
DEFERRED (scheduled to be sent out later)
DSENDER - Deferred message - specifying time/date to send then is sent via the queued process
DLSENDER - Deferred message (10-digit code equivalent of DSENDER)
DLQUEUE - Deferred message (10-digit code equivalent of MTQUEUE)
POSTQ - Posted a message out to a server - does not go to aggregators
VOICE - Sends a voice message out through a queued send process
EMAIL - Sends an email through a queued process
MESSAGE SEND METHODS
Individual Message Send
Usually used when each number is to receive a different message. You can send to up to 10 numbers with this call. However, if any of the numbers in the list is invalid, the entire batch will be canceled! Invalid numbers consist of both badly formed numbers and any number for which a carrier cannot be located. Thus a landline number in the batch will cancel the entire batch. If you use this, always use the Queue option and don’t ignore the send results sent to you!
Send type: MTQUEUE
API calls: SendSMS or SendSMSFull - both in Basic Interface Version 2 documentation
Bulk sends can be executed from the Alert Manager app as well as from an API call. All numbers opted in under the keyword in your credential header will be sent to unless narrowed by a list of one or more send tags supplied in the API call or on the Alert Manager app.
Send type: QSENDER
Example API calls used for this send type: SendToClients or SendToClientsByTag - both in Basic Interface Version 2 documentation
1. For messages that are individual in nature: E.g. The message contents are different for each number, set the Queued parameter.
2. For messages that are group in nature and are voluminous: Send data via SendToClients or SendToClientsByTag. Voluminous is a vague term but if the number of recipients is >100, definitely use SendToClients.
Customized Send Lists
Bulk Sends operate by extracting numbers from your Optin database, putting them into a temporary send list and then executing the send against that send list. You may create your own send lists however and execute the send against that list. These lists are permanent and do not get erased. The API calls to do this are found in the Advanced Message Services API set.