Email, SMS and OTP workflows
Manage account verification, password recovery and transactional messages from your backend. Plan delivery providers, abuse controls and delivery feedback separately.
How to design the workflow
Queue delivery and process bounces, complaints and failed SMS states. Avoid errors that reveal account existence. Keep provider keys and sender configuration on the server.
Cost and service boundaries
SMS can cost by country and volume, while email can cost by delivery volume. No free or unlimited OTP package is offered; a customer messaging provider is not connected.
Pre-launch checklist
Validate these steps in your app and with the providers you choose. Measure concurrent load alongside CPU, memory and storage before selecting a plan.
- Test OTP brute-force and resend limits.
- Keep tokens out of logs.
- Verify sender setup and delivery reporting.
Common questions
Is this service available today?
This page describes a service plan and architecture. Managed customer services are not enabled; publication does not activate resources or integrations.
Which plan should I consider?
Consider the resource scope of Developer. This is not a capacity guarantee; validate it against application load and external provider fees.