Frequently asked

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.

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.

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.

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.

Yes. Recording is off by default and is enabled separately for each number after you acknowledge responsibility for recording and consent requirements. FaceTime Audio records both sides in the browser; regular phone calls use carrier recording. Open Calls and choose Play once the recording is ready. An answered call does not guarantee a recording: recording must have been enabled and capture must have succeeded. Calling the FaceTime dial endpoint alone does not connect your microphone or create a recording.

Yes. Read receipts are explicit; polling the inbox does not send them. Typing can be sent explicitly, or a project admin can enable the automatic typing indicator for incoming one-to-one iMessages while a reply is prepared. The automatic setting does not apply to SMS, RCS, or group chats.

You can read and reply in group threads, create groups through the API, and manage their name, photo, and participants where the messaging service supports it. Group conversations remain visibly separate from one-to-one threads. Leaving a group through the public API is not supported yet.

You can unsend inside Apple's two-minute window, exactly as you could from an iPhone. After that the message stays delivered. Editing a sent message through Miss Blue is not supported yet.

Yes, in both directions. A tapback your customer adds appears against the message it belongs to, and you can add or remove one from the API or the console.

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.

Enter a ZIP for each number, or select Any area is fine — you pick when you have no preference. If you purchased several numbers, add a row for each one in the setup form. Each row can have its own ZIP and forwarding destination, and each submitted request reserves one of the workspace's available dedicated numbers.

It is a dedicated line on hardware assigned to you — not a pool shared with strangers, and not a shortcode. The inbox is yours; we provide the interface your team reads it in. Shared-pool numbers exist as a separate, clearly-labelled option for people who want them.

One per line of conversation you want kept separate — a front desk and a recalls queue are two, not one. Numbers live inside projects, and who can answer which line is set per project by your own admins.

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.

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.

The second one is refused with a 409 rather than delivered. A send takes a moment, and in that moment somebody unsure it worked presses send again — as does a retry after a timeout, and a second browser tab. Your customer receiving it twice is the one outcome nobody wants. If you genuinely mean to repeat yourself, there is a flag for it.

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.

A 201 means accepted, not delivered — delivery is a separate event that arrives afterwards, over a webhook or by reading the message back. Anything that failed shows up with the platform's own error against it, and every message records which Mac build handled it, so "did last Tuesday's failures stop after the update?" is a question with an answer.

That is what the MCP server is for. It is worth deciding deliberately what you let one do: replying is reasonable, and sending a read receipt is not — that receipt is a claim a human looked, and an agent that fires them by polling is telling a small lie at scale.

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.

Every conversation shows who on your team last answered it, and the activity screens show messages sent, people written to and days active per person. Conversations split by whether they replied, whether they are new, and who wrote first — because nine out of ten strangers ignoring a cold message is ordinary, and nine out of ten people who wrote in first being ignored is a problem.

Messages you send are accepted and queued, and go out automatically as soon as the number is back — there is nothing to resend. The API answers 201 with status pending, queued: true and a notice saying why; the console marks the number temporarily unavailable and shows each waiting message as queued. You can cancel a queued message until it goes, from the conversation or with POST /v1/messages/{id}/cancel. Live actions — reactions, edits, unsends and typing indicators — need the number to be available and answer 409 until it is. Messages that arrive meanwhile are picked up when the number is back, and members can request a conversation sync for the numbers they have access to.

The workspace is the business or account that owns the plan and contains projects. A project groups numbers, conversations, people, and integrations. The switcher shows the workspace first and the selected project underneath. Dashboard project totals cover that project; workspace totals cover all its projects, so the figures can match when all activity is in one project.