Marketing site
This website — product pages, guides, help articles and the console entry point.
Static pages served from a CDN. If you can read this, it is up.
What each component does, how it fails, and where a change is announced — plus the fastest way to get an answer when something looks wrong.
This website — product pages, guides, help articles and the console entry point.
Static pages served from a CDN. If you can read this, it is up.
The authenticated area where connections, keys, suppression and logs are managed.
Availability depends on the API below, because the console reads and writes through it.
The HTTP interface your own services call to send messages.
Authentication failures and validation errors are returned by the API rather than hidden — a rejection is a response, not an outage.
Provider receipts collected and normalised into a single status. SMS channel.
Receipt arrival depends on the provider and the destination network; a missing receipt is not the same as a failed send.
Receipt events pushed to the endpoint you configure.
Treated as best-effort rather than guaranteed. Reconcile against the message log.
The record of what was sent, to whom, with which status.
The authoritative answer to “did we send it?” — read it rather than guessing.
Each component exposes a health signal that our own monitoring checks, so a failure is usually detected before it is reported. If you saw it first, that is worth telling us — it means a signal we rely on needs tightening.
When something ships that changes how the platform behaves, it is written up in the changelog with a date. If you believe something is broken now, contact support@mail.whaleal.com and include the message reference or the time window — the message log is the fastest route to an answer, so a reference shortens the loop considerably.