Reading a delivery receipt
A receipt is a sequence of states, not a verdict. Treating an intermediate one as final is the most common way a sending dashboard ends up lying to you.
Read the guide →Messaging for travel and hospitality
Travel messaging is time-zone-shaped: a confirmation that must arrive immediately, a reminder that should arrive the evening before, and a disruption notice that is worthless if it arrives after the guest has left for the airport.
From booking to arrival
- Booking confirmation with a reference
- Pre-arrival check-in and directions
- Day-of arrival time and access information
- Disruption, delay and cancellation alerts
- Post-stay review requests
Failover matters when guests are already travelling
A disruption notice goes out when something has already gone wrong, which is the worst moment to discover that one provider account has stopped accepting traffic. On the SMS channel the platform can route to another connected account instead of failing, and normalised receipts show what actually left.
- Automatic failover between your connected SMS accounts
- Delivery receipts normalised into one status
- Per-number pacing so a wide disruption send does not stall
What remains with you
Guest consent, the accuracy of the information you send and any local rules about contacting travellers are your responsibility. The platform carries the message, not the decision to send it.
Questions this usually raises
- Can a message go out in the guest’s own language?
- Content is whatever you send, so any language the channel supports is possible. Non-Latin scripts change message segmentation, which affects message count and therefore cost.
- What if a guest replies to a disruption notice?
- Replies are captured as inbound messages and can be surfaced, but the platform is not a guest-services inbox. Route replies to your own system if you need to act on them.
- Can we send on WhatsApp as well as SMS?
- You can connect the accounts you hold on each channel and choose which one carries a given message. Routing, receipts and suppression are implemented for SMS; the same is not claimed for the other channels.
Keep reading
Routing and failover
Routes are ordered by priority and weighted within a connection. The point of the arrangement is that a provider rejecting sends degrades into slower sending, not into silence.
Read the guide →E-commerce & retail
A storefront is mostly a messaging operation that happens to have a checkout. The confirmation, the dispatch note, the delivery window, the code for a failed payment — these are the messages customers actually read, and they run on the same few send paths every day.
Open →Fintech & payments
In payments, the message is often the product: a code that must arrive before a session expires, an alert that proves a transaction happened, a reminder that keeps a subscription alive. Latency and duplicates matter here more than anywhere else.
Open →Healthcare & clinics
Most healthcare messaging is administrative, and administrative is exactly where a missed message costs a wasted appointment slot. The discipline is to say just enough to be useful and nothing that belongs in a clinical record.
Open →Logistics & delivery
A delivery operation lives on contact attempts: the customer who is not home, the gate code nobody has, the parcel going back to the depot. Each of those is a message that either saves a second attempt or causes one.
Open →SaaS & online services
For a SaaS product, messaging is infrastructure with a product surface: the login code, the incident notice, the trial-expiry nudge. These messages sit on the critical path of someone else’s workday, which sets a higher bar than marketing ever has.
Open →Education & training
Education messaging is overwhelmingly about timing: a class that moved, a deadline that is close, an enrolment that has not been confirmed. The failure mode is not a missing message, it is a message that arrives after it matters.
Open →Marketplaces & platforms
A marketplace sends to two audiences who care about the same event for opposite reasons: the buyer wants it to arrive, the seller wants proof that it did. That makes receipts and auditability the interesting part of the problem.
Open →On-demand & field services
Field service messaging is measured in minutes: a technician is twenty minutes away, a job has moved, a customer will not be in. Every one of these messages exists to avoid a wasted trip.
Open →Scope. Whaleal Messaging is an orchestration layer over the CPaaS or BSP accounts you already hold. Your contracts, your rates and your sender identities stay yours, and nothing in the middle reprices them. Sector-specific rules — consent, records retention, industry obligations — stay with you and your provider.