iMessage for sales, agents & teams A complete business texting platform + API # Your next reply starts *in blue.* Miss Blue gives your business a dedicated iMessage line you can use from your own inbox or connect to your CRM through the API. Reach leads and customers in the channel they already answer. **80%** **higher response rates** than SMS outreach\* **37%** **more attributed revenue** than SMS outreach\* [Create your free account](https://missblue.dev/signup) Shared team inbox Your own blue line iMessage API access [Discover](#intro) ONE NUMBER SHARED TEAM INBOX EVERY CONVERSATION BUILT FOR BLUE ONE NUMBER SHARED TEAM INBOX EVERY CONVERSATION BUILT FOR BLUE 01 — THE IDEA Reach more leads. Get more replies. Make more revenue. People answer iMessage. They delete another marketing email. Miss Blue puts your business on the line they already read, so the leads you have turn into conversations you can close. 02 — A complete business texting platform ## No code needed. *An API if you want one.* Miss Blue is business texting software first: a shared inbox your team signs into, your contacts, and one dedicated iMessage line for the whole company. Most customers never write a line of code. If you would rather your product or an AI agent send the messages, the same line is available over our API. Shared team inbox ### Business texting your team just opens. Sign in, add your contacts, and message customers from your company’s own line. Everyone works the same threads with the same history — no app to install, no personal cell phones, nothing to build. No code, no install One line, whole team Contacts and history **Conversations** +1 (415) 555-0198 *AC* **Ari Chen*Dana replying*** Tomorrow at 2 works! now *JM* **Jordan Miles** Can you send the details? 4m *SK* **Sam Kim** Thanks for checking in. 18m 3 teammates in this inbox · nothing installed No account, no card ## Try a real blue line *for 30 minutes.* Not a video and not a sandbox — an actual iMessage line you sign in to and send from. It can only message the phone you texted us from, so there is nothing to set up and nobody to bother. 1. 01 Text **DEMO** to [(929) 272-7048](sms:+19292727048) From the phone you want to try it on. That text is what tells us where to send everything. 2. 02 We text back a code Four characters, with a link. Tap it and the code is already filled in. 3. 03 Send yourself a message Watch it arrive as a blue bubble. Try the inbox, the API, the webhooks — the whole thing, for half an hour. [I have a code](https://missblue.dev/demo) [Text DEMO to get one](sms:+19292727048) 03 — A working preview ## This is the inbox. *Send it a message.* Every customer in one list, the conversation beside it, and your whole team working from the same thread. Type something below and watch the reply land. MB Conversations Search messages AC **Ari Chen** iMessage · +1 (415) 555-0142 Live Today, 10:41 AM A demo — the replies are written in advance, not generated. Your real inbox works exactly like this, with real people and your own number. 04 — Why Miss Blue ## Built for the way *your team already texts.* We started Miss Blue to give a business one line its whole team can work — not another number nobody recognizes, and not somebody’s personal cell phone. 1. ### *01*Texting a business shouldn’t feel like a workaround. Most business texting still arrives as a grey message from a number nobody recognizes—or from someone’s personal cell. Miss Blue gives your company its own blue line, with names, delivery and read state, photos and reactions, so it looks like every other conversation on your customer’s phone. 2. ### *02*Everybody should see the same conversation. One thread stuck on one person’s phone is a customer nobody else can help. Your whole team works from one shared inbox with the contact and the full history in front of them, so anyone can step in and keep things moving—and every teammate is included, not billed for. 3. ### *03*One reply should open the whole conversation. People answer iMessage: beta customers saw 80% higher response rates than their own SMS outreach.\* And once someone replies you can keep talking—unlimited messages back and forth, for as long as the relationship lasts, with no per-message billing to make you ration the follow-up. 05 — Designed around the conversation ## One blue line. *Different kinds of work.* 01 For sales & support teams ### Text customers from one shared inbox. Message leads and customers from your company’s line, with the contact and the whole history beside every thread. Any teammate can pick a conversation up and carry it. Shared inbox Contacts Team access 02 For AI agents ### Make your agent feel like a contact. Put an assistant in the channel people already know. Connect your own model and tools to two-way iMessage threads, and step in from the inbox whenever a person should. Real-time Context Human handoff 03 For developers ### 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. REST API Typed events Media 06 — Why iMessage ## SMS delivers a message. *iMessage starts a conversation.* 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. 01 ### Built for replies A blue thread feels like a conversation, not a campaign. People can answer naturally without learning a new channel or opening another app. 02 ### Richer than a text blast Read and delivery state, reactions, replies, and high-quality media give every message more context than a basic SMS exchange. 03 ### Human when it matters Automation can start the conversation and your team can continue it from your inbox—on the same number, in the same thread. Traditional SMS Unknown number. Plain text. Little context. Hi, just following up on your request. With Miss Blue A recognizable conversation designed to continue. Hey Ari — still looking for a time that works? Yes! How about tomorrow at 2? Read · ready for your next step \* 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.](https://missblue.dev/imessage-response-rate-study) iMessage use cases by industry ## Built around the work *your customers need done.* Explore detailed playbooks for lead response, scheduling, estimates, customer updates, team handoff, CRM automation, and responsible messaging. [Explore every use case](https://missblue.dev/use-cases) [01 **iMessage for real estate** Realtors, agents, teams, and brokerages](https://missblue.dev/imessage-for-realtors) [02 **iMessage for plumbing** Plumbers and plumbing service companies](https://missblue.dev/imessage-for-plumbers) [03 **iMessage for hvac** HVAC contractors and service teams](https://missblue.dev/imessage-for-hvac) [04 **iMessage for roofing** Roofers and roofing contractors](https://missblue.dev/imessage-for-roofers) [05 **iMessage for home services** Home-service operators and multi-trade teams](https://missblue.dev/imessage-for-home-services) [06 **iMessage for maid services** Maid services and residential cleaning companies](https://missblue.dev/imessage-for-maid-services) [07 **iMessage for commercial cleaning** Commercial cleaners and janitorial service companies](https://missblue.dev/imessage-for-commercial-cleaning) [08 **iMessage for electricians** Electricians and electrical service companies](https://missblue.dev/imessage-for-electricians) [09 **iMessage for landscapers** Landscapers and lawn-care companies](https://missblue.dev/imessage-for-landscapers) [10 **iMessage for pest control** Pest-control and wildlife service companies](https://missblue.dev/imessage-for-pest-control) [11 **iMessage for restoration companies** Water, fire, mold, and property-restoration companies](https://missblue.dev/imessage-for-restoration-companies) [12 **iMessage for general contractors** General contractors, remodelers, and project teams](https://missblue.dev/imessage-for-general-contractors) [13 **iMessage for property managers** Residential and commercial property-management teams](https://missblue.dev/imessage-for-property-managers) [14 **iMessage for auto dealerships** Auto dealers, dealer groups, and automotive sales teams](https://missblue.dev/imessage-for-auto-dealerships) [15 **iMessage for dentists** Dental practices and dental service organizations](https://missblue.dev/imessage-for-dentists) [16 **iMessage for med spas** Medical spas and aesthetic practices](https://missblue.dev/imessage-for-med-spas) [17 **iMessage for solar companies** Residential solar installers and energy sales teams](https://missblue.dev/imessage-for-solar-companies) [18 **iMessage for salons** Hair salons, beauty studios, and appointment-based stylists](https://missblue.dev/imessage-for-salons) [19 **iMessage for gyms** Gyms, fitness studios, and membership teams](https://missblue.dev/imessage-for-gyms) [20 **iMessage for restaurants** Restaurants, hospitality groups, and guest-service teams](https://missblue.dev/imessage-for-restaurants) [21 **iMessage for hotels** Hotels, resorts, and guest-experience teams](https://missblue.dev/imessage-for-hotels) 07 — Illustrative case studies ## What a better *conversation unlocks.* Three practical workflows for the private preview. These examples show how Miss Blue fits into the work, without inventing customer names or performance claims. 01 Sales Illustrative workflow ### From form fill to a real conversation. 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. 1. 1Lead enters the CRM 2. 2Miss Blue starts the thread 3. 3A rep takes over in the inbox A shorter path from interest to reply 02 AI concierge Illustrative workflow ### An assistant that lives in Contacts. 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. 1. 1Customer texts a request 2. 2The agent completes the task 3. 3A human can step in at any time Useful without another app download 03 Customer care Illustrative workflow ### Support without the support portal. A customer sends a photo and explains the issue in one thread. Your team sees the context, responds from your inbox, and follows up where they already are. 1. 1Issue arrives with rich media 2. 2Context stays with the thread 3. 3The team closes the loop Less friction, richer context 08 — From CRM to conversation ## From one workflow to *one blue bubble.* A deliberately simple path from your product to the conversation, with secure routing and clear delivery state at every step. 01 ### Your product A typed API request 02 ### Miss Blue Secure message routing 03 ### Blue line Ready to send and receive 04 ### Their Messages A familiar thread Built for reliable delivery Real-time message state Access scoped by number Before you ask ## Questions we get *every week.* - What if the person I'm messaging doesn't have iMessage? It still reaches them, automatically. The message falls back to RCS, or to SMS where RCS is not available, from the same number and with nothing for you to configure or switch on. So an Android customer is not a customer you cannot answer, and you do not keep a second number for them. It arrives as a green bubble with whatever that channel supports, which is why a read receipt or a typing indicator may not be there. - How do I know whether a message went blue or green? Every message records the service that carried it, so a thread tells you which channel each message actually used rather than leaving you to guess from a colour. You can also ask before sending: a lookup answers reachable, undeliverable, or unknown, from your own traffic rather than from Apple. Unknown means nobody has tried this handle yet, which is what every genuinely new customer looks like — it is a reason to send, not a reason to avoid it. - Do you support voice memos and attachments? Yes. Send images, videos, PDFs, and audio, and receive attachments in the shared conversation. A single audio attachment sent without text or a quoted reply uses the native voice-note path by default; an integration can set native\_voice\_note to false to send it as a regular attachment. If native delivery is unavailable before sending, Miss Blue automatically sends a regular playable audio attachment. - Can I call from these numbers? Yes. Start FaceTime Audio for a reachable Apple contact or a regular Phone call for a dialable phone number, directly from the conversation. Browser audio is the default for outbound phone calls once the line is ready for calling. Incoming phone calls can forward to a destination you choose separately for each number. The project's Calls page keeps both call types, the caller, outcome, ring time, and talk time together. - Can I bring my own phone number? Yes, you can request a transfer when setting up a paid dedicated number. Choose your current carrier and enter the number, account number, transfer PIN if issued, and billing ZIP. You can also give forwarding instructions and notes. Staff review and complete the transfer; it typically takes 1–2 weeks. Keep the existing SIM active until the transfer completes. - Can I do message blasts? No, and this is enforced rather than discouraged. A line is capped at fifteen messages a minute, and anything past that is spaced four seconds apart instead of refused — so an ordinary busy conversation never notices, and a pasted list of five hundred contacts hits it immediately. Blasting is what gets numbers flagged, and a flagged number is one nobody's messages arrive from. - Is it really unlimited texting? Conversations are not what is limited: replies never count against new people. New people per line per day are: 50 by default, seven an hour, and a line sends at most 150 messages a day in all. That is not a billing lever — it is what keeps a number looking like a business rather than a broadcaster. If you need more reach, more lines is the answer. - Is there an API? Yes, with a command line and an MCP server for supported messaging workflows. Send, read threads, look a handle up, react, unsend, manage contacts, and register webhooks. API keys belong to a project; signed-in account actions such as billing and regular phone calling are separate. The API reference lists the supported endpoints and the CLI guide lists its available tools. - Who on my team can see which conversations? Whoever you put in the project. Numbers live in projects and people are added to projects, so a receptionist and a recalls clerk can share a workspace without sharing an inbox. Your own admins do this — you do not ask us every time somebody joins or changes desk. [More questions, answered in full](https://missblue.dev/faq) — numbers, limits, groups, agents and what happens when a Mac goes offline. Explore the platform ## Go deeper on the way you want to work. [For developers ### iMessage API Build two-way blue-bubble conversations into your product or agent. Explore](https://missblue.dev/imessage-api) [For teams ### Message Center Use a complete shared conversation platform without writing code. Explore](https://missblue.dev/features/message-center) [For Apple contacts ### FaceTime Audio calling Call from your blue line without carrier Spam Likely labels. Explore](https://missblue.dev/features/facetime-audio-calling) [For every phone ### Outbound calling Call any dialable number from your Miss Blue business line. Explore](https://missblue.dev/features/outbound-calling) A complete inbox + API access ## Meet your *blue line.* 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. [Create your free account](https://missblue.dev/signup) [Already have an account? Sign in](https://missblue.dev/login)