Repository navigation
💡 SMS check-in channel for app-averse vendors #71
Replies: 3 comments
Weekly UpdateWhat ChangedNew research on SMS-based vendor onboarding patterns from the 2026 SMS platform landscape:
Updated Assessment
RecommendationAdvance — urgency increased. The SMS platform ecosystem is mature and affordable (Textedly, Textla are low-cost). Implementation could use Twilio or a similar programmable SMS API. The flow: vendor texts a market-specific keyword → system confirms identity via phone number → records check-in → notifies manager and followers. No app download required. This directly addresses the "app-averse vendor" adoption barrier that is the #1 risk to the supply-side flywheel. |
|
This is an exceptional product-growth and architecture proposal. Addressing app-averse supply-side users by lowering the barrier to entry to a native SMS interaction ( From a technical architecture standpoint, this proposal gets several critical things right:
Recommendation: Proceed with the suggested spike. Spin up a sandbox number, wire the Edge Function to the existing DB function, and run a 4-market pilot. The implementation cost is negligible, but the upside on supply-side liquidity and activation rates is massive. Let's build it! |
Weekly UpdateWhat ChangedThe Market Signal line "No incumbent (Marketspread, ManageMyMarket, MarketWurks, Local Line) provides an SMS path" needs revising:
Source: Marketspread latest updates. Marketspread's SMS appears to be manager-to-vendor messaging (outbound plus AI summarizing of replies), not a structured vendor-to-system status channel that updates a public shopper view. That distinction is now this idea's moat. It also suggests an upgrade: instead of strict keywords ( Architecture note: the original body references Supabase Edge Functions. The current architecture is a Go backend on Cloud Run, so the inbound webhook should be a Cloud Run handler that calls the same check-in resolver and publishes the same domain event, keeping one handler for both transports. Updated Assessment
RecommendationAdvance. Update the Market Signal, retarget the implementation notes to Go/Cloud Run, and prototype free-text parsing with echo-back confirmation against 50 realistic vendor texts before choosing keyword-only or LLM-assisted parsing. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Add an inbound-SMS check-in channel for vendors who refuse to install or open the mobile app. Vendors text a short keyword (e.g.,
IN,LATE,OUT) to a market-specific number; the backend resolves the vendor by phone, attributes the check-in to today's market day, and routes the event through the same notification + audit pipeline as in-app check-ins.Market Signal
User Signal
Agents.mdandepics.mdboth treat the mobile app as the only check-in surface; there is no current FR for SMS or any non-app input channel.Technical Opportunity
Fromphone →vendors.phone→vendor_id, then calls the samecheck_in_vendor()SQL function the mobile client uses today (Epic 4). One handler, two transports.source=smsin the audit log so reliability analytics can distinguish channels later.Assessment
Adversarial Review
Strongest objection: "SMS introduces an authentication and impersonation risk — anyone who knows a vendor's phone number can spoof a check-in, and the platform's whole value proposition is trustworthy data."
Rebuttal: Three layers: (1) SMS sender ID is verified by the carrier (much harder to spoof than email); (2) on first SMS from a new number, the system replies with a one-time PIN the manager confirms verbally during onboarding — same pattern Square uses; (3) SMS check-ins are flagged in the audit log and can be revoked by managers without dropping the in-app channel. The trust profile is no worse than the existing FR20a "manager checked in vendor on their behalf" path, which already has weaker auth than this proposal.
Suggested Next Step
Spike: stand up a Twilio sandbox number, wire an Edge Function to the existing
check_in_vendor()SQL, and pilot with a single friendly market. Measure SMS-vs-app check-in ratio over 4 market days. If SMS share is >20%, write a full PRD addendum.Proposed by the BMAD Analyst (Mary) on 2026-04-07.
Workflow run
All reactions