Design the notification flow, not just the send
Authentication, payment and security workflows work best when the message is part of the event design from the start. Your application owns OTP generation, expiry and retry limits. Sendozi handles the delivery request, route selection and recipient-level status.
Product moments that suit Transactional SMS
- Signup and login verification codes
- Debit, credit, transfer and payout alerts
- Password-change and new-device notices
- KYC and onboarding reminders
- Subscription, renewal and account-status updates
For each, keep the message recognizable, concise and free of sensitive credentials. A customer should never be asked for a password, PIN or OTP by SMS.
Build for a supportable retry
An accepted API request is not the same thing as handset delivery. Store Sendozi's message ID against your own verification or transaction event, then use the delivery state and webhook event when your team investigates a real customer case.
Use idempotency when a network timeout makes your application unsure whether a request reached Sendozi. That protects the customer experience and prevents a retry from becoming a duplicate charge or duplicate OTP.
Separate necessary alerts from campaigns
Transactional SMS is for messages a customer expects because of an action, account or service event. Promotional SMS is for marketing to an audience with the appropriate consent. The routes are distinct because the responsibilities are distinct.
Do not label a campaign as an OTP or alert to evade DND rules. Correct classification protects your customers, your sender ID and your operations.
Answers before you start