01Pick by traffic
Find the page that matches what you send.
Transactional traffic leaves at any hour. Marketing traffic needs consent, an opt-out and the destination's delivery window. Two-way traffic needs a number.
Browse the guides- OTP and verification codes by SMSLogin, sign-up and transaction codes that arrive in seconds.
- Order, payment and account notificationsReceipts, shipping updates and account notices from your own systems.
- SMS marketing campaigns to many countriesPromotions and announcements from a file, priced per country before you send.
- Appointment and booking remindersFewer no-shows: a reminder the day before, a confirmation by reply.
- Two-way SMS: replies, keywords and confirmationsA number people can answer, with replies in your inbox and on your webhook.
- Operational alerts and incident notificationsMonitoring, on-call and outage notices that do not depend on an app or data.
- SMS for crypto exchanges, wallets and Web3 appsLogin codes and withdrawal alerts, paid from the treasury you already hold.
- SMS for startups, indie developers and side projectsShip SMS today: no contract, no sales call, a test key that costs nothing.
02Settings at a glance
Four decisions per use case.
Quiet hours, sender, validity and the interface to use. Each page explains why.
| Use case | Quiet hours | Sender | Validity | Interface |
|---|---|---|---|---|
| OTP and verification codes by SMS | Bypassed | Name where delivered, number elsewhere | 5 to 10 min | API, one call per code |
| Order, payment and account notifications | Bypassed | Name where delivered, number elsewhere | Default 48 h | API per event, batch for runs |
| SMS marketing campaigns to many countries | Applied per country | Name where delivered; STOP needs a number or a link | Default 48 h | Panel campaign or batch |
| Appointment and booking reminders | Bypassed (service message) | Two-way number if you ask for a reply | Until the slot | send_at per message, or a daily file |
| Two-way SMS: replies, keywords and confirmations | As the traffic type requires | Two-way number per destination | Default 48 h | Panel replies, inbound webhook |
| Operational alerts and incident notifications | Bypassed | Name or number | 15 to 60 min | Webhook action from your tools |
| SMS for crypto exchanges, wallets and Web3 apps | Bypassed for security traffic | Brand in the text; name where delivered | 5 min for codes | API with scoped keys |
| SMS for startups, indie developers and side projects | Depends on the traffic | Depends on the destination | Default 48 h | Test key first, then live |
03The common ground
Whatever you send, four things stay the same.
-
One published rate per destination
A code, a receipt and a promotion to the same country cost the same. No plan per use case, no verification fee.
-
No identity check
An email address opens the account. No use-case questionnaire, no campaign registration programme.
-
Panel and API on one balance
Campaigns from a file, events from your code. Same routes, same reports, same credit.
-
A test key that never bills
Build and verify the whole flow, including webhooks, before funding anything.
04Questions, answered
Use cases, answered.
What can I use SMSMeteor for?
Any application-to-person SMS that the recipient expects or agreed to: one-time codes, order and account notifications, appointment reminders, operational alerts, two-way confirmations and consented marketing campaigns, to 228 destinations.
What is the difference between transactional and marketing SMS?
A transactional message follows from something the recipient did (a login, an order, a booking) and can be sent at any hour. A marketing message promotes something: it needs prior consent, an opt-out and delivery inside the destination's permitted hours.
Do different use cases have different prices?
No. Price depends only on the destination and the number of segments. A code, a receipt and a promotion to the same country cost the same published rate.
What is not allowed?
Anything illegal in the destination, phishing, impersonation of banks, carriers or public services, unsolicited bulk to harvested numbers, and marketing sent as transactional. The acceptable use policy lists them and is enforced.
Do I need to declare my use case or register a campaign?
No. There is no use-case questionnaire and no campaign registration programme. The content rules apply to every message; country-specific sender registration is handled with support where a destination requires it.
Can one account serve several use cases?
Yes. Use a campaign tag per message type, one API key per system, and keep marketing and transactional streams separate so reports and rules stay clear.
05More products
Everything else in the toolkit.
One account, one balance, one rate card. Every product below is included; none costs extra.
See the rate card- Bulk SMS campaignsUpload a list, write once, send to millions.
- SMS APIOne HTTP call per message. Any language.
- SchedulingLocal-time delivery windows per destination.
- Sender ID and routesAlphanumeric, numeric or shared senders.
- Delivery reportsPer-message status, exportable in one click.
- WebhooksDelivery events pushed to your endpoint.