Add iMessage to your SMS platform
Give your customers blue bubbles on iPhone without rebuilding their flows. One API call, with eligible RCS, and SMS as fallback.
Same send, better channel
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.
Your brand
No Comms branding on messages. Set the name and photo per line.
Webhooks for everything
Replies, reactions and delivery events arrive signed.
How it works
Call a hosted iMessage API from the same place you send SMS today. With Comms by Osis, one POST to /api/v1/comms/messages with channel set to auto sends iMessage to iPhones, then tries eligible RCS, and SMS.
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.
Replies, reactions and delivery events arrive as signed webhooks, so your inbox and automations can treat iMessage like another channel. Save the message ID from each send: acceptance is not delivery.
Reviewed against the published API docs. Product facts
Under your brand
Yes. Comms does not add its branding to messages your customers send. On a dedicated line, set the contact card name and photo recipients see.
Give each customer their own dedicated line, keep the customer-to-line map in your backend, and use line-scoped keys where an integration should only reach one line.
Dedicated is $200/month per line with $0 setup and up to 7,000 messages a day. A dedicated line is required to start conversations: on Free and Plus shared lines, the contact texts first. Additional dedicated lines are set up with our team on an Enterprise plan.
What iPhone users get
Typing indicators, read receipts, tapbacks, polls (iOS 26 or later), group chats on dedicated lines and contact cards.
RCS adds richer messaging on eligible Android phones; 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.
SMS rules still apply
Yes, for messages that go out as SMS. Carrier registration and consent rules still apply to the SMS route, and RCS requires carrier enablement. Keep your existing opt-out handling and apply it to every channel.
Talk to the team.
Book 30 minutes with the people who build Comms. Bring your use case and we’ll scope the lines you need.