Send it later, and never too late.
Schedule a reminder for when it is useful and give it an expiry. If it cannot be delivered before then, it is marked expired, not sent late.
What you get
One-time scheduled sends
Set send_at on a transactional message and Hopwire sends it at that time.
Cancel before it goes
Cancel through the API or the explorer until the message is handed to a provider.
Expiry that counts from the right moment
Immediate sends count from acceptance, scheduled sends from their scheduled time. Retries and fallback never extend it.
Uncertainty surfaced, not hidden
When a provider does not answer, the message is marked unknown and never resent blindly.
Recurring schedules
At launchRepeat sends with explicit time zones and clear rules for daylight-saving changes.
Quiet hours
At launchHold non-urgent messages until the recipient's local daytime.
Questions
Can I schedule OTPs?
No. OTPs go out as soon as they are accepted. Scheduling is for transactional messages.
What is the longest expiry?
Three days for transactional messages, one hour for OTPs.
What does unknown mean?
The provider did not answer, so nobody can tell if it accepted the message. Hopwire stops instead of risking a duplicate.
Related
- NotificationsAvailableAppointment reminders, order updates and account alerts on WhatsApp and SMS, sent now or at a set time, with a full delivery record.
- AutomationsRelease 2Event-driven workflows with delays, waits and branches, reusing your templates and routing. Planned for Release 2.
- SandboxAvailableA sandbox with simulated providers and fixed scenarios for failures, timeouts and messy callbacks, using the same webhooks as Live.
Start with the beta.
Hopwire is free during the invite-only beta. Tell us what you send and we will reply by email.