Agents using the respond.io mobile app in low-connectivity environments — commuting, at client sites, in areas with unstable cellular coverage — cannot reliably send messages when their network drops. When connectivity is lost, send attempts silently fail: the message disappears from the compose field, no offline notification appears, and the agent has no confirmation of whether their reply was delivered.

When an agent sends a message while offline, the message should be queued locally and delivered automatically once connectivity is restored — with no additional action required. The message should appear immediately in the conversation with a clear pending indicator, transition to sent once delivered, and show a visible failure state with a retry or discard option if delivery permanently fails.