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 shaped by the clock: a confirmation that has to arrive immediately, a reminder the evening before, a disruption notice that is worthless once the guest has left for the airport. Send each one from an account that is still accepting traffic.
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
The one day you cannot afford a second failure
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 normalized receipts show what actually left.
- Automatic failover between your connected SMS accounts
- Delivery receipts normalized into one status
- Per-number pacing so a wide disruption send does not stall
Guest consent stays with you
Guest consent, the accuracy of the information you send and any local rules about contacting travelers 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 and automatic failover are implemented for SMS; opt-out suppression applies to marketing sends on every channel, and receipts are normalized wherever the provider reports them.
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 runs on the messages customers actually read: the confirmation, the dispatch note, the delivery window, the code after a failed payment. Send all of them over the SMS, email and WhatsApp accounts your store already pays for.
Open →Fintech & payments
In payments the message is often the product: a code that has to land before the session expires, an alert that proves a transaction happened, a reminder that keeps a subscription alive. Connect your own accounts, and the send path stops being the part you have to watch.
Open →Healthcare & clinics
Most clinic messaging is administrative, and a missed administrative message costs a wasted appointment slot. Send a confirmation at booking and a timed reminder before, on the number the patient gave you — and keep clinical detail out of it.
Open →Logistics & delivery
A delivery operation lives on contact attempts: the customer who is not home, the gate code nobody has, the parcel heading back to the depot. Each of those is a message that either saves a second trip or causes one.
Open →SaaS & online services
Your login codes, incident notices and renewal nudges sit on the critical path of someone else’s workday. Send them from your own service with a tenant API key, and read the outcome back through the same API.
Open →Education & training
Education messaging is about timing: a class that moved, a deadline that is close, an enrollment nobody confirmed. The failure mode is not a missing message — it is one that arrives after it mattered.
Open →Marketplaces & platforms
A marketplace messages two audiences about the same event for opposite reasons: the buyer wants it to arrive, the seller wants proof that it did. That makes the receipt the part worth getting right.
Open →On-demand & field services
Field service messaging is measured in minutes: a technician twenty minutes away, a job that moved, a customer who will not be in. Send the ETA when the event happens and it saves a trip; send it late and it is worse than silence.
Open →Scope. Whaleal Platform sends 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.