Hello Floran,

Thank you for reaching out to us.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

There is currently no option to verify the number that the customer enters into the phone field.

Please feel free to search through our feature suggestion page, and see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and it will be forwarded to our management for review.

After it's been reviewed it will be presented on the front page, for voting. Please note that it may take some time before your suggestion is brought up for voting since we receive quite a lot of suggestions on daily basis.

Hello Floran,

Since I have trouble understanding french, can you please tell me which SMS notification template sent that SMS that contained 3 sections?

Looking forward to your reply.

Hello Floran,

Thank you for clearing that up.

Can you please update the plugin with the latest version of the Amelia plugin with the new fixes applied? 

Please find the plugin folder attached and provide me with an update if the same issue persists.

Looking forward to your reply.

Hello Floran,

If your language has characters that are not in the list of GSM characters (for example ț, ć, or a dash ( – ) instead of a hyphen ( - ) - notice the length between the two), those characters convert the text from GSM to Unicode. When that happens, the number of characters per SMS segment is reduced from 160 to 70.

You can read more about this here, but in short - GSM (standard, Latin letters) messages contain 160 characters. Large messages are segmented into 153-character segments and sent individually, then rebuilt by the recipient's device. For example, a 161-character message will be sent as two message segments, one with 153 characters and the second with 8 characters.

If you include non-GSM characters like eastern European characters in SMS messages, those messages have to be sent via UCS-2 encoding. Messages containing any UCS-2 characters are limited to 70 characters and will be concatenated into 67-character message segments, even if the messages contain less than 160 characters.

So, your messages are actually split into segments, and each segment is charged as a single message. You can go to Amelia/Notifications/SMS Notifications/SMS History, and in there, you will see a column "Segments", where you will see how many segments were actually used.

The only way around this is to reduce the number of characters in the SMS template and/or remove the special characters that are not in a basic Latin keyboard.

A good tool to see how many characters are used, and if they are in GSM or Unicode can be found here, so you can use that tool to calculate the templates before creating a template. Please note that, if you're using Notification Placeholders, they won't be taken into account, but instead the value they are replaced with, so if your template looks like this:

"You booked an appointment with %employee_full_name%"

It will not be 51 characters long (the length of the template, but the length of the name that replaces the placeholder. For example:

"You booked an appointment with Aleksandar Vukovic"

So, 49 characters long.