What shouldn’t you use SMS notifications for?

The first thing that comes to mind when thinking about sending messages from a document workflow system is sending SMSs notifications when a new case has been handed over to a user. It turns out, however, that SMSs are not the best solution for this situation. Sending e-mail notifications is much better for this purpose because emails may contain more information and have a more effective graphic presentation.

Secondly, users nowadays use many devices interchangeably. Sometimes they check their e-mails on a computer and sometimes on a smartphone. Email notifications will work equally well on both devices. Also, with AMODIT, the system works in a browser and is device independent. Unfortunately, this cannot be said about SMSs, which are well integrated with other systems.

What should you use SMS notifications for?

While email is generally the standard, I would like to show you a use case where SMSs are better. Hopefully, this will inspire you to invent your own business processes using SMS notifications.

Notifying people who do not have smartphones or accounts in the system.

One of our clients asked with the following question:

“We have a group of blue-collar workers who do not have access to a computer at work, nor do we know if they have smartphones. They also don’t have AMODIT accounts. However, we would like to send them notifications on important corporate matters, such as days off, changes in the work mode, etc. Can it be done in AMODIT? “

The answer, of course, was yes. And, even better, a working solution was delivered within an hour! The process was created as follows: First, a dictionary was created that contains the names and phone numbers of people who might need to be notified by SMS.

Second, the “SMS Notifications” process was prepared. After starting the process, the following form appears.

On this form you can enter the text for the notification. Additionally, a list of people from the dictionary appears below. You can verify the list, as well as add or remove people for this particular notification. This list and the text of the notification is stored in the system, so you can check what, and to whom, notifications were sent. The last step is to press the “Send” button.

Conclusions

As you can see, the process is very simple and functional at the same time. Of course, we could add many refinements, like a dictionary of groups that might receive messages, or a dropdown list of standard messages, etc. But this simple process met our client’s needs in a very timely and efficient manner.

Thanks to the SMS functionality built into AMODIT and the ease of defining processes, it was possible to provide a solution to a business problem within 1 hour. Read this article about SMS Communication with Clients for another example.

What could you do in one hour with AMODIT? Get inspired, register a Free Demo, and find out!