Programmable Messaging API  ·  View 06 of 22  ·  People and journeys

Journey — Texting STOP

The only journey whose success condition is that nothing else happens.

Editable source SVG draw.io All views
Message recipient on a shared short code Goal — Make it stop, once, without a web form Trigger — A marketing message they did not ask for Done when — One confirmation, then silence from every tenant on that number 1 · Unwanted message 2 · Replies STOP ◆ moment of truth 3 · Confirmation 4 · The next campaign ◆ moment of truth What they do Reads it, annoyed Texts STOP Gets one reply Waits to see What the platform does Inbound endpoint verified Keyword intercepted first Consent written, append-only Mandated reply sent Tenant told, already actioned Submit refused, attributably How it feels Left alone Annoyed Reporting you Where it hurts Shared number hides the sender Duplicate inbound = two opt-outs Messages already in flight What the architecture owes it Ownership by allocation rule Dedup by provider reference Platform owns the keyword 30 s propagation, stated Journey — Texting STOP and Being Left Alone The only journey where the right answer is that nothing else happens. v 1.0 · owner Integration Platform Architecture

Decisions

  • The platform owns the regulated keyword, not the tenant: STOP is actioned before the tenant is told, and the tenant receives an already-actioned event.
  • Consent is an append-only history, so "what did we know when we sent it" is answerable years later.
  • On a shared sender identity, ownership is resolved by an explicit allocation rule rather than inferred from conversation history.

Assumptions

  • Consent changes are effective in the data plane within 30 s, which is stated rather than hidden.
  • Carriers redeliver inbound messages on their own schedule, so inbound dedup is mandatory, not defensive.

Risks

  • Messages already accepted and in flight when the STOP lands are the honest gap; the 30 s window is the stated bound on it.
  • A duplicated inbound delivery becomes a duplicated tenant action, which for an opt-out means two confirmation messages to someone who asked for none.
◀  Journey — First Send, First Complaint All views Layered Architecture  ▶
Solution Architecture v1.0 · Google Cloud · Integration Platform Architecture · 2026-10 · 22 views · 16 architecture decision records06-journey-stop