For many people worldwide, SMS-enabled devices have become irreplaceable tools to stay connected with the outside world. Immediately communicating with customers, clients, employees, and members therefore makes SMS an extremely powerful messaging tool for businesses. When considering a short code, the following preliminary questions will be a helpful in evaluating your mobile communication goals:

• What is the mobile communications budget?
• What is the timeline to launch a mobile communications campaign?
• What are the text message volume needs?

There are two short code options for companies to engage their audiences with text messaging: shared short codes and dedicated short codes. Which one is the best choice for your business?

Shared Short Code: Lower Cost, Quick Launch, & Shared Volume

Shared short codes allow a business to run a campaign on a short code that is used by other companies. The primary benefit is a savings in both money and time. Shared short codes cost less than dedicated short codes because a single shared short code is used across various text messaging campaigns run by multiple companies. Dedicated short codes typically cost $500 per month to lease with a $3,000 carrier application processing fee, plus the cost to send each message. Tapping into a short code that is already active saves you the time of obtaining and provisioning a short code yourself (typically an 8-10 week process or more) – plus you can launch your text messaging campaign almost immediately.

Separate campaigns are able to run simultaneously on a single short code with the use of keywords. A keyword is a unique phrase assigned to a short code that identifies a business campaign. For example, Dr. O’s dentist and Sal’s Pizza both use short code 55616 to communicate with their customers. Dr. O uses the keywords SMILE and CLEAN for two separate campaigns: texting SMILE to 55616 subscribes the user to appointment reminders; and the CLEAN keyword designates a special offer Dr. O’s office is running this month. Sal’s Pizza uses CHEESE so subscribers can subscribe to delivery specials. The unique keywords allow businesses to share the use of a short code.

Dedicated Short Code: Brand-Friendly, Better User Experience & 35 Dedicated Messages/Second

Dedicated short codes are an excellent mobile tool for businesses requiring sole use of the short code. While it costs more money and time to launch a dedicated short code, there are certain advantages to consider: they are brand-friendly, offer a better user experience, and handle a higher throughput of text messages.

A short code can become part of a company’s brand strategy particularly with a vanity short code, which allows you to specifically request the numbers of the short code. This might be used to mimic a zip code, or an associated word (e.g., 76453 spells SMILE). Vanity short codes cost $1,000 per month to lease, whereas a random short code costs $500 per month and is randomly assigned.

The second advantage of a dedicated short code is better user experience. With a shared short code, the user will typically have to text a keyword, and then an action word to subscribe. For example, Dr. O wants to run two campaigns with the keyword SMILE. This first is for appointment reminders, as mentioned above, and the second is appointment confirmations. Since both use the keyword SMILE, each campaign should be designated with an action word. The user would text SMILE RMD to set up SMS appointment reminders. When they receive the reminder (e.g. “Your appointment is 3/30/10. Txt SMILE Y to confirm”), the user needs to text the keyword SMILE plus the action word Y for yes in order to route the response to the correct company. With a dedicated short code, this is not necessary.

A dedicated short code can send up to 35 text messages per second. On a shared short code, this volume is shared among the number of companies using a single short code.

CDYNE provides U.S. and Canadian short codes for use with the SMS Notify! API – SMS Notify! is a secure two-way SMS Gateway that facilitates your business communications with a developer-friendly API.

Get more short code information, or test today for free.

Previous blog: Text Messaging: Almost a Guaranteed Read

Next blog: Dedicated Short Code: Steps to Launch

SMS Notify! supports text messaging worldwide with the potential to reach over 5 billion people globally.  You can reach this network of mobile users by purchasing a UK DID for assignment to your SMS Notify! license key. When you pass a phone number with 011 + the country code, the API will automatically use the UK DIDs assigned to the license key for sending the text messages.

Unicode Support

Another great feature is Unicode support. Unicode is a standard for handling text in all writing systems, and allows you to send text messages in many languages. It provides a unique number for every character, and allows text data to pass through many systems regardless of the platform, computer program, or programming language used. You should note that that the receiving device determines which characters it will display. While it may support Unicode, it may not display all Unicode characters.

Unicode covers any language that can be written in a script (e.g. Latin, Greek, Cyrillic, Han, etc.), which is an inventory of graphical symbols.  For example, a single script such as Latin may be used to write hundreds of languages (e.g. English, Spanish, and West Germanic), whereas a single language like Japanese may use multiple scripts including Han, Hiragana, and Katakana.

