

The settings screen: account credentials, the sender name, and the consent rule.
An order email can sit unread for a day. A text is read in minutes, which is why
“has it shipped?” is the question shops answer most often.
This plugin sends an SMS through your Meser 10 account when an order reaches a
status you choose. You write the message for each status, and statuses you leave
empty send nothing.
You need a Meser 10 account with SMS enabled, and both the API key and the
numeric User ID from it. Sending needs both – the key on its own is not enough.
A sender name has to be approved on the Meser 10 side before it will show on the
handset instead of a number.
Messages are charged per segment by Meser 10. A message in Hebrew or with an
emoji fits 70 characters per segment rather than 160, so the settings screen
shows the segment count under every template you write.
Order status updates are usually treated as service messages rather than
marketing, but the rule differs by country. There is a setting that restricts
sending to customers who ticked a consent box at checkout, for shops whose rules
require it.
This plugin sends text messages through the Meser10 platform, an email and SMS sending service. A request is made only when an order reaches a status you have written a message for, when the shop alert is switched on and a new order arrives, or when you press the test send button. What is sent is the recipient’s mobile number, the message text with its placeholders filled in from the order, the sender name, and your Meser10 API key and User ID for authentication. No other external service is contacted; the w3.org and xmlsoap.org addresses in the code are XML namespace identifiers, not requests.