Key Takeaways
- Android SMS gateway two-way inbox in-depth: replies land on the same MSISDN that sent, then into your dashboard or webhook — not a hosted long code you rented from us.
- STOP must suppress the next promo send. A pretty inbox without a CRM write is decoration.
- Do not park customer support on the OTP originator.
- Inbound retention is a policy, not “keep forever because it is convenient.”
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 300 SMS lifetime.
- Product path: two-way SMS. Developer Center owns live inbound fields.
Query android sms gateway two-way inbox when support wants replies on the same thread the customer saw. Hub A: complete practitioner guide. Product: two-way SMS. STOP automation: auto-reply and STOP.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If STOP only prints in the inbox and the next campaign still fires, you do not have two-way. You have a log.
What a two-way inbox is
Outbound SMS leaves the modem. Inbound SMS to that MSISDN is captured by the app and surfaced as a thread or webhook. Recipients see a real mobile number. That helps trust. It also means a burned SIM is a burned inbox.
It is not iMessage on a server
Concatenation, encoding, and delayed MO (mobile originated) messages still apply. Do not promise chat-app latency. Staff who live in the inbox need a runbook for after-hours STOP.
Route table: STOP, support, OTP noise
| Inbound | Where it should land | Failure mode |
|---|---|---|
| STOP / UNSUBSCRIBE | Promo suppression list immediately | Footer-only, next blast still sends |
| Human support reply | Named promo or support SIM | OTP device becomes a helpdesk |
| Accidental reply to a code | Drop / ignore on OTP pool | Support tickets on a login radio |
| Keyword auto-reply | Documented, rate-capped | Loop with another bot |
STOP API spoke: auto-reply and STOP API usage.
Inbound events vs the dashboard tray
Humans can live in the UI. Production CRM needs webhooks with signatures. Server webhook in-depth. Limits: webhooks limits.
Retention and who can read replies
Inbound SMS is personal data. Keep it as short as the job requires. Staff access is a list, not “everyone with the dashboard password.” GDPR-minded handling is a sibling how-to, not this page.
USSD is a different product
Balance checks and operator menus: USSD requests in-depth and USSD gateway. Do not stuff USSD sessions into the SMS inbox mental model.
Inbound still sits on a SIM you fund
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. We do not supply the MSISDN as a rented aggregator number. Losing two-way means replacing a SIM you own, not opening a ticket for a hosted long code.
Checklist
- Promo vs OTP SIMs named.
- STOP writes suppression before the next send.
- Support hours and who watches the tray.
- Webhook path for CRM, not inbox-only.
- Retention window written.
- No USSD mixed into SMS runbooks.
- Canary inbound from a staff handset.
- Developer Center for live inbound fields.
- Consent story matches promotional two-way.
- No “unlimited SMS” claim because replies are free-looking.
Next steps
Open two-way SMS, wire STOP, then device and volume pricing. The inbox is a SIM with manners.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- two-way SMS inboxReplies on your SIM
- SMS auto-reply and STOP keywordsOpt-out and keywords
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
