Key Takeaways
- A services marketplace list is clients who opted into that pro and job type — not everyone who ever searched “plumber.”
- Slot-open SMS is a second list. Do not reuse the “follow this pro” blast.
- Free is 1 device, 300 SMS lifetime, and 300 contacts. Developer is 25,000 SMS per year. Platform price is devices plus send volume.
- Client login OTP stays off the dispatch SIM.
- Idempotency is slot-id plus client-id — pros reopen the same calendar hole.
Summary
Scenario 671 is marketplace contact lists for licensed service-provider booking calendars — not artisan kilns, not vehicle PPI, not drop lots, not RFQ. A plumber opens a Thursday AM slot. Only clients who opted into that pro (and often that job type) should hear “slot open.” Service pricing is devices plus SMS send volume. You bring the phones and operator credit. Free is 1 device, 300 SMS lifetime, and 300 contacts.
Starter allows 2 devices: dispatch dual-SIM plus a spare. Uncapped platform volume is not unlimited carrier SMS. Confirm list APIs in Developer Center.
pro · job type · slot
slot-id + client-id — not “plumber”
A booking list is not a trade dump
Opt-in is pro plus job type plus travel radius. “Plumber” is not a list. If Ana opens a leak-repair window, do not page everyone who once booked a water-heater install.
If you reuse last month’s leak list for a new pro, you will text people who never followed this license. Rebuild from live opt-in. Persist slot-id plus client-id so a reopen does not double-page.
Services list matrix
| List | Who | Failure |
|---|---|---|
| Follow pro | Pro opt-in | Trade-wide dump |
| Slot open | Followers + job type | Follow list reused for all jobs |
| Booked / confirm | Winner only | All followers “you’re booked” |
| Client OTP | Auth pool | OTP on the dispatch radio |
Slot open and booked
Signed webhooks when a hole opens. Webhooks, DLR. MCP wraps REST only.
License and STOP
Suspended licenses stay off slot-open SMS. Honor STOP. DOL wage rules are not a reason to blast the trade tree.
Devices, volume, and airtime
A sloppy trade dump burns volume and trust. We meter devices and platform sends. Free (1/300/300) is one pro proof.
Dispatch operations
Charge the dispatch chassis before the morning window. Setup, Downloads, pricing.
Decision guide
Ship when lists are pro-and-job-type. Delay if you blast the trade. Not a CodeCanyon booking pack.
Booking checklist
- slot-id + client-id idempotency.
- No trade dump.
- Slot list ≠ follow list.
- Booked to winner only.
- Developer Center fields confirmed.
Next steps
Scenario 611 kiln, scenario 551 vehicle.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- contacts, lists, and segmentsAudience hygiene
- bulk SMS from Excel and CSVSpreadsheet campaigns
- bulk SMS with consent best practicesHigh-volume outreach
- SMS API documentationLive endpoint reference
