@yanokwa, this was all plain text. I noticed when using a shared short code (Running on MTN Uganda) we found if an SMS exceeded 120 characters it would be split into 2 separate messages. Our dedicated short codes on Safaricom Kenya and Airtel Malawi did not have a similar issue. I then just restricted the character limit to 120 for all messages for uniformity and provided a template to be used when sending from our office MIS (bespoke) to user phones that kept it at 120.
All users used Android devices with no less than 2GB RAM running KitKat or better.
We were using an API provided by Infobip: https://dev.infobip.com/getting-started although I doubt it was the cause since we used it across the board.
From this: Long story short, SMS is not a great foundation for data transport. We can be sure that messages are sent, but we can't be sure they are received. And that means that with SMS we risk data loss. Given that, we probably should have a way to send data via a more reliable transport even if we could generate duplicate records.
My reply is this: I would imagine there will be a platform for collecting all traffic information. Which would include the sender, receiver and status of the message sent (Delivered, Pending, Not Delivered); this would be the log of activity and would not necessarily provide a 'message status' to sender or receiver. It would however provide a starting point for data cleaners to sort duplicate entries.
Having as many settings that can be altered an changed only after entering admin password sounds good to me, it is a small measure towards data protection if we can limit as much as possible human error at time of form submission.