47SMS
Prepared isn't delivered.
Know the difference.
47SMS is being restored for team communication that distinguishes preparation, approval, provider response and delivery. The aim is a clearer account of what happened to each message.
Being restored · No public delivery service
Who it is for
For teams designing communication workflows around consent and observable delivery events.
Have a task in mind?
Tell us what you need to achieve and what you already have. Start with a description, without private files or credentials.
Availability, examples and technical limits
47SMS
A clearer path from preparing a message
to knowing what happened to it.
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.
Earlier software is being restored under the working name 47SMS. No public message-delivery service is available.
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.