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 heading back to the depot. Each of those is a message that either saves a second trip or causes one.
The messages that save a second 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
Batches that drain, and receipts you can read
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, so a batch does not stall partway through. Receipts come back normalized, which is what tells a failed delivery apart from a message that never arrived.
- Batches spread across connected accounts instead of hammering one
- Automatic failover between connected SMS accounts
- Receipt status normalized across providers into one webhook payload
It fits next to the systems you already run
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 normalizes 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 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 →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 →Travel & 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.
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.