[All articles](https://missblue.dev/blog) Miss Blue field notes # Linq Blue pricing, and why there isn’t a number Linq publishes a free sandbox and an Enterprise tier priced by conversation. That is a legitimate way to sell, and it means a comparison table with a dollar figure next to Linq is showing you something nobody published. Here is how to price it yourself. Published August 27, 2026 12 minute read In this guide [What Linq publishes](#section-1) [Why third-party price tables for Linq are unreliable](#section-2) [What “talk to an expert” pricing usually means](#section-3) [Build the quote request yourself](#section-4) [Ask what the unit is before you ask what it costs](#section-5) [Multi-channel changes the comparison](#section-6) [What the rest of the market publishes](#section-7) [Use the free sandbox for what it can settle](#section-8) [Terms to pin down before signing](#section-9) [Where Miss Blue sits](#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 ## What Linq publishes As of August 27, 2026, Linq’s pricing page presents two tiers: a free sandbox that needs no credit card and only an email verification to start building, and an Enterprise production tier fronted by a “Talk to an Expert” call to action. No dollar figure appears for production. The page positions the product as a cost-effective alternative to pay-per-message solutions and describes Enterprise as supporting API or CRM integration across iMessage, RCS, SMS, and Voice, scaling to millions of messages. It publishes no entitlement table alongside that claim. - Free sandbox — no credit card, verify your email, start building - Enterprise — API or CRM integration across iMessage, RCS, SMS, and Voice - Production pricing — not published; contact sales - No published per-line, per-message, or per-seat entitlements 02 ## Why third-party price tables for Linq are unreliable Comparison articles routinely print a monthly figure beside Linq. Because Linq does not publish one, those numbers come from somewhere else — an old quote, a competitor’s estimate, or an outright guess — and they are frequently reproduced without a source or a date. Treat any Linq price you did not receive in writing from Linq as fiction. That includes the figure on this page, which is why there isn’t one. 03 ## What “talk to an expert” pricing usually means Quote-based pricing is not a red flag on its own. It typically signals that the deal shape varies enough — lines, channels, volume, integration scope, implementation effort — that a single published number would misprice most customers. It does have consequences for you as a buyer. You cannot budget before a sales conversation, you cannot compare on price without one, and you have no public anchor to negotiate against. Plan the evaluation accordingly: get the quote early, not after you have already invested in a technical trial. 04 ## Build the quote request yourself Write one scenario before you contact any vendor and send the identical scenario to each. This is the only way to get comparable numbers out of a quote-based process, and it takes about twenty minutes. Be specific about peak rather than average. A quote built on your average month will be repriced when your peak arrives. - Number of lines at peak, and what drives adding one - Whether you initiate conversations or only answer them - Monthly outbound messages and expected inbound replies - Channels needed — iMessage only, or RCS, SMS, and Voice too - Teammates who need inbox access - CRM systems that must be integrated, and by whom - Contract length and what happens at cancellation - Support response commitment when delivery degrades 05 ## Ask what the unit is before you ask what it costs The first question is not “how much”, it is “what am I buying a unit of”. Per line, per message, per conversation, per seat, and per platform-plus-implementation are five different cost curves, and they diverge sharply at scale. Linq’s positioning against pay-per-message solutions suggests it is not selling a per-message unit, but positioning is not a contract. Get the unit named in writing, with the overage behavior beside it. 06 ## Multi-channel changes the comparison Linq describes Enterprise as spanning iMessage, RCS, SMS, and Voice. If you genuinely need all four, comparing it against an iMessage-only provider on price alone understates what you would otherwise assemble and operate yourself. If you need iMessage only, the reverse applies: you may be buying a platform sized for a problem you do not have. Decide which case you are in before the first call, because it determines whether a higher quote is expensive or a bargain. 07 ## What the rest of the market publishes For an anchor to bring into the conversation, here is what other providers published as of late August 2026, taken from their own pricing pages. The units differ, so this is a map rather than a ranking. Bringing published figures to a quote-based negotiation is useful. It converts an open-ended “what’s your budget” into a discussion about where a specific number sits relative to a specific market. - Miss Blue — $39/month shared testing number; $99/month per dedicated number with unlimited commercial usage, contacts, team access, Message Center, and API access - Sendblue — free sandbox; $100/month per line inbound-first; outbound on Enterprise quote - Blooio — $39 Starter, $89 Commercial Shared, $289 Commercial Dedicated, $109 Inbound, per month - Project Blue — $300/month plus $500 setup, or $166.50/month billed annually with setup waived - Blue Reacher — $249/month per line plus $449 one-time activation, waived on annual - Tuco AI — from $149/month plus a $335 one-time setup fee - Claw Messenger — from $5/month on a metered message allowance - Linq Blue — no published production figure 08 ## Use the free sandbox for what it can settle A no-credit-card sandbox is genuinely useful, and you should use it — but be clear about what it can and cannot tell you. It settles whether the API is pleasant, whether the documentation is accurate, and whether your integration is straightforward. It cannot settle the questions that decide the contract: production limits, outbound rights, deliverability at volume, support responsiveness during an incident, or price. Run the sandbox and the quote request in parallel rather than in sequence. 09 ## Terms to pin down before signing In a quote-based deal, the terms that are cheapest to negotiate before signing are the ones most expensive to discover afterwards. Number ownership and data export lead that list every time. Ask the same questions of every vendor. In the absence of a published price, precision in the answers is the main signal you have about how the relationship will run. - What is the unit, and what is the overage rate? - What are the per-line daily and monthly conversation limits? - Is outbound permitted on the quoted tier, in writing? - Who owns the number if we leave, and can it be ported? - Can we export full conversation history, and in what format? - What is the contract length, and what is the exit notice? - What is the contractual support response during a delivery incident? 10 ## Where Miss Blue sits Miss Blue publishes its prices: $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. Optional managed Conversational AI is $100 per month plus a one-time $250 setup fee; a specific area-code request is a one-time $205 fee where inventory permits. Enterprise pricing is custom. The displayed $39 and $99 figures are current 50%-off sale rates against regular prices of $78 and $198, locked in while the plan remains active. If you want a published number you can budget against today, that is the difference. If you need iMessage, RCS, SMS, and Voice in one platform with implementation attached, a quote-based vendor may fit better — but get the quote before you build. Frequently asked questions ## Quick answers How much does Linq Blue cost?+ Linq does not publish a production price. Its pricing page presents a free sandbox and an Enterprise tier behind a “Talk to an Expert” call to action. Any dollar figure you see elsewhere did not come from Linq’s published page. Retrieved August 27, 2026. Is there a free Linq tier?+ Yes — a sandbox requiring no credit card, just email verification, intended for building against the API. It will not answer questions about production limits, outbound rights, or price. Why do comparison sites list a price for Linq?+ Because a table with a blank cell looks incomplete. Those figures come from old quotes, competitor estimates, or guesses, and are usually printed without a source or date. Treat only a written quote from Linq as real. What should I ask for in a quote?+ The unit being priced and its overage rate, per-line conversation limits, whether outbound is permitted in writing, number ownership at exit, data export format, contract length, and the contractual support response during a delivery incident. Primary sources ## Read the documentation. - [Linq official pricing (retrieved August 27, 2026)](https://linqapp.com/s/pricing) - [Miss Blue official pricing](https://missblue.dev/pricing) 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)