Key Takeaways
- A contact list is a living opt-in file you send through your own SIMs — not a purchased cloud audience.
- Subtract STOP before every send. Re-importing a dirty spreadsheet is how you undo auto-reply work.
- Segment by consent source and traffic type. Login numbers do not belong on a campaign list.
- Free is 300 contacts and 300 SMS lifetime. Bigger lists need Professional/Business plus operator airtime.
- Personalization tokens still cost segments. Count the rendered body, not the column header.
Searchers for android sms gateway contact lists usually have a spreadsheet and a SIM. The product question is narrower: can you store opted-in numbers, slice them, and send through phones you actually keep online — without re-texting people who already said STOP.
The pillar is contacts and lists. Spreadsheet send sits on bulk SMS from Excel/CSV. You bring the Android and operator credit. Pricing is devices plus send volume.
Opt-in · web form
Reminders list
Opt-in · POS
Order-ready list
STOP · 14 Jun
Skipped on next send
What a contact list is on this gateway
It is not a rented audience. Recipients see your SIM’s number. That is the commercial point and the compliance load: the same MSISDN they can reply to is the one that will carry your reputation with the operator.
Store people you can explain. “Bought a CSV from a broker” is not a segment. “Signed the paper form at reception on Tuesday” is. Keep that story next to the row even if the send UI only needs a phone column.
A list without a STOP subtract is a pending complaint. The radio does not care that marketing “needed the extra reach.”
Segments that earn their keep
Split by consent source and by job. Transactional order texts, appointment reminders, and promotional drops should not share a bucket even if they share a company. When someone STOPs campaigns, you still may need a human policy for operational SMS — write that down before the first import.
Country and language belong as fields, not as folklore in a Slack thread. Unicode names and local scripts change segment count. See bulk CSV overview for the file-shaped version of the same problem.
Field table
| Field | Why it exists | What breaks if you skip it |
|---|---|---|
| MSISDN (E.164) | The only send key that matters | Local formats, dropped leading zeros, mixed countries |
| Consent source + date | Your evidence, not the modem’s | You cannot answer a regulator or an angry reply |
| List / segment id | STOP scoped to a program | One unsubscribe kills OTP or every brand on the SIM |
| Language / script | GSM-7 vs UCS-2 budget | Two SMS parts and a truncated name |
| Timezone | Scheduled sends | 02:00 local “reminders” |
Live column names in the panel can move. Confirm there. Programmatic fields live in the Developer Center.
Hygiene, STOP, and re-import
Auto-reply can record an opt-out. Your list process has to honor it on the next send, CSV, and API path. See auto-reply and STOP. Deduplicate before you personalize. Three rows for one person is three airtime hits and one complaint.
Industry baseline: CTIA messaging practices. Counsel still owns the local letter of the law.
Keep OTP off marketing lists
Authentication is a different job: short TTL, dedicated SIM, no campaign copy. Do not “just add login users” to a blast list because the numbers already exist. The OTP use case is the other door.
Lists vs one-shot CSV
A saved list is for repeats: weekly reminders, members, routes. A one-shot CSV is a campaign hopper. Both must hit the same blacklist. If you maintain two copies of truth, STOP will leak. Prefer one store, many segments.
Plan and radio limits
Free: 300 contacts, 300 SMS lifetime, one device. Larger lists are a Professional/Business conversation, still metered by devices plus platform send volume. Operator airtime is separate. A 40,000-row list on one phone is a weekend queue, not a cloud interconnect. Isolate campaign radios from OTP.
Next steps
Import a staff list of ten, fire STOP on one row, prove the eleventh send skips it, then scale. Install the Android app and keep the sending phone charged. The list is only as honest as the last subtract.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- device and SMS volume pricingPlans and allowances
- contacts, lists, and segmentsAudience hygiene
- Android SMS gateway product guideDefinition, product, and how to buy
- SMS API documentationLive endpoint reference
