My user doesn't have permissions to consult and/or manage some options:
The display of the application options are configured by roles and users. If you do not have permission to manage products, you must request permissions from the technical support team through a ticket. Remember to include the following information: user account (username), the name of the required permission functionality (example: “Broadcast by email”, and the URL of the application.
How to create users in a workspace:
You can self-manage new users within a workspace:
Enter the application and locate the workspace in which the new user will be configured, then select the "Admin" menu (upper right), then select the "Custom users" option. Enter the information and permissions of the new account and press "Save" Make sure that the role associated with your user account has administrator permissions of the application.
Check the delivery status of a message:
To check the delivery status of messages: Enter the application and locate the workspace from which the shipment was made, then select the “Reports” option in the Menu, then select the “Sent & DRs” report. Select the parameters and press "Search" Make sure that the role associated with your user account has administrator permissions of the application.
API submission fails:
Verify that the parameters used in the call are correct: Url, instanceid, public key, and private key. If you are not sure about this information, you can request it from the support team.
To learn more about this functionality, please consult the following documentation:
- Messangi API: https://documenter.getpostman.com/view/8950262/SzKSUfvF
- MMC API: https://apidoc.mobilengage.net/
Add / remove numbers in blacklist:
You can block users by phone number and / or by email accounts. To add and / or remove users in blacklist:
Enter the application and locate the workspace in which you want to configure the users to the blacklist, select the option "Utilities" (SMS or EMAIL), enter the information by user or add a list if you want a batch process. -Make sure that the role of the account you are using has the necessary permissions for this option, otherwise consult the support staff.
Identify the id of a template:
To check the id of a configured template:
Enter the application and locate the workspace in which the template was configured, then select the option "Utils" from the Menu, then "Template" You will see the list of all the configured templates with their corresponding ID, name and text Use the "Search" field to search for the template by text or by ID. -Make sure that the role of the account you are using has the necessary permissions for this option, otherwise consult the support staff. ort staff.
Why i'm receiving two or more delivery receipts for one message?
We recomend to check on the text used on the message of the campaign, and look for a possible special character that would have cause a change on the encoding this might create more than 1 message hence for that reason more delivery receipts are being processed
Facing issues regarding Android Wallet and Google Pay
In order to use properly all of the advantages provided by the tools in our platform there is a few matters that requires being of concern.
Regarding the mobile device and the OS used by it (apple or android based), this mean that there would be some limitations that are strictly related to the mentioned point above about the used OS.
Regarding the mobile device signal and availability must be on check on what it comes to the implementation of any of these functions
You can always count on our documentation for more information at https://docs.messangi.com/docs/user-guide
SMS Enconding
There are 2 enconding used for SMS, both are GSM -7BIT (160 characters message) and UCS-2 (70 characters message, important to notice that each has its own default alphabet, if there are more doubts we recommend to check on GSM 03.38 character enconding
Concatenate messages can be achieved only if the carrier or operator allows this functionality
0x00 | 0x10 | 0x20 | 0x30 | 0x40 | 0x50 | 0x60 | 0x70 | |
0x00 | @ | Δ | SP | 0 | ¡ | P | ¿ | p |
0x01 | £ | _ | ! | 1 | A | Q | a | q |
0x02 | $ | Φ | " | 2 | B | R | b | r |
0x03 | ¥ | Γ | # | 3 | C | S | c | s |
0x04 | è | Λ | ¤ | 4 | D | T | d | t |
0x05 | é | Ω | % | 5 | E | U | e | u |
0x06 | ù | Π | & | 6 | F | V | f | v |
0x07 | ì | Ψ | ' | 7 | G | W | g | w |
0x08 | ò | Σ | ( | 8 | H | X | h | x |
0x09 | Ç | Θ | ) | 9 | I | Y | i | y |
0x0A | LF | Ξ | * | : | J | Z | j | z |
0x0B | Ø | ESC | + | ; | K | Ä | k | ä |
0x0C | ø | Æ | , | < | L | Ö | l | ö |
0x0D | CR | æ | - | = | M | Ñ | m | ñ |
0x0E | Å | ß | . | > | N | Ü | n | ü |
0x0f | å | É | / | ? | O | § | o | à |
table of 3GPP TS 23.038 version 12.0.0
Comments
Please sign in to leave a comment.