What your SMS client can promise: separate your actions from external outcomes
“Registration guaranteed” can appear in an interface before anyone asks what supports it. If your product uses SimAggregator, receiving a message and completing a third-party flow remain different outcomes. Promises should match the part your team actually controls.
List your own actions: display known data, preserve local history, explain uncertainty, and provide a support path. Include an item only if it is implemented and verified. Alongside it, note the external conditions on which the next step depends, without offering your own guarantee for them.
Review buttons, errors, and emails as well as the main page. “All done” after an SMS arrives may imply more than intended. Clarification belongs beside the relevant result, not buried in a long document.
Explain the boundary to translators. Shortening a sentence must not remove its condition or turn a possibility into certainty. Revisit wording with support after product changes: actual questions often reveal which words customers interpret differently from developers. Check that the four language versions make equivalent promises, even when their wording is naturally different.