Hosted messaging lines inside your product, through an API and webhooks. Provisioning requires workspace approval and available inventory.
iMessage, RCS and SMS from one number
Fits the stack your merchants run
01Where we are coming fromThesis
Every app a merchant installs wants a way to reach their customers. Most of it goes out as email, or as a green text from a short code, and the conversation ends there.
Meanwhile, Messages is where people already talk. Put your merchants there, under your name, and every message can be answered.
The future of commerce is here.
02What stays yoursPartnership
Your agents
Your agents run the conversation. We carry the messages through the API and webhooks.
Your checkout
Your checkout stays yours. Payments on Comms is an optional add-on, off by default.
Your brand
Your merchants see your product. Comms runs underneath.
Your merchants
We don't sell to your merchants. They stay your customers.
03What their customers seeHow it works
Answer. Your agent answers on the merchant's own line, from their catalog and policies, at two in the morning.
04An SMS API, and then thisComparison
Keep your SMS. Campaigns stay where they run now. Comms adds the line for every conversation that deserves a reply, without you building a messaging stack.
05What your app ships on one APIProduct
Signature Hoodie · MCove Apparel$118.00Apple Pay
An optional add-on, off by default.
Inbox 0
(646) 555-0148Store agent · iMessage
can I swap the M for an L? have not opened it
Every handoff lands with the whole conversation.
A number per store, assigned by API.
Knowledge Reading 1 of 5
Bring your own, or start from our template.
orders/fulfilled
Delivered · iMessage
API, webhooks and MCP.
06PricingPer line
For platforms
$200per line, per month
Volume pricing on a call. We plan the rollout with you.
You never pay per message. Every merchant you turn on is a line.
07QuestionsFAQ
No. We don't sell to your merchants. Your agents, your checkout and your brand stay yours. We handle the lines and delivery.
Comms phone-number iMessage is distinct from Apple Messages for Business. Check the actual line and recipient capabilities.
Monitor line status and delivery evidence. Reconcile uncertain sends before retrying; channel fallback requires a clear rejection.
Messages are unlimited on Dedicated. One line carries up to 7,000 a day; past that, add a line for each extra 7,000.
It is a real phone number. iPhones get iMessage. Android gets RCS where the line and carrier support it, and SMS otherwise. Keep your campaigns where they run. This is for the conversations.
No. Payments is an optional add-on, and it is off by default.
Porting requires approval and a supported number. Confirm port-out rights, fees and timing in your agreement.
API line assignment requires workspace approval and inventory. Confirm eligibility before promising a merchant a number or area code.
Lines and messages are in the API. Webhooks carry every message and event, and MCP lets your own agents work the conversation.
$200 a line. Volume pricing is set with you on a call. You never pay per message.
Plan the rollout with us. Timing depends on integration readiness, workspace approval and number inventory.
Cale LaneCofounder, Comms · cale@osis.co
We are building Comms because we believe the next checkout is a conversation, and the apps merchants already run are the fastest way to bring it to them. If you want to see how it fits your platform, book a call. I would love to hear what you are building.
