Key Takeaways
- Marketplace SMS templates are two programs: buyer transactional and seller transactional. Promo is a third.
- Never let a seller’s “broadcast” share the OTP SIM buyers use to log in.
- Dispute and payout messages should name the marketplace, not impersonate a bank.
- Rate-limit peer notifications or your operator will do it for you.
- You bring Android phones and operator credit. Pricing is devices plus send volume.
Android sms gateway for marketplaces message templates fail in a distinctive way: one SIM tries to be login, GMV notifications, and every seller’s newsletter. Buyers then stop trusting the number. This page splits copy and radios the way a two-sided product actually works.
You bring the handsets and airtime. We meter devices and volume. Ecommerce cousin: ecommerce message templates.
Buyer
Market: login code 481920. Expires in 5 min.
Seller
Market: you sold #8821. Payout pending review.
Two-sided templates
Each event has a buyer sentence and a seller sentence. They are not the same template with a name swap. Payout language especially — it attracts phishing lookalikes. Lead with the marketplace brand, never “your bank.”
If a seller can paste arbitrary text onto your MSISDN, you are not running a gateway. You are renting your spam reputation.
Buyer vs seller copy
| Event | Buyer SMS | Seller SMS | SIM |
|---|---|---|---|
| Login / 2FA | Brand + code + expiry | Same pattern, maybe same OTP pool | OTP only |
| Order placed | Order id, next step | Sold + SKU-ish id, no buyer address dump | Transactional |
| Ship / receive | Status, how to track in-app | Optional; do not double-notify spam | Transactional |
| Payout | — | Status, no “click to claim funds” | Prefer isolated money lane |
| Promo / push | Consented only + STOP | Seller newsletter is their problem unless you send it | Never OTP |
Account OTP is not an order ping
Dedicated device. One-segment GSM-7. OTP templates · OTP use case.
Order, payout, dispute
Disputes: “open the app to respond,” not a novel in SMS. Payout OTP or PINs should not sit in the same thread as “you made a sale.” Idempotency on order id so retries do not triple-text a hot listing.
Contacts: contacts and lists.
Spam between users
Cap SMS that fire on “new message from buyer.” Those become a paid denial-of-wallet on your operator bill. Prefer push/email for chat; SMS for irreversible states (paid, shipped, banned).
STOP, lists, and sellers who paste CSVs
If you offer seller campaigns, you own STOP on that MSISDN. Blacklist management · bulk CSV. Parse E.164 or refuse the file.
Who burns airtime
Two-sided notify ≈ 2× order events. Size devices for drop-hour, not Tuesday noon. Free: 300 SMS lifetime. Developer: 25,000/year. Starter / Professional / Business uncap platform send volume with 2 / 5 / 15 devices. Carrier fair-use remains. Pause on Free/Developer at allowance.
Checklist
- Buyer OTP SIM isolated; no seller broadcasts on it.
- Payout copy has no claim-fund shortener.
- Chat notifications rate-limited or not on SMS.
- STOP on any promo MSISDN persisted before the next CSV.
Next steps
Write the table in your admin, then canary one buy+sell on staff numbers. Downloads · setup.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
- download the Android gateway appGet the APK
