For an application or website to send messages, the developer must create an information channel, which must be signed by the user who will receive the messages.
If a user ceases to be a channel subscriber, no message will reach him, that is, it is the user who decides whether or not to receive messages from a channel simply by becoming a subscriber or by canceling the subscription.
The creation of a channel must be performed by the developer on the Followzup website, while the subscription of a channel must be done by the users in the APP Followzup installed on the mobile device.
Applications can make use of different channels to send messages, depending on the purpose of each one (customers, suppliers, employees, managers, support teams, etc.).
In situations where more than one application makes use of the same channel, it is opportune to develop a gateway that coordinates the communication with webzervice Followzup and meets the requests of the various systems, thus maintaining control of the requests.
Creation of a channel must be performed on the Followzup website by a user identified by your email account, who will be the channel owner . There is no possibility of two or more developers sharing ownership of the same channel. For security, if there is a need to share possession of a channel, one can make use of institutional email accounts, with shared access.
In the inclusion of a channel, the developer must inform the following attributes:
|Tag||Required|| The tag is the channel ID in Followzup. The tag must be between 3 and 32 characters, and can be composed of uppercase letters, lowercase letters, numbers and the character “-” (hyphen). It should also start and end with an alphanumeric character.
Examples: “XYZ-Customers”, “test12345”, “go-Support”; “9988776655”, “KwY123456h”, “Australia”.
Reserved Tags: Tags up to 8 characters are reserved by the system, and can be made available to the developer upon request. If you are interested in registering a reserved tag, please make your request through the contact page.
|Presentation text||Optional||Text up to 200 characters, which is displayed along with the tag in the search results displayed on the mobile device to assist users in choosing the channel to be signed.|
|Welcome message||Optional||Message with up to 200 characters automatically sent to the user when the channel is signed, and can also be a warning or an orientation for the new subscriber.|
|Welcome message URL||Optional||HTTP address sent with the welcome message, so that the user can click on the message and open the URL entered in the browser of the mobile device.|
|Response message URL||Optional||HTTP address for sending user messages from your mobile device through the text box at the bottom of the channel's message list. This text box is only displayed when this URL is entered.|
|Private Channel||Flag||Private channel indicator, causing the channel to only appear in search results when the searched argument is identical to the channel tag, including uppercase and lowercase letters. Once signed, the private channel has the same way of use as any other channel.|
|Private Code||Optional||Secret code to be informed by the user in the mobile device when signing a private channel.|
|Channel Icon||Optional||Representative image of the channel, displayed along with the tag in the channel list and search results. After upload, the image is converted into square format.|
After creation, Followzup generates a pair of asymmetric keys (RSA) for exclusive channel usage, and the developer must download the API, where the RSA public key is stored. Asymmetric keys are used in the process of encrypting the transmitted data.
Another information generated in the creation of the channel is its internal identification in Followzup (Channel-ID), consisting of 12 alphanumeric characters beginning with the letter “c”. All letters contained in a Channel-ID are lowercase letters (example: c03wfcr23k1p).
The API that contains the cryptographic key must be stored securely on the application server. In case of any breach of confidentiality in the API storage, the developer can generate a new asymmetric key pair and proceed with a new download.
Ownership of a channel can be transferred between users and must be performed on the Followzup page, where the new owner's email is indicated, which in turn receives a message in their electronic mail requesting confirmation of the transfer of ownership of the channel . Once the transfer of ownership has been confirmed, it can not be undone by the former owner.
In case of need, the channel can be suspended by the developer. A suspended channel remains available to the application as if it were an active channel, including for sending messages. The difference is in the interruption of the process of transmission of the messages to mobile devices, as if a tap were closed. Once reactivated, Followzup restarts the process of broadcasting repressed messages during the sleep period, which are still within their lifetime.