Comms
Launch iMessage agents in seconds
160 followers
Launch iMessage agents in seconds
160 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
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?
Comms
@ark_y_k We have both dedicated and shared lines or numbers available.
@andrew_weir2 Good — dedicated being available at all is the answer I was hoping for.
On the shared side, what's the blast radius if one deployment gets flagged? Shared numbers are the cheap default that most people will start on, so I'd assume that's where the risk actually concentrates. Is there anything watching send patterns per customer before it becomes everyone's problem, or is the guidance essentially "move to dedicated once you're serious"? Either is fine, I'd just want to know which one before building on it.
@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?
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
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.
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.