All articles

An error vocabulary that turns a technical result into a useful next step

A user sees “error,” clicks again, and cannot tell whether anything changed. In your SimAggregator client, separate the observed condition from the available action. This is a local interface vocabulary; it does not replace documented API replies or create platform statuses.

For each situation, record what is known, what remains unknown, what the user can do, and what the application will check. A missing reply means uncertainty about the outcome, not automatic permission to repeat a purchase. An unavailable selection and a lost connection need different explanations.

Link the technical record to a readable sentence through your application's internal reference. Give translators context instead of isolated words. “Try later” is unhelpful when an active button still looks like a required next step.

Test the vocabulary with synthetic scenarios. A teammate who has not read the code should explain what has happened and what action is offered. Preserve the original technical cause in protected diagnostics so clearer wording does not erase distinctions needed during investigation. Review all supported languages whenever the suggested action changes.

Your first number in a minute

Signing up takes a minute, topping up a couple more, and the code arrives in 20 seconds.

Buy a number
No subscription feeCancel with a refund in the first hour