Slack
Slack’s error handling is pretty streamlined. Either the error message or ‘check network’ suggestion appears, then comes a button to retry executing the action, the process is rerun and we see either success or another failure. The tone throughout the error states are friendly and the process is very succinct and efficient. This reflects the company’s prioritization of workplace retention as the teams want to handle any sort of communication errors with urgency.
Uber
Uber’s error handling strategy is complete communication and transparency with the user. This means that the user is notified, in real time, when their ride is cancelled, when a new driver is being found, and how long it may take. This communication ensures ride completion even in unforeseen circumstances as the constant communication builds extreme trust with the user.
Banking Apps
Most banking apps have a similar way of addressing errors, specifically those actually committed by the users or perceived to have been committed by the users. For example, my bank will always send me a text message after a large purchase, and even sometimes deny the purchase, assuming it is fraudulent. I will have to text back to verify the purchase and retry for it to go through. Similarly, I will get notified if I accidentally enter incorrect information while trying to login to my account. Both of these features in the error handling process truly does build trust which is possibly the single most important thing a bank wants from its users.