Which Encoding Does SMS Notify! Support?

To send Unicode messages using SMS Notify!, set the IsUnicode parameter to True in the AdvancedSMSSend method. The API supports UTF-16, which is a character encoding for Unicode. Unicode text messages are 70 characters per transaction. Non-Unicode messages are 160 characters.
By default the IsUnicode parameter is set to False. In this instance, SMS Notify! supports Latin-9, or ISO/IEC 8859-15 encoding which are 160 characters per transaction.

A Couple of Tips for Sending International Text Messages

• 011 + country code + phone number in the PhoneNumber parameter when sending messages outside of the U.S. and Canada. SMS Notify! will automatically send from your International DIDs.
• Some international carriers use spam-filters which block messages based on content. Check out the Carrier Restrictions tab (Excel doc) for more details.

Contact CDYNE for more information about Extended International SMS coverage.

Test SMS Notify! API for free.

Short code text messaging is an excellent way to reach your customer and consumer base with relevant and time-sensitive information because text messages have a sense of urgency compared with other methods of communication. But it is important to note that text messaging is a permission-based medium that requires the sender to obtain the recipient’s consent to send SMS to their handset. Because consumers pay to receive text messages, the wireless carriers regulate the industry and create rules for interacting with recipients through SMS. CTIA is the International Association for the Wireless Telecommunications Industry that monitors text messaging for the carriers and issues violation notices. Non-compliant text messaging can result in citations, suspension, or termination of your short code campaign. The CTIA published a Compliance Handbook, effective June 2012, which clarifies the industry compliance rules, opt-in, and mobile campaign deployment.

Call to Action

A call to action is is an opportunity for a business to successfully capture a mobile number and an invitation for a consumer to provide their cell phone number in order to subscribe to content. Several examples include on-site signage, print advertisements, or a web page. The wireless industry requires that a call to action contains five pieces of information including:

Product description and quantity

What will the recipient receive by providing their cell number? And how often? (e.g. Receive account alerts 2-3/month)

Program identification

What is the name of the business, or the text messaging initiative? (e.g. Dr. O’s Medical Alerts)

Opt-out instructions

Include the keyword in bold that recipients must text to stop receiving messages. (e.g. Text STOP to unsubscribe)

Message and data rates may apply

Customers should know that carriers may charge them for these text messages. (e.g. Message & Data rates may apply)

Links to privacy policy and terms and conditions

Dedicated short code users must create a privacy policy. Shared short code users can use the policy drafted by CDYNE for each shared short code. Terms and conditions must be posted online. (e.g. Privacy Policy and Terms & Conditions)

Opt-In: Even if You Already Have a Business Relationship

It’s worth mentioning here that existing business relationships and the purchase of opt-in lists do not automatically allow a company to send text messages to those mobile numbers. For example, if you already communicate with customers via email, you must still get their permission to receive text messages. Or if you collect mobile numbers during an online transaction or other method – this does not count as an opt-in. Automatic enrollment in multiple programs is not allowed, and the CTIA requires a dedicated opt-in for each program. The CTIA  Compliance Handbook outlines four examples for capturing opt-in. In all opt-in scenarios, consent to receive text messages must be clear and accurate at the time the mobile number is given.

• Enter a phone number online,
• Click a button on a mobile Webpage,
• Send an MO message containing an advertised keyword, or
• Sign up at a point-of-sale location

SPAM

The reason behind all the rules and regulations is to eliminate unsolicited text messages, or SPAM. The CTIA Compliance Handbook defines unsolicited messages as, “All messages delivered before a user opts in or after a user receives confirmation of opt-out, and any message delivered in excess of the quantity advertised, are considered spam.”

For more information about the laws that address SPAM, read the FCC’s guide titled “Spam: Unwanted Text Messages and Email.”

CDYNE supports only the sending of opt-in text messages from the SMS Notify! API for both short codes and DIDs.  In an effort to ensure that all text messaging sent through CDYNE SMS Notify! API is conducted responsibly, please read the Responsible Use Guidelines.

Contact CDYNE for more information about short codes.

Test SMS Notify! API for free.

A valuable benefit of using PAV is to check whether or not an address is deliverable in order to receive barcode discounts. PAV includes DPV (Delivery Point Validation), which is the USPS process for verifying deliverability. A delivery point is a single point at which mail is delivered (e.g., a mail slot, PO Box, or mailbox). It is not the same as a street address. In fact,  an address can contain multiple delivery points such as an apartment building or business office with numerous suites. The USPS defines DPV as a specific set of digits between 00 and 99. Combined with the ZIP+4 code, a delivery point gives each deliverable address a unique identifier. Delivery points are encoded in barcodes, which allows automated sorting for the USPS.

Developers can utilize PAV to return detailed mailing industry information including DPV data returns. This data is accessed when using the “VerifyAddressAdvanced” method and setting the “MailingIndustryInfo” parameter to True. The following are example address input and outputs.

Input: 505 independence parkway, suite 300, chesapeake, va, 23320

Output: 505 INDEPENDENCE PKWY STE 300, CHESAPEAKE, VA, 23320-5178

• DeliveryPoint = 75
• DpvConfirmationIndicator = Y
• DpvCrmaIndicator = N
• DpvFootnote1 = AA
• DpvFootnote2 = BB
• DpvFootnote3 = Null

In this example, the unique identifier and delivery point is 23320517875 (ZIP+4+delivery point). PAV confirms this address does have a delivery point and mail can be delivered there (DpvConfirmationIndicator = Y). The DpvCrmaIndicator = N means that the address is not associated with a valid CRMA, which stands for Commercial Mail Receiving Agency, and is also known as a Private Mailbox (PMB) operator. The DPV footnotes indicate the address has been matched to the ZIP+4 file (AA) and all components of the address were matched to DPV (BB).

The keys below show all available PAV data results.

DPV Confirmation Indicator Key

1. Y – Address was DPV confirmed for both primary and, if present, secondary numbers
2. D – Address was DPV confirmed for the primary number only, and secondary number information was missing
3. S – Address was DPV confirmed for the primary number only, and secondary number information was present but unconfirmed
4. N – Both primary and, if present, secondary number information failed to DPV confirm

DPV CMRA Indicator Key (CMRA = commercial mail receiving agent)

1. Y – Address was found in the CMRA table
2. N – Address was not found in CMRA table

DPV Footnotes Key

1. AA – Input address matched to the ZIP+4 file
2. A1 – Input address not matched to the ZIP+4 file
3. BB – Input address matched to DPV (all components)
4. CC – Input address primary number matched to DPV but secondary number not matched (present but invalid)
5. F1 – Input address matched to a Military address
6. G1 – Input address matched to a General Delivery address
7. N1 – Input address primary number matched to DPV, but address is missing secondary number
8. M1 – Input address primary number missing
9. M3 – Input address primary number invalid
10. P1 – Input address missing PO, RR, or HC box number
11. P3 – Input address PO, RR, or HC box number invalid
12. RR – Input address matched to CMRA and PMB (postal mailbox) designator present (PMB 123 or # 123)
13. R1 – Input address matched to CMRA but PMB (postal mailbox) designator not present (PMB 123 or # 123)
14. U1 – Input address matched to a unique ZIP code

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.

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.

Happy Halloween from everyone at CDYNE.

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.

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.

More than 90% of the 140 million Postal Service’s delivery points are classified as residential. RDI, or Residential Delivery Indicator is a USPS delivery type status that flags an address as residential or business. Because some delivery companies charge more for residential deliveries, the biggest advantage of knowing the RDI for an address is the ability to shop for the most cost-effective delivery option. Some of the benefits of identifying an address as residential or business include:

• Reduce residential delivery surcharges
• Lower shipping charges by price-shopping for a service that meets your needs
• Enhance Customer Relationship Management (CRM) by demonstrating efficient and accurate shipping practices
• Identify shipping patterns to improve operational efficiency
• Providing online rate-shopping services on websites

CDYNE PAV API includes an optional RDI flag free of charge. It can be returned with VerifyAddressAdvanced method by setting the parameter “ReturnResidentialIndicator” to “True.” If the address is a residence, PAV will return “N,” and if it is a business, PAV will return “Y.” The following is an example showing an address classified as a business.

Input:

505 independence pkwy, chesapeake, va 23320
Return Residential Indicator: True

Output:

505 INDEPENDENCE PKWY, CHESAPEAKE, VA 23320-5178
Residential Delivery Indicator: N

For more information about CDYNE PAV, 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 PAV.

Developers find CDYNE PAV API integration details on the CDYNE developer’s wiki.