Android SMS Gateway Scenario 743: Marketplaces contact lists in practice

Featured illustration for Android SMS Gateway Scenario 743: Marketplaces contact lists in practice

Android SMS Gateway Scenario 743: Marketplaces contact lists in practice. Scenario-based article #743 combining vertical and feature contexts under hub A. Must stay unique via specific workflow and failure case. Priced by devices and SMS send volume; BYO phone and operator credit.

Written by the SMS Gateway team for operators who run phones and airtime themselves — not for theoretical cloud SMS demos.

InformationAndroid SMS GatewayScenarioHub A
Article
Published
July 18, 2026
Updated
August 1, 2026
Reading time
16 minute read

Key Takeaways

  • Scenario 743 is dark-kitchen / ghost-kitchen bay pickup lists — not B2B RFQ samples, event wristbands, marina slips, P2P parking, tool rentals, storage-auction units, vehicle cash holds, lost-found lockers, charity vans, will-call merch, consignment, booth maps, wholesale pallets, RMA bays, meetup pins, escrow, age-gates, or seller KYC.
  • “Bay DK-5, courier window 18:00–18:20, brand BR-2” is transactional. “Add another brand” is marketing. Split SIMs.
  • Free caps contacts at 300. Do not keep every closed shift in the gateway book.
  • Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Developer is 25,000 SMS per year.
  • Staff console OTP stays on its own phone. A Friday dinner rush will starve it if shared.
  • REST list/send fields live in Developer Center — not a CodeCanyon dark-kitchen plugin. MCP, if you use it, is only a REST wrapper.

Summary

Scenario 743 is marketplace contact lists for dark-kitchen bay pickup. The kitchen OS owns the brand. The Android texts the courier a bay and a clock. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

If you reuse last night’s “open bays” dump, you will text riders whose shift already ended — and they will treat DK as spam.

Dark-kitchen bay pickup

Bind the list to live tickets for this shift. Contact lists · marketplace guide. Fields: Developer Center. Industry context: GSMA.

List map

ListPayloadSIMDo not
Live ticket + shiftBay, brand, clockTransactionalReuse closed shifts
Pass deskInbound / LATEDesk AndroidShare courier pins
Add another brandPromoPromo MSISDNRide the bay inbox
Staff loginOTPDedicated OTP phoneAttach a DK bot

DK is not STOP

DK / LATE / DONE belong on the pass Android. STOP on an “add another brand” blast must not mute a live pickup. Auto-reply and STOP · two-way.

Cost

Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free: 1 device, 300 SMS lifetime, 300 contacts. Developer: 25,000 SMS per year. Paid plans uncap platform volume; devices still meter. Pricing.

Ops

Charge the pass radio at the hatch. Doze · setup. Purge closed tickets after the shift.

Security

A live ticket is not an add-brand consent. Trust Center · OTP.

Checklist

  • This-shift live-ticket filter only.
  • Role-specific DK templates.
  • OTP isolated.
  • STOP scopes documented.
  • Airtime for Friday dinner rush.

Next steps

Transactional SMS · SMS API documentation.

Jump to the live product docs for this topic—not another long-form article.

FAQ

Frequently asked questions

Direct answers about android sms gateway scenario 743 marketplaces contact lists.

Can we SMS the same DK pin to courier and cook from one list?

Send role-specific templates. A shared pin on a group list is how a third rider takes the bag.

Does importing a dark-kitchen list include SMS credit?

No. You bring phones and operator airtime. We meter devices and platform send volume.

Is Free enough for a Friday dinner rush?

Free is 300 SMS lifetime on 1 device. Prove one bay, then use a paid device/volume plan.
Keep learning

Topically related guides—chosen by subject overlap, not a fixed sitewide footer.

Information
android sms gateway how to segment contact lists

Core Android SMS Gateway: How to segment contact lists

Core Android SMS Gateway: How to segment contact lists. Actionable guide on how to segment contact lists in context of android sms gateway. Include prerequisites, steps, limits, and internal links. Priced by devices and SMS send volume; BYO phone and operator credit.

Sep 27, 202516 min
Read article
Information
android sms gateway contacts

Android SMS Gateway contact lists: Api usage

Android SMS Gateway contact lists — api usage. Feature deep dive on contact lists (api usage). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Sep 21, 202516 min
Read article
Information
android sms gateway contact lists

Android Sms Gateway Contact Lists: In-Depth Guide

Android Sms Gateway Contact Lists: In-Depth Guide. Long-tail article focused on exact query "android sms gateway contact lists". Expand with examples, limits, FAQ, and links to hub A. Priced by devices and SMS send volume; BYO phone and operator credit. Developer Center owns live API parameters.

May 25, 202616 min
Read article
Information
android sms gateway contact import csv

Android Sms Gateway Contact Import Csv: In-Depth Guide

Android Sms Gateway Contact Import Csv: In-Depth Guide. Long-tail article focused on exact query "android sms gateway contact import csv". Expand with examples, limits, FAQ, and links to hub A. Priced by devices and SMS send volume; BYO phone and operator credit. Developer Center owns live API parameters.

Jul 20, 202516 min
Read article

Browse the full Android SMS gateway knowledge base or return to how an Android SMS gateway works.

Get started

Test the gateway on your own Android phone

Install the app, pair one device, and validate your API flow before choosing a paid plan.

You supply the phone, SIM, and operator SMS credit.