Product facts
Current Comms capabilities and requirements
A reviewed source for channel eligibility, routing, number control, payment availability, AI billing and hosted MCP. Endpoint documentation is the detailed integration contract.
Channels and delivery
Auto routing selects an available channel for the sending line and recipient, moving to another channel only after a confirmed pre-send rejection. RCS fallback supports plain text. An uncertain result does not trigger another send. An explicit channel never falls back.
RCS requires a supported dedicated line, carrier enablement, and a compatible recipient. Sending currently supports one plain-text message to an E.164 phone number.
Acceptance is not delivery. Delivery and read events depend on the channel, line, recipient, and available receipts. SMS does not provide read receipts.
| Route | Eligibility | Behavior |
|---|---|---|
| iMessage | Supported line and recipient | Rich messaging capabilities vary by line and recipient. Not Apple Messages for Business. |
| RCS | Supported dedicated line, carrier enablement, compatible recipient | Plain text to one E.164 number. Check line and recipient capabilities. |
| SMS | SMS-capable line and supported destination | Carrier messaging. No read receipts; regional registration requirements may apply. |
| Auto | Eligible routes for the selected line and content | Auto routing selects an available channel for the sending line and recipient, moving to another channel only after a confirmed pre-send rejection. RCS fallback supports plain text. An uncertain result does not trigger another send. An explicit channel never falls back. |
Dedicated lines and number control
API line claiming requires workspace approval and available inventory. A denied claim returns line_claim_not_allowed; unavailable inventory returns no_available_line.
Porting requires approval and a supported number. Confirm port-in, port-out, geographic availability, fees, and timing before planning a migration. You can cancel replacement setup before submitting the transfer; a submitted transfer cannot be canceled from the setup panel.
Payment availability
Payment requests use checkout links only when the global Payments product and workspace payments are enabled and merchant requirements are met. Native in-thread Apple Pay is coming soon; checkout links are not native Apple Pay in Messages.
AI usage and billing
AI usage is billed separately from messaging plans, through prepaid Comms credits or a connected customer OpenRouter account. No messaging plan includes AI usage. Review credit-purchase fees and model costs before enabling a hosted agent.
Hosted MCP is available
The hosted MCP endpoint is https://comms.osis.co/api/v1/comms/mcp. It supports OAuth or a scoped API key. Inspect tools/list for the current tool inventory; use webhooks for event-driven inbound processing.
Do not use a fixed historical tool count. Tool names and permissions should be read from the authenticated server inventory.
Documentation changes
13 October 2026: reconciled current navigation and optional-product gates; Payments requires both global and workspace enablement. The ecommerce and Why previews remain noindex.
5 October 2026: published this capability summary, clarified RCS and fallback requirements, distinguished checkout links from native Apple Pay, and documented provisioning gates and separate AI usage billing.
These are documentation clarifications, not claims that new channel features launched on this date.
Developer examples are tested locally using signed events and a simulated send endpoint. Production delivery, number portability and workspace eligibility must be validated for your account.