How to Receive a Text Message
Step-by-step guide to receiving text messages on an Android device used as a self-hosted SMS gateway. Covers setup, auto-responders, webhooks, and tracking with real configuration examples.
TL;DR
Install the FlixySMS app on an Android phone, pair it via the dashboard QR code, enable inbound capture, and define keyword rules or webhook URLs. Incoming messages trigger auto-replies or external calls within seconds while using your carrier plan for cost control.
To receive a text message with FlixySMS, install the app on an Android phone and link it to your dashboard so incoming SMS route through your carrier plan instead of paid APIs.
Setting Up the Android Gateway
Install the FlixySMS app from the Play Store on a dedicated handset. The phone becomes the hardware layer that listens for inbound messages at the standard 160-character limit or splits longer ones automatically.
A typical Android handset processes 30 to 100 SMS per minute depending on carrier throttling. Pair the device with your account by scanning the QR code shown in the dashboard.
Enabling Inbound Message Processing
After pairing, open the device settings screen and toggle inbound capture. This routes every incoming message to the FlixySMS servers for logging and rule evaluation.
Configure a primary webhook URL that posts the full payload including sender number, timestamp, and message body to your own endpoint. Test the connection by sending a message from a second phone.
Sample Payload Fields
- from: "+15551234567"
- to: "+15559876543"
- body: "Order #48291 shipped"
- receivedAt: "2026-05-21T14:32:05Z"
Building Auto-Responders
Create rules that match keywords like STOP or HELP. When a match occurs the system sends a pre-written reply within three seconds.
Common setups include opt-in confirmations for marketing lists and order status lookups tied to Shopify. One rule can reference an external Google Sheets column to fetch customer data before replying.
Connecting External Platforms
Link the gateway to WooCommerce so every new order triggers an inbound confirmation path. Custom webhooks let any other system post events that the Android device then converts into SMS replies.
Use the REST API endpoint documented at API Documentation to query recent inbound messages programmatically. A sample curl call returns the last 50 entries with delivery status flags.
Monitoring Delivery and Replies
The dashboard shows real-time counts for received messages alongside delivery receipts. Track multi-segment messages separately because they arrive as separate parts that the platform reassembles.
| Setting | Value | Example Use |
|---|---|---|
| Webhook retry | 3 attempts | Order confirmation failures |
| Keyword match | Exact or regex | STOP compliance |
| Response delay | 1-5 seconds | Chatbot flow |
| Log retention | 90 days | Audit trails |
Step-by-Step Configuration
- Download and open the FlixySMS app on your Android device, grant SMS permissions, and create a new project in the dashboard.
- Scan the QR code displayed on the /dashboard page to pair the phone; wait for the green connected status indicator.
- Navigate to inbound rules and add your first keyword trigger such as "HELP" with a 160-character reply text.
- Enter a webhook URL in the integrations panel and send a test SMS from another phone to verify the JSON payload arrives correctly.
- Connect Shopify by installing the official extension and mapping order events to auto-reply templates.
- Import a contact list via Google Sheets using the bulk upload tool and assign the list to an active responder group.
- Review the activity log for the first 24 hours to confirm all messages are captured and no carrier blocks appear.
- Set a monthly quota reminder in the billing section so you stay within plan limits listed on the pricing page.
Handling Multi-Segment Messages
Messages longer than 160 characters are split automatically. The platform adds concatenation headers so the receiving phone reassembles the full text without extra work on your side.
Review the How it Works section for diagrams that show the split and reassembly flow across two or three segments.
Two-Way Conversation Examples
A customer texts "status" and receives the latest order update pulled from your WooCommerce store. Another user sends "unsubscribe" and the system removes the number while logging the event for compliance.
Check the FAQ page for answers about carrier-specific throttling and recommended phone models.
Limitations and Tradeoffs
The gateway uses your existing carrier plan so per-message cost equals your monthly bill divided by total volume. Throughput stays lower than carrier APIs when you run a single handset; add more devices for parallel sending and receiving.
We do not support picture messaging or group MMS in the current version.
Visit the contact page if you need help mapping a specific integration. Sign up at /dashboard to start receiving messages today.
Frequently Asked Questions
how do i receive a text message on my server+
Pair an Android phone running the FlixySMS app with your dashboard account. Enable inbound processing and point webhooks at your server endpoint to capture every message in real time.
can I auto reply to incoming SMS+
Yes. Create keyword rules in the dashboard that match phrases like STOP or HELP and send a configured response automatically.
what happens with messages over 160 characters+
The platform splits multi-segment SMS automatically and adds concatenation headers so the recipient phone reassembles the full text.
how do I connect Shopify orders to SMS replies+
Install the Shopify integration, map order events to responder templates, and the Android gateway will send confirmations when new orders arrive.
is there a limit on received messages+
Limits follow the plan you select on the pricing page. The Android hardware itself handles 30 to 100 messages per minute depending on the carrier.