Error handling
One of the major pain points of the current product was dealing with errors in the source file (CSV / XLS) uploaded to the system. In fact, error handling wasn't performed at all within the product. If the file filled incorrectly the user would have to wait for the algorithm to finish its process. At the end of the process when a file was found as an incorrect file, the user should re-upload the same file without errors and again wait for the algorithm to finish the process. It's a very long and frustrating process.
As a solution, what I have suggested is to deal with the errors even before the algorithm receives the file, thus allowing the user to fix them already within the product and not within the source file.
One of the major pain points of the current product was dealing with errors in the source file (CSV / XLS) uploaded to the system. In fact, error handling wasn't performed at all within the product. If the file filled incorrectly the user would have to wait for the algorithm to finish its process. At the end of the process when a file was found as an incorrect file, the user should re-upload the same file without errors and again wait for the algorithm to finish the process. It's a very long and frustrating process.
As a solution, what I have suggested is to deal with the errors even before the algorithm receives the file, thus allowing the user to fix them already within the product and not within the source file.
Yotpo, Email & SMS multi-message
App UX/UI. Prototyping. Usability Testing
