47SMS
A clearer path from preparing a message to knowing what happened to it.
Earlier software is being restored under the working name 47SMS. No public message-delivery service is available.
47SMS is being restored as a communications product for teams. The intended experience brings together permission to contact someone, message preparation, approval and delivery status, while keeping the responsibilities of each messaging provider clear.
A team communication · illustrative example
A team prepares an update for people who have agreed to receive it. The proposed workflow would check the intended recipients and permissions, obtain any required approval, then track what the selected provider reports. Preparing a message, having a provider accept it and confirming delivery are different events; the product needs to show the difference.
Where the work stands
Retained tests cover a limited configuration component. Those tests did not call a messaging provider or deliver a message. Earlier work explored several channels, but no channel is presented here as currently supported.
What remains to be proven
The complete route from an approved message to provider response and delivery status needs verification on the restored system. Provider connections and live delivery are not established by configuration tests.
Discuss 47SMS
Tell us about the communication workflow you need, without sharing recipient lists or private messages.