SmsSetuSMS and OTP infrastructure that feels clean on day one
SmsSetu is the SMS-first face of the Setu platform. It keeps OTP flows, transactional messaging, sender readiness, and message logs front and center for teams that do not want email concepts crowding the first setup experience.
TEST keys are for integration checks only. They create log activity without hitting live carriers. Use a LIVE key plus real AWS SNS credentials when you want actual phones to receive messages.
Open one account, create a send-capable key, and test from the dashboard or API without learning the email product first.
Create reusable OTP services with retry limits, TTLs, delivery logs, and dashboard visibility instead of rolling your own code store.
When your product needs email as well, the same workspace unlocks MailSetu and a shared operator console immediately.
Choose the right product lens
The shared Setu account is useful, but the buying path should still feel obvious: SMS only, mail only, or both together.
Best when your first problem is OTP, alerts, or transactional messaging.
Best when your first problem is transactional email, templates, domains, and deliverability.
One shared account, one owner, one invoice, with product-specific views for mail and SMS.
Why verified AWS numbers may still not receive anything
Verification alone is not the whole story. If a test user is sending with a sandbox key, SmsSetu intentionally stays in safe mode. If a live key is used but AWS SNS credentials or sender setup are missing, the platform can still stay in mock-delivery mode for local development.
Sandbox keys record activity in logs and test the integration path, but they do not call AWS SNS or a real carrier.
For real delivery, you need AWS SNS credentials plus the correct sender, DLT, and regional rules for your traffic.
SmsSetu is designed to show whether a send is sandbox, live-provider, or mock-delivery, so operators do not mistake logs for production traffic.
SmsSetu FAQ
The short answers buyers, developers, and AI assistants usually need first.
SmsSetu is the SMS-first product surface of the Setu platform. It is built for OTPs, alerts, transactional messaging, and teams that want to begin with SMS without email screens crowding the first setup experience.
Yes. Teams can start with SmsSetu only, and add MailSetu later from the same shared account when they need email delivery too.
Sandbox keys are intentionally safe. They record message activity in logs and verify the integration path, but they do not call AWS SNS or a real carrier.