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 →Send order confirmations customers can keep
The confirmation is the message your customer keeps — forwarded, screenshotted, quoted back to support. Send it the moment the order lands, on a channel they actually read, and let the log answer for it later.
What a customer needs to see
- The order reference, prominently — it is what support will ask for
- What was bought, at least in summary
- The amount, including currency
- What happens next, and when
- A link to the order in your own system
Send it the moment the order lands
Confirmation is transactional and should not queue behind promotional traffic. Keeping the two message types distinct means a large campaign does not delay the message that tells someone their payment worked.
- Transactional sends are not filtered by opt-out suppression
- Each send is logged with its status, so support can answer from the record
- Delivery receipts are recorded wherever the provider reports delivery back
Same event, whichever channel they read
Whether a confirmation goes out on SMS, email, WhatsApp, or more than one of them, is a decision about the customer rather than about the technology. The platform connects the accounts you hold on each channel and sends on the ones you choose.
Questions this usually raises
- Should the confirmation be in the same channel as the checkout?
- Not necessarily — it is whichever channel the customer will actually look at. Multiple channels can be connected and chosen per send.
- Can we include a discount code?
- Content is yours to compose; the platform sends what it is given. Treat a discount in a transactional message as a marketing decision with its own consent implications.
- What if the confirmation fails?
- The send records its error, and the failure is visible in the logs. A retry is a decision your system makes, remembering that a retry sends a second message.
Keep reading
Who decides whether a message is marketing
The platform asks you to declare what kind of message you are sending instead of inferring it from the text. That one field decides whether the opt-out gate applies — and the honesty of the declaration is yours.
Read the guide →One-time passwords
Your login depends on a code landing before the session expires. Connect the accounts you already pay for and the platform paces each code to the number it leaves from — so a burst of logins drains at the speed your numbers allow instead of queueing behind one shared quota.
Open →Shipping and delivery updates
Dispatch notices, tracking updates and delivery windows go out when the state actually changes, not on a timer. On the SMS channel the platform spreads a dispatch batch to the limit your provider applies per number, so a whole route does not stall halfway through.
Open →Appointment reminders
A reminder earns its place by arriving early enough to change a plan and saying only what the person needs to act on: when, where, and how to change it. Send a confirmation at booking and a timed reminder before, on the number they booked with.
Open →Payment reminders
The reminder that arrives before a due date is a service; the one that arrives after is a complaint notification. Send both, keep them transactional, and pace the due-date batch so it drains in a time you can plan around.
Open →Two-factor authentication
A 2FA message is triggered by a login attempt, is time-critical, and — when it arrives unexpectedly — is the earliest signal your customer gets that someone else has their password. Send it fast, word it as a warning, and keep the record.
Open →Account security alerts
A security alert is not a notification — it is the account owner’s chance to interrupt something in progress. Speed and clarity are the whole job, and detail is a liability.
Open →Service and incident alerts
An incident alert arrives when something is already wrong — the worst possible moment to discover your send path is down too. Keep more than one connected account on that channel, and the notice about the outage is not its first casualty.
Open →Customer feedback requests
A feedback request is marketing in everything but name, so treat it like one: one question, sent once, to people who have not opted out. That is what keeps the answers worth reading.
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. Routing and pacing run on the SMS channel while logging covers every channel; consent and content stay with you.