The Store Concept

For developers who will not be creating any additional stores aside from your original production store, this section is not that important. For those developers who will be creating on.

When CRM Text started, we sought to rectify the challenge of routing text messages on one specific short code. The only way to do this properly was to include a keyword in every text message that was sent from a mobile subscriber to a business. That isn’t very efficient. The SMS API is built on the store concept. Think of it like franchises or containers even. Each franchise has a unique phone number, right? Right!

In our concept, each store, or franchise, must have a unique keyword. We call that keyword the primary store keyword. The CRM Text SMS API guarantees message routing by binding a mobile number to one of our communication short or long codes after the subscriber opts-in. The opt-in will occur within two scenarios:

Handset Initiated
In this instance, a mobile subscriber will send an opt-in keyword to our marketing short code, 444999. They will receive an opt-in confirmation on our communication short code. The mobile subscriber will be binded to that communication short code such as 24411 and all communications between the store and the mobile subscriber will occur on this short code for the life of the opt-in. If the mobile subscriber opts-out, the binded short code will be released for the mobile subscriber to use with a different store.

Non-Handset Initiated
The CRM Text SMS API allows developers to opt-in mobile subscribers through our API without a keyword being initiated by the mobile subscriber. In this instance, the mobile subscriber will only receive an opt-in request message from a communication short code.
Once opted-in, the mobile subscriber can send messages to the store on the assigned short code and those messages will be received to the appropriate store. But what if the mobile subscriber opts-in to two of your stores? Simple. We will assign another communication short code to the mobile subscriber for that store. Any communications over that assigned short code will only go to the new store.

For a simplified example of how we route messages to multiple stores lets examine a CRM Text Client, Dominion Dealer Solutions, which works with thousands of automobile dealers providing CRM, marketing and fixed operations SaaS. The CRM Text store concept allows Dominion to create one store for each of its unique auto dealership Clients so that they can share CRM Text short codes while ensuring that messages sent and received are routed to their appropriate destination. The graphic below illustrates our patented approach.

Once a mobile subscriber opts-in to one of your stores, we bind that mobile subscriber’s number to that store with one of our short codes. That bind will remain in place for the life of the relationship or until the mobile subscriber opts-out.

If your company manages multiple franchises or Clients, the CRM Text SMS API provides flexibility in managing message routing with store creation.