gaelic-ghost SMS MMS RCS Workflow
Workflow
- Classify the requirement as SMS/MMS, RCS for Business, a CPaaS multi-channel route, or an Android/iOS app compose/OTP feature. These are not equivalent APIs.
- Define sender ownership, country/carrier coverage, registration and verification, consent evidence, opt-out/help handling, content class, rate limits, and fallback before sending any message.
- For RCS for Business, model an agent with an external trigger, HTTP API, webhook responses, device capability check, rich-card fallback, and SMS fallback for unsupported recipients.
- Verify inbound signatures, deduplicate events, track delivery states, and prevent a retry from becoming a duplicate user notification.
- Keep OTP use limited to an authorized authentication flow; do not treat a client-side SMS/RCS retriever as permission to read ordinary user messages.
- Validate a test sender, inbound reply, opt-out, unreachable recipient, fallback, media behavior, and delivery failure path in the intended region.
Sources And Handoffs
Use RCS for Business for Google's direct route. A provider route may use Twilio Programmable Messaging, but it must retain the provider's sender and consent requirements. Hand Android app work to android-dev-skills and backend work to the selected server skill.