I ran into an issue recently where an outgoing internet call wouldn’t connect, and the app just showed a generic error message. No clear explanation, no guidance — just a code.
It made me think about how we design these moments. When a call fails (a VoIP error code), the cause could be anything from a weak connection to a backend issue, but users don’t really care about the technical side — they just want to know what to do next.
How do you approach designing these kinds of error states? Do you keep it simple and friendly, or provide more detailed troubleshooting info somewhere in the UI?
Would love to hear how others handle this in their products.
