[All articles](https://missblue.dev/blog) Miss Blue field notes # Switchit and iMessage: sending the video follow-up Switchit’s differentiator is video, and video is also the most interesting thing you can do with a messaging line. It just is not something Switchit does — its cards are shared by text, not sent by it. Here is where the boundary falls. Published August 27, 2026 11 minute read In this guide [The short answer](#section-1) [Shared by text is not the same as sending texts](#section-2) [What Switchit actually is](#section-3) [Why the assumption comes up](#section-4) [The workflow worth building](#section-5) [Sending video over iMessage](#section-6) [Getting contacts out of Switchit](#section-7) [Consent still applies](#section-8) [What about RCS?](#section-9) [The messaging half](#section-10) Build with Miss Blue **Turn the next message into a real reply.** Get a blue line for your product, agent, or team. Use the Message Center today and connect the API anytime. [Create your account](https://missblue.dev/signup) [Explore the API](https://missblue.dev/imessage-api) Build with Miss Blue **Turn the next message into a real reply.** Get a blue line for your product, agent, or team. Use the Message Center today and connect the API anytime. [Create your account](https://missblue.dev/signup) [Explore the API](https://missblue.dev/imessage-api) 01 ## The short answer Switchit does not have an iMessage API. It holds no phone number, sends no messages on your behalf, receives no replies, and reports no delivery outcomes. As of August 27, 2026 nothing in its published material describes a messaging channel. The confusion here has a specific source, and it is more understandable than for the rest of the category: Switchit cards are shared via text message. That is your phone’s messaging app sending a link you tapped — not Switchit sending anything, and not something a server can drive. 02 ## Shared by text is not the same as sending texts When a Switchit card is shared by text, the flow is: you tap share, your device opens Messages with a link prefilled, and you press send. The message comes from your personal number, through your own device, initiated by you. That distinction is the whole article. It means there is no programmatic path — no server-side send, no automation, no send on behalf of a team, no delivery receipt, and no way for a reply to reach anything but the individual’s phone. Any workflow that needs a message to leave without a human tapping send needs a messaging provider. - Share-by-text uses your device and your personal number - It requires a person to tap send, every time - There is no server-side equivalent - Replies go to the individual’s phone, not to a team inbox - No delivery state, no retries, no audit trail 03 ## What Switchit actually is Switchit is a digital business card platform built around video: the card leads with a video introduction rather than a static profile, and is shared by text, email, or QR code. It is the most differentiated product in the category on presentation. Its published integration surface is thinner than competitors like Blinq, Popl, or Mobilo — a HubSpot integration is documented, but there is less public developer material to build against. If you need a programmatic export path, confirm what is available on your plan before designing around it. - Video-first digital business cards - Shared by text, email, or QR code - A documented HubSpot integration - Less published developer material than others in the category - No line, no send endpoint, no inbound message events 04 ## Why the assumption comes up Two reasons. The share-by-text flow above is the first, and it is the strongest in the category — Switchit genuinely does put a text message on your screen. The second is Linq, a digital business card company that launched Linq Blue, a separate messaging product with an iMessage API. One vendor in the category crossed into messaging, which makes the question fair to ask of the others. Switchit has not. Messaging infrastructure means Apple accounts, hardware, deliverability, and an operations team on call — a different business from making a good video card. 05 ## The workflow worth building Video plus messaging is a genuinely strong follow-up, and it is more effective when the video arrives in a thread than when it arrives as a link in an email nobody opens. So the workflow is: capture the contact with Switchit, then send the follow-up — including the video or a link to the card — from a business messaging line. Done this way, the follow-up can go out automatically, from a line the whole team can see, with a reply landing somewhere a person is actually watching. That is the part share-by-text cannot do. 06 ## Sending video over iMessage If you want the video itself in the thread rather than a link, that is an attachment send. Miss Blue handles media by uploading the file first and referencing it on the send. One detail catches people out: iMessage has no captions, so text and attachments go as separate messages rather than as one captioned bubble. In practice, send a short line of context first and the video immediately after. Keep the file small enough to arrive quickly on cellular — a ninety-second introduction at a sensible bitrate, not an uncompressed export. ``` // Text first, then the video — iMessage has no captions. const BASE = "https://api.missblue.dev"; export async function sendVideoFollowUp({ recipient, attachmentId, firstName }) { const send = (body, key) => fetch(`${BASE}/v1/messages`, { method: "POST", headers: { Authorization: `Bearer ${process.env.MISS_BLUE_KEY}`, "Content-Type": "application/json", "Idempotency-Key": key, }, body: JSON.stringify({ number_id: process.env.MISS_BLUE_NUMBER_ID, recipient, ...body }), signal: AbortSignal.timeout(30_000), }); await send( { text: `Hi ${firstName} — great meeting you. Quick 60-second intro below.` }, `switchit:${recipient}:intro`, ); await send({ attachment_ids: [attachmentId] }, `switchit:${recipient}:video`); } ``` 07 ## Getting contacts out of Switchit Because the public developer surface is thinner here, plan for the possibility that your export path is a CRM integration or a manual export rather than a webhook. That is workable — it changes the latency, not the design. If the follow-up will not fire within minutes, adjust the copy. A message that opens with “great meeting you just now” reads badly the next afternoon; one that opens with “following up from yesterday’s show” reads fine. - HubSpot integration as the documented join, where available - CRM record as the trigger, rather than a capture webhook - Scheduled or manual export for low volume - Match the message copy to the actual delivery latency 08 ## Consent still applies Someone accepting a video card has agreed to receive your details. They have not agreed to receive business text messages, and the fact that the card itself arrived by text does not change that — that message came from a person, at the moment of the conversation, and is not a standing permission. Capture the messaging opt-in explicitly and store the timestamp and wording with the contact. CTIA’s Messaging Principles set the industry expectation of consent before messaging and a working opt-out, and applicable law may be stricter for promotional content. - A card shared by text is not messaging consent - Capture the opt-in explicitly and record it - Keep transactional and promotional consent separate - Suppress across every workflow at once - Identify the business and the rep in the first message 09 ## What about RCS? Switchit publishes no RCS API either. Channel choice belongs on the messaging side, decided per recipient based on what the destination supports — which matters here because video behaves differently across iMessage, RCS, and MMS. That is a good reason to keep channel selection with a provider rather than in your own code: the same follow-up may need to be a video on one channel and a link on another. 10 ## The messaging half Miss Blue supplies what Switchit does not: a dedicated business iMessage line, an HTTP API with attachment support and durable conversation events, and a shared Message Center where teammates read the same thread and take over from an automation. Published pricing is $39 per month for a shared testing number and $99 per month per dedicated number, with unlimited commercial usage, contacts, team access, the Message Center, and API access included on the dedicated plan. Those are current 50%-off sale rates against regular prices of $78 and $198, locked in while the plan remains active. Frequently asked questions ## Quick answers Does Switchit have an iMessage API?+ No. Switchit is a video-first digital business card platform. Its cards can be shared by text, but that uses your own device and number and requires a person to tap send. There is no server-side send, inbound events, or delivery state. Switchit shares cards by text — isn’t that a messaging feature?+ It opens your phone’s Messages app with a link prefilled. The message comes from your personal number and needs a human to send it. Nothing about it can be automated, sent on behalf of a team, or tracked for delivery. How do I send a video follow-up over iMessage?+ Upload the video as an attachment and reference it on the send. Because iMessage has no captions, send a short line of context as one message and the video as the next, and keep the file small enough to arrive quickly on cellular. How do I get contacts out of Switchit?+ A HubSpot integration is documented; beyond that the public developer material is thinner than for competitors, so confirm what your plan exposes. If the export is not real-time, adjust the follow-up copy to match the actual delivery latency. Primary sources ## Read the documentation. - [CTIA: Messaging Principles and Best Practices (May 2023)](https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf) - [Miss Blue API documentation — attachments and sends](https://missblue.dev/docs) - [Miss Blue: iMessage API and conversation events](https://missblue.dev/imessage-api) Explore the platform ## Turn the research into a working conversation. [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 industry teams ### iMessage use cases See practical playbooks for real estate, plumbing, HVAC, roofing, and home services. Explore](https://missblue.dev/use-cases) [Miss Blue Research ### iMessage vs SMS study Read the beta observations, reported benchmarks, methodology, caveats, and pilot framework. Explore](https://missblue.dev/imessage-response-rate-study) Ready to build? ## Send your first blue bubble with Miss Blue. [Explore the iMessage API](https://missblue.dev/imessage-api)