Getting an iMessage line for your business used to mean sales calls, carrier paperwork, weeks of waiting, and $225+ a month before your first text. Comms puts a live agent on a real iMessage line in about 30 seconds. Describe it in plain English or make one API call. It handles support, bookings, onboarding, and payments inside the thread people actually read. Free to start with 3,000 messages a month, then a flat $50.
Hey guys, I'm Cale, the co-founder of Comms. My partner Andrew and I set out on a mission to fix the way iMessage agents were handled. We spent thousands of dollars on lines that took weeks to set up and knew there had to be a better way. Now it takes one sentence, and your agent is live on a real line in about 30 seconds.
We want iMessage agents to be a way for companies to grow with their customers through support, bookings, payments, and so much more. Communication has always evolved with new generations, and we believe pairing AI with iMessage is how that trend continues.
The demo is the product. Text the live agent at comms.osis.co and ask it anything. Andrew and I are here all day - feel free to ask questions in the comments!
the demo-is-the-product approach is the right call for proving this actually works. one thing I keep coming back to though: what happens if someone adds this agent's number into a group iMessage thread instead of a 1:1 support convo? group consent and expectations are pretty different from a private support DM, and that feels like something you can't really control from the API side once a customer decides to do it.
Finally got a real iMessage line for my side project without dealing with carriers, set it up in like two minutes and the API docs were actually readable. Flat pricing beats the per-message surprises I kept getting elsewhere.
the setup speed is genuinely impressive but the line in the description that catches my eye is "payments inside the thread" - collecting card details over iMessage is a different compliance bar than support/bookings. is that handled through a tokenized link/handoff so raw card numbers never actually land in the message thread itself, or is the agent parsing payment info directly out of chat text
Signed up and got a working iMessage line in under a minute, which still feels almost illegal. The plain-English setup actually understood what I threw at it without me rewriting the prompt three times.
The 30 second setup is honestly kind of wild compared to the carrier paperwork nightmare I went through last year for my business line. Really cool that it works through real iMessage too, not some random SMS gateway pretending to be Apple.
Seconds-to-launch is a good promise, but iMessage is the one channel where the platform has no official path for this, so the interesting question is what's underneath.
Specifically: whose number is sending? If agents share infrastructure, one badly behaved deployment getting flagged seems like it would affect everyone downstream, and Apple's enforcement isn't something you can appeal your way out of quickly. Is there isolation per customer, and have you hit any rate ceilings yet in practice?
iMessage as an agent channel skips the app-install friction entirely, which is the right wedge for consumer use cases. The Apple Messages framework has always been tricky around delivery receipts and the SMS fallback. How do you handle agent session state when a thread silently switches from iMessage to SMS mid-conversation and the agent needs to stay coherent?
pricing comparison is big plus , most of those competitors charge just for the line, so the $50 "agents and inbox included" framing is a genuinely fairer comparison than it first looks
Comms launched on Product Hunt on July 27th, 2026 and earned 115 upvotes and 15 comments, placing #12 on the daily leaderboard. Getting an iMessage line for your business used to mean sales calls, carrier paperwork, weeks of waiting, and $225+ a month before your first text. Comms puts a live agent on a real iMessage line in about 30 seconds. Describe it in plain English or make one API call. It handles support, bookings, onboarding, and payments inside the thread people actually read. Free to start with 3,000 messages a month, then a flat $50.
Comms was featured in Messaging (52k followers), Developer Tools (517.5k followers) and Artificial Intelligence (475.9k followers) on Product Hunt. Together, these topics include over 206.3k products, making this a competitive space to launch in.
Who hunted Comms?
Comms was hunted by Cale Lane. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Comms stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Cale Lane