Follow CDYNE Blog on WordPress.com
Header Image -

Tag Archives

14 Articles

The Monopoly of Short Codes!

The Monopoly of Short Codes!

Short Codes offer a unique opportunity to engage with customers fast and effectively. We know there are a lot of regulations and rules that come along with using short codes and it can get a bit confusing. In this article we answer some frequent asked questions about short codes from some of our CDYNE customers to help ease some of the confusion.

5 views

CDYNE’S Top 10 : Correct Text Messaging Techniques

CDYNE has put together a list of correct techniques when using short codes. They stress the importance of using the proper information, verbiage, and keywords to adhere to and stay in compliance with the CTIA, which is the organization that represents the wireless communications industry and ensures all rules and regulations are followed ( http://www.ctia.org/ ).The following Top Ten list is a guide to help make you aware of possible issues when sending short code text messages. For more details read the CTIA Citation Handbook Overview at http://www.wmcglobal.com/assets/ctia-mobile-commerce-compliance-handbook-v-1-3.pdf .

7 views

SMS Notify! API System Keywords

SMS Notify! API is a programming interface that provides connectivity to wireless carriers. It allows developers to build business applications to send and receive text messages using DIDs or short codes. DIDs are SMS-enabled 10-digit phone numbers (e.g., 757-544-9510), and short codes are 5- to 6-digit numbers (e.g. 55512). Here is a PDF document outlining the differences between each method. One important feature of SMS Notify! is the system keywords. When a person begins a text message with a system keyword and sends it to your DID or short code, SMS Notify! will automatically send a text message reply. System keywords and responses vary between DIDs and short codes as outlined below.

DID System Keywords

HELP

System Response:“Business Name”-SMS Notifications.Txt STOP to end.Msg&Data Rates may apply.”Business point of contact.”

  • The default business name is the name used to sign up for the SMS Notify! account. This may be updated by contacting CDYNE.
  • The business point of contact is two forms of contact including any combination of phone number, email, or website.
STOP, END, CANCEL, UNSUBSCRIBE, QUIT

System Response: This provider is now blocked. Text back RESUME to unblock your number.

  • SMS Notify! API will block the recipient’s number from receiving messages until the recipient sends RESUME.
  • CDYNE will log the recipient STOP request including the license key, sending DID, and recipient’s phone number.
  • The STOP response occurs at the license key level. SMS Notify! will only block messages from that same license key to the recipient’s phone number.
  • Other license keys may send to the recipient’s phone number.
RESUME

System Response: OK.

  • This will allow SMS Notify! to send messages to a recipient who previously sent a STOP command.
  • License Key with Assigned DIDs: The recipient can reply RESUME to any DID assigned to the license key that logged the original STOP request.
  • License Key without Assigned DIDs: The recipient must reply RESUME to the original DID assigned to the license key that logged the original STOP request.

Short Code System Keywords

HELP, HLP, AIDE, INFO

System Response:“Business Name”: Reply STOP to cancel. Msg&Data Rates may apply. Msg Freq per acct setup. “Business #.”

  • The default business name and number is the name and number used to sign up for the SMS Notify! account. This may be updated by contacting CDYNE.
  • The HELP response for short codes are at the license key level so you can set up multiple custom HELP responses per short code.
STOP, END, CANCEL, UNSUB, QUIT, ARRET

System Response:“Business Name”: You have opted out and will no longer receive messages from this service. “Business #”

  • SMS Notify! API will block the recipient’s number from receiving messages until the recipient sends RESUME.
  • The STOP response occurs at the license key level. SMS Notify! will only block messages from that same license key to the recipient’s phone number.
  • The reply to French keywords is the standard English reply.
RESUME

System Response: Welcome to “ProgramName”. Reply STOP to cancel. Reply HELP for help or call “ProgramContact”. Msg&Data rates may apply.  Msg freq per acct setup. Pwr’d by CDYNE.

  • Shared short code system messages will contain “Pwr’d by CDYNE.” Dedicated short code messages will not.

Contact CDYNE for more information about short codes.

Test SMS Notify! API for free.

1 view

Receiving SMS Messages with Short Code Keywords

A short code keyword is a unique one-word phrase that identifies a business, product or service. Keywords allow multiple  businesses to run unique campaigns on the same short code. Likewise, a business using a dedicated short code can differentiate communications with multiple keywords. For example, your dentist places a sign in the waiting room that says, “Text SMILE to 55512 to get appointment reminders.” In this example, “SMILE” is the keyword, and “55512” is the short code. By texting SMILE to short code 55512, the patient is opting in to receive appointment reminders. Using the same short code, the dental office may run a separate promotional offer. For example, “Text WHITE to 55512 for $25 off teeth whitening.” In this way, patients choose the interaction they wish to receive from their dentist. Communication with short codes and keywords give businesses great flexibility and responsiveness when engaging their customers, patients, or clients with text messaging. Here are guidelines and rules to consider when using keywords:

Select User Friendly Keywords

Keep it short – A short keyword is easy to remember.

Make it memorable – An easy to remember keyword will generate a better response.

Use a single word – SMS Notify! will match the entire message when checking for incoming keywords. If an incoming keyword is followed by any characters, a match will not be made.

SMS Notify! Incoming Keyword Rules

  • Only 1 instance of keyword per short code
  • Keyword cannot be a system keyword (e.g., STOP, HELP, ect.)
  • Keyword must be at least 3 characters long
  • Keyword cannot be a typical SMS response (e.g., sure, yes, thanks, monday)
  • Keywords are not case sensitive; ‘THIS’ is the same as ‘this’ and ‘ThIs’

Using PostBackURL to Capture Incoming Keywords

Developer’s can set up automated responses to incoming keywords using the SMS Notify! API PostBackURL system. When a keyword is assigned to your short code, CDYNE can also assign a URL or webpage you designate. Set your application to look for the variable SMSResponse=1, which is posted when a message is sent to your short code, or when a response to your outgoing message arrives. PostBackURL data is posted behind the scenes, and is not visible on your webpage. Program your application to capture the PostBackURL variables that are passed to your webpage from SMS Notify! API.

Contact CDYNE for more information about short codes.

Test SMS Notify! API for free.

5 views

CDYNE Phone Notify! API StatusChangePostURL

One of the great features of CDYNE Phone Notify! API is the ability to customize call logic exactly the way your business needs it. It handles complex call scripts, responds to call actions in real time, and can be programmed to deliver relevant communications exclusive to your customers or clients. For many Phone Notify! applications, it is important to know when a call is placed, the call status has changed, the call is finished, or when a call is received. The best way to automate this process is to use the StatusChangePostURL command. With a StatusChangePostURL in place, Phone Notify! will post phone call information to a URL you designate.

What information does the StatusChangePostURL command post?

Phone Notify! utilizes a command called StatusChangePostURL, which will post back information about the phone call to your server. Once you’ve created a web page to handle postbacks, the URL can be set to recieve this information automatically. The following values are posted:

  • QueueID – Contains the ID of the Call
  • ResponseCode – 1 = Call Answered, 2 or more – Call Unanswered (see all status codes here)
  • StartTime – Start time in Universal Time (UTC)
  • EndTime – End time in Universal Time (UTC)
  • Duration – Call Length in Seconds
  • machinedetection – Currently only HUMAN, MACHINE, or FAX
  • AC – Contains a status code – this is for advanced problem solving with Tech Support
  • digitsdialed – contains all the digits dialed during a call
  • incoming – contains true if the call was an incoming call
  • [Any Variables you collected] – any additional variables that you collected during the call

 

Where do I assign the StatusChangePostURL?

There are three scenarios for assigning the StatusChangePostURL command. The first is when using the Advanced methods of Phone Notify! API. You can pass it in the NotifyPhoneAdvanced and NotifyMultiplePhoneAdvanced programming operations. Each operation contains a parameter named, “StatusChangePostURL” where the URL can be input. A URL must be in lower case.

The Basic methods of Phone Notify! do not contain the “StatusChangePostURL” parameter, so an alternative is to assign the URL in the script. In this case, you can include the URL within your script by using the ~StatusChangePostURL(posturl)~ command. This should be placed at the beginning of your script.

The last scenario includes incoming phone calls. To set the URL in this case, you can log into your account online and specify a URL for each dedicated phone number assigned to your license key as shown in the image below:

For more information about CDYNE Phone Notify! API, please contact an account representative at 1-800-984-3710, inquire by email, or initiate a chat for more details.

Or sign up for a free trial license key to test CDYNE Phone Notify! API.

Developers find CDYNE Phone Notify! API integration details on the CDYNE developer’s wiki.

 

 

 

0 views

SMS PostBackURLs Two Ways

For many SMS Notify! applications, it is important to know when an MT* message is sent, when a response to that text message is received, or when an MO* message is received by your application. In each scenario, SMS Notify! will alert your application when you use the PostBackURL feature. This can be helpful for storing information in a database, or responding with another message. The PostBackURL is a web page you assign where CDYNE will post back the specific information about the MT or MO SMS messages.

MT (Mobile Terminated) PostBack Fields

If you specify a PostBackURL in your SMS outgoing request, the following fields can be programmed to postback when a message is sent:

  • SMSSent – Always set to “1.”
  • MessageID – A unique identifier that matches the initial MessageID from your outgoing SMS.
  • ReferenceID – This is populated if you set a reference id in your outgoing request.
  • FromPhoneNumber – This is the number that sent your outgoing message.
  • ToPhoneNumber – This is the number you sent the SMS to.
  • SentTime – UTC Date when the message was sent.

 

MO (Mobile Originated) PostBack Fields

If you specify a PostBackURL in your SMS outgoing request, or CDYNE assigned you an SMS DID – the following fields can be programmed to postback when a response message is returned, or when an MO message is sent to your DID.

  • SMSResponse – Always set to “1.”
  • MessageID – A unique identifier for this response. This will come as a GUID.
  • MatchedMessageID – A GUID that is populated when the response matches a previous message.
  • ReferenceID – This is populated if the response matches a previous message and you set the ReferenceID field in your outgoing SMS.
  • FromPhoneNumber – This is the number that sent the response.
  • ToPhoneNumber – This is the Local SMS Number that received the message. If you have an assigned DID number from CDYNE, this will be that number. Otherwise it will be a random number from our Phone Number pool.
  • ResponseReceiveDate – UTC Date when the message came in.
  • Message – This is the incoming SMS Text Message body.

 

Shared Numbers or DIDs – How to Assign the PostBackURL

There are currently two flavors of CDYNE SMS messaging: shared and dedicated phone numbers. With shared numbers, your application can send SMS messages, and receive responses to those messages. Shared numbers cannot receive MO (Mobile Originated) or customer initiated/inbound text message to your application. You’ll need a DID for MO messages.

You can order a DID through a CDYNE Account Representative. When they assign the DID to your SMS license key, they can also assign the PostBackURL at that time. Alternatively, you can log into your account online and specify a URL for each dedicated phone number assigned to your license key as shown in the image below:

By doing so, all messages sent to or from the DID will be captured with the PostBackURL.

When using CDYNE’s bank of shared phone numbers, you can assign the PostBackURL in the SimpleSMSSendWithPostback or AdvancedSMSSend methods. When using a DID, if the PostBackURL is already assigned, you do not have to pass it in the SimpleSMSSendWithPostback or AdvancedSMSSend methods. If you do put in a PostBackURL, it will override the system URL.

* MT (Mobile Terminated) message – an outgoing message sent from your application. It is a text message that terminates on a mobile device.

* MO (Mobile Originated) message – an inbound message sent to your application that is initiated by the customer (rather than a response to an MT message already sent out). It is a text message that originates from a mobile device.

 

For more information about CDYNE SMS Notify! API, please contact an account representative at 1-800-984-3710, inquire by email, or initiate a chat for more details.

Or sign up for a free trial license key to test CDYNE SMS Notify! API.

Developers find CDYNE SMS Notify! API integration details on the CDYNE developer’s wiki.

1 view