Keyword Creation & Management
The CRM Text SMS API allows for two types of keywords. When a store is created, a default opt-in keyword is given to the store as required. Or it can be entered by the developer as a custom opt-in keyword. That keyword is the primary keyword. It's important to note that the primary store keyword cannot be changed with these methods. It is used in your authorization string to administrate the store. If you do need to change it for some reason, contact Support
. The two types of keywords allowed in the CRM Text SMS API are as follows.
Opt-in keywords, when initiated by a mobile subscriber, will immediately opt them into the store that is assigned to that keyword. The mobile subscriber will thus be known as an opted-in customer of the store and CRM Text SMS API will assign a dedicated short code for the store and customer to communicate with for the life of the opt-in. Since the customer is opted-in, you now have permission to send them text messages on an ongoing basis. The opt-in keyword you create cannot be edited for compliance purposes. However, the ability exists for the CRM Text SMS API to turn off automated opt-in messages and you can listen for the keywords and respond as you wish. contact support
if this is a requirement. But be prepared to keep your message compliant.
Responder Keyword (Or TextCode)
CRM Text SMS API also provides the ability to set a keyword as a responder only. When initiated by a mobile subscriber, the responder keyword can only return one response, which comes from our marketing short code. The mobile subscriber is not converted to opted-in status and no additional messages can be sent. It is generally used for one time coupons or general information.
It’s important to also note that you can control keywords within your application as well, but only AFTER the customer has opted-in. If you want to do responder games or surveys, use the opt-in keyword as your first path to get the mobile subscriber opted-in. Once done, you can assign keywords outside of the CRM Text SMS API system because the Customer is already opted-in to your store. You can use the callback listener to look for the keywords you want to respond to.
For example: Customer opts-in and you want to do a back and forth message. After opting in, the Customer will be assigned to your store on only one short code. So you can ask them to reply GREAT and then you can deal with that response as you wish after we post it to your callback URL.
The three API Calls in the Keyword Creation & Management section consist of:
This call allows you to create a responder or secondary opt-in keyword for a store based on your authorization string. If you create a responder keyword, you have two options available to you to generate the response to the mobile subscriber. You can listen for the keyword and respond on your own. Or, you can allow CRM Text to automate the response by using the method mentioned next.
This call allows you to edit the content of a responder keyword only.
This call sets allows you to delete a responder or secondary opt-in keyword.
Other Important Considerations
- We do not allow keywords that are 3 characters or less or any keyword that is all numbers. Should you need a keyword that fits that description email us at support
- Phones auto correct things. A keyword like FINDMYDOG is going to auto correct to Find My Dog. Try shortening keywords. FMDOG or FMD1 will get better opt-in results.
- If you select a keyword type of 5 for responder keyword, when you edit the keyword we require both the optinmsg and nonoptinmsg parameters when editing the keyword.
- We do not limit the number of keywords that each store can contain, but we do charge for keywords. So if you aren’t using a keyword it might be a good idea to delete it from the store.
- When considering content for your keyword, we support up to 1600 characters in one text message. However, we do advise you use less than 160. Some carriers will break up your text message if it is longer than 160 characters.
- Once you create a store, the primary store keyword you created with it cannot be made into a secondary store keyword. If this is an issue contact support