Transactional & notification messages
Some messages a customer is waiting for — an order confirmation, a receipt, a login code. Transactional sends have to arrive in seconds and land every time. Climails delivers them by API over email, SMS and WhatsApp, on infrastructure built for speed and trust.
The messages that can't be late
Transactional messages are triggered by something the user just did, and they're expected instantly. A slow or missing confirmation or verification code erodes trust and floods support — so this class of message has to be fast and dependable.
- Order and shipping confirmations the moment they happen
- Receipts and invoices delivered reliably
- One-time passcodes and verification links in seconds
- Account, security and status alerts the user is waiting on
How to set it up
- 1
Get an API key
Create a scoped API key in the dashboard for your application to authenticate its send requests.
- 2
Build your templates
Design confirmation, receipt and code templates once, with variables for the order, amount or passcode.
- 3
Call the send API
Fire a message from your backend on the triggering event — a purchase, a signup, a login — passing the recipient and variables.
- 4
Track delivery via webhooks
Subscribe to delivery and engagement webhooks so your system knows each message was delivered, opened or bounced.
Pick the channel per message
Not every notification belongs in email. Send a receipt by email, an OTP by SMS for speed, and a shipping update by WhatsApp — each over the channel that fits the moment, all from one API.
- Email for confirmations, receipts and detailed updates
- SMS for OTP codes and urgent, must-see alerts
- WhatsApp for rich order and delivery notifications
- Web push for lightweight status changes
Reliable, and kept separate
Transactional traffic is isolated from marketing sends so a promotional spike never delays a login code — and every message is authenticated, logged and traceable end to end.
- Transactional sending isolated from marketing volume
- Authenticated on your own domain for trust and inbox placement
- Full delivery logs and webhook events for every message
- Signature-verified webhooks so your system can trust them
Frequently asked questions
How do I send transactional messages?
Call the send API from your backend with an API key, passing the recipient and template variables. The message fires on your triggering event — a purchase, signup or login.
Can I send OTP codes by SMS?
Yes. One-time passcodes go by SMS for speed, or by email, and arrive in seconds so users can complete verification without waiting.
Are transactional and marketing sends separated?
Yes. Transactional traffic is isolated from marketing volume, so a large campaign never delays a confirmation or verification code.
How do I confirm a message was delivered?
Subscribe to delivery webhooks. Your system receives signature-verified events for delivered, opened and bounced, so you always know the status.
Start sending in minutes
Create a free account, connect your domain and reach your audience across every channel — no credit card needed.
Free plan forever · No credit card required · Set up in minutes