Launching today
Comms
Launch iMessage agents in seconds
84 followers
Launch iMessage agents in seconds
84 followers
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
@cale_lane Getting this error message https://snap.wrld.tech/RLThWcL7NpmYBTJq7grl - would love to try this out!
Also, emailed
Comms
@ridgeway Thanks for bringing that to our attention! We've removed the cap and would love for you to try it now.
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?
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?
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
@mohammed_messeguem Absolutely, making iMessage agents accessible and easy is our focus. They are the best way to talk to agents, and we want everyone to have the opportunity to build with them.