Add iMessage to what you’re already building.
A focused HTTP API for sending, receiving, attachments, reactions, and conversation state—without building the delivery infrastructure yourself.
Miss Blue gives your business a virtual iMessage line you can use from our shared inbox or connect to your CRM through the API. Reach leads and customers in the channel they already answer.
No new app to teach.
No cold channel to fight.
Just a conversation.
Messaging is already where relationships happen. Miss Blue makes that surface programmable—and keeps a human inbox one click away.
Most people just open the Miss Blue inbox and start talking to customers — nothing to install, nothing to build. If you have a product or an AI agent that should send the messages instead, the same line is available over our API.
Send from a granted number, receive replies, and keep message state in sync without exposing the Mac fleet beneath it.
POST /v1/messages"number_id": "num_01J...","recipient": "+1 415 555 0142","text": "Still free Thursday?"
A focused HTTP API for sending, receiving, attachments, reactions, and conversation state—without building the delivery infrastructure yourself.
Put an assistant in the channel people already know. Connect your own model and tools to two-way iMessage threads.
Use the Miss Blue inbox to talk with contacts directly, pick up where automation stopped, and keep one shared history.
People are more likely to engage when outreach feels familiar, personal, and easy to answer. A blue thread brings richer cues and less friction to every exchange.
A blue thread feels like a conversation, not a campaign. People can answer naturally without learning a new channel or opening another app.
Read and delivery state, reactions, replies, and high-quality media give every message more context than a basic SMS exchange.
Automation can start the conversation and your team can continue it from the shared inbox—on the same number, in the same thread.
Unknown number. Plain text. Little context.
A recognizable conversation designed to continue.
* Based on Miss Blue's internal analysis of beta customer messaging, comparing iMessage outreach with those customers' SMS outreach. Revenue means revenue attributed by participating customers to those conversations. Results vary by audience, message, timing, attribution method, and use case. Read the research and methodology.
Explore detailed playbooks for lead response, scheduling, estimates, customer updates, team handoff, CRM automation, and responsible messaging.
Explore every use caseThree practical workflows for the private preview. These examples show how Miss Blue fits into the work, without inventing customer names or performance claims.
A qualified lead gets a personal iMessage while intent is still high. The agent handles the first reply, then routes the thread to a rep when the buyer is ready.
Customers ask for help the same way they would text a person. The agent answers, uses its tools, and keeps the whole task inside one familiar conversation.
A customer sends a photo and explains the issue in one thread. Your team sees the context, responds from the shared inbox, and follows up where they already are.
A deliberately simple path from your product to the conversation, with secure routing and clear delivery state at every step.
A typed API request
Secure message routing
Ready to send and receive
A familiar thread
Build two-way blue-bubble conversations into your product or agent.
Use a complete shared conversation platform without writing code.
See practical playbooks for real estate, plumbing, HVAC, roofing, and home services.
Read the beta observations, reported benchmarks, methodology, caveats, and pilot framework.
Start with a Miss Blue number and a conversation platform your team can use immediately. Connect the API whenever you are ready to build those same conversations into your product or agent.