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 logistics and 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.
Where messages save a failed attempt
- Dispatch confirmation with a tracking reference
- Day-of delivery window, updated when the route changes
- Driver-arriving notice ahead of the stop
- Failed-delivery notice with a one-tap reschedule link
- Depot-collection reminder before a parcel is returned
Routing and receipts do the heavy lifting
Delivery messaging is bursty: a route is planned, a batch goes out, then nothing. On the SMS channel the platform spreads the batch to the pacing your provider allows per number, routes around an account that stops accepting traffic, and normalises the receipts so a failed delivery can be distinguished from a message that never arrived.
- Batches spread across connected accounts instead of hammering one
- Automatic failover between connected SMS accounts
- Receipt status normalised across providers into one webhook payload
How it fits the rest of your delivery stack
Routing, parcel data and your transport management system stay where they are. The platform sends the message you ask it to send, on the account you connected, and reports what happened to it — which makes it a clean fit next to the systems that already know the route.
Questions this usually raises
- Can I send a batch of delivery notices without hitting a rate limit?
- The platform paces SMS to the limit your provider applies per sender number, and you can add further numbers or accounts to raise the ceiling. It does not override your provider’s limit for you.
- How do I know a notice was actually delivered?
- Providers return delivery receipts, and the platform normalises them into a single status. Note that a receipt reflects acceptance by the destination network, not that a human read the message.
- Can the same notice go out on WhatsApp as well?
- You can connect the accounts you already hold on each channel and send on whichever you choose. Routing and automatic failover between accounts are implemented on the SMS channel today.
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 →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 →Travel & 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.
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.