ZeroSettle vs Project Blue: iMessage for sales teams (2026)

How we compared ZeroSettle and Project Blue

We compared ZeroSettle and Project Blue on what a sales team decides: price and buying process, channels, CRM and calling, webhooks, opt-outs, outbound limits and AI.

ZeroSettle is an iMessage API: a real phone number on real iMessage, running on Apple hardware we operate for you, that your code texts customers from and hears back on through a bearer token and signed webhooks. Project Blue Services LLC sells iMessage lines for sales reps, with SMS fallback, built into GoHighLevel, HubSpot and Close. New to the category? Read what an iMessage API is.

Project Blue facts come from its own pages, read October 8, 2026. Other vendors are on the iMessage API comparisons hub and in 14 iMessage API providers compared.

ZeroSettle vs Project Blue at a glance

Project Blue is built around reps working inside a CRM, with calling and SMS fallback. ZeroSettle is built around your own code, with signed webhooks, platform-enforced STOP and a hosted agent.

ZeroSettle cells: ZeroSettle API docs and zerosettle.io. We re-check every Project Blue cell quarterly.

How do price and buying process compare?

For one rep, ZeroSettle Pro costs $49 a month with no setup fee and no demo, while a Project Blue line costs $300 a month plus setup, or $1,998 a year up front, after a demo.

Project Blue's monthly price per line is $300 for 1 line, $250 for 2–10 and $200 for 11+. Its monthly setup fee shows as $250 next to a struck-through $500, “($250 credited back at onboarding)”; the annual plan's $1,000 setup fee is waived. Sources: Project Blue pricing; the Dialer subscription is in its API reference.

Project Blue says it requires a demo to confirm your tech stack fits and to match you with “a dedicated rep who understands your industry”; its plans include implementation consultation and optimization check-ins. Its terms make payments “non-refundable once a billing period has begun”; leaving a commitment term early costs the rest of the term plus waived setup fees.

ZeroSettle Pro is bought in the console, with no free trial; instead, “ask within 30 days and you are refunded in full and the subscription is cancelled.” Numbers can sell out, with a waitlist. Growth starts with a demo, then ZeroSettle sends a signup link.

CRM, calling and sales features

Project Blue ships more for reps out of the box: CRM inboxes, calling, group chats and SMS fallback. ZeroSettle gives developers an API, a console and an AI connector; beyond its Close integration, CRM work is code you run.

• Project Blue in the CRM: GoHighLevel reps text from their usual inbox, a “Receive iMessage” trigger starts workflows, and a Chrome extension adds message and call buttons to every phone number; HubSpot and Close are integrated too. “Every rep texts from their own line.”
• Project Blue calling: a dialer with routing, recording, voicemail and transcripts; FaceTime Audio is an add-on, capped at 40 unique destinations a day per account.
• Project Blue extras: group iMessage of 2–32 (one Android participant drops the thread to SMS), send effects, AI voice memos “in your own voice”, porting and an MCP server.
• ZeroSettle: POST /api/imessage/send for texts, photos and voice messages; tapbacks; typing indicators both ways; your brand name and photo; a console your team answers from, where you can invite teammates; and an MCP connector that sets up the number and webhook.

ZeroSettle's native CRM integration is Close, which logs every message on the lead and can send from it; Salesforce is coming soon. The guide to logging iMessages in HubSpot or Salesforce covers the other CRMs.

Webhooks and opt-outs

ZeroSettle signs every webhook, retries failed message deliveries and blocks sends to anyone who texted STOP; Project Blue's webhooks are unsigned and single-attempt, and its API leaves STOP detection to you. For a team running follow-up sequences, those differences decide whether a reply or an opt-out slips through.

Project Blue cells quote its webhook support article and the Webhooks section of its API reference.

ZeroSettle's retries cover seconds, not hours, so a longer outage still needs polling (GET /api/imessage/messages?after_id=…); Project Blue advises “treat webhook delivery as best-effort.” The ZeroSettle webhook steps include Python and Node verifiers.

How each one handles STOP

On ZeroSettle, “When a contact texts STOP, the server records it and blocks your number (every number on your account) from reaching them.” Any text with the word STOP in it, or a clear request like “take me off your list”, counts, and only START (or unstop) opts them back in; later sends to that person return 403 recipient_opted_out. Only STOPs received since enforcement launched are recorded.

Project Blue “does not automatically detect or block STOP replies, and there is no built-in suppression list on the API today.” CRM workflows must “independently check opt-out/DND status,” and since webhooks are not retried, a STOP that lands during a receiver outage reaches your list only if you also poll.

A CRM sending through ZeroSettle should still mirror the opt-out list. Both calls follow the ZeroSettle API docs:

BASE=https://portal.zerosettle.io
# Everyone who has texted STOP, for your CRM's do-not-contact field
curl -s -H "Authorization: Bearer $ZEROSETTLE_TOKEN" $BASE/api/imessage/opt-outs
# {"opt_outs": [{"handle": "+18055550123", "opted_out_at": "2026-09-28T17:04:11Z"}]}

# The newest webhook delivery: ok, status_code, error, attempts
curl -s -H "Authorization: Bearer $ZEROSETTLE_TOKEN" $BASE/api/imessage/line | jq .last_delivery

More in how STOP and opt-outs work on a ZeroSettle line.

How do the outbound limits compare?

Project Blue allows 50 new numbers a day per line and queues the overflow; ZeroSettle allows 5 new contacts a day per number on Pro and 50 per number on Growth, and refuses the overflow with 429 new_contact_limit so your code decides when to retry. On both, a lead who texted first never counts.

ZeroSettle's day runs 3 AM to 3 AM Eastern. Project Blue column: its API Rate Limits article.

The math for an SDR texting 35 new form leads a day

• Project Blue, one line: 35 is under 50; the ~15-per-10-minutes cap queues a morning batch out over roughly 20 minutes.
• ZeroSettle Pro: 5 go out; the other 30 get 429 new_contact_limit until 3 AM Eastern. Pro does not fit this rep.
• ZeroSettle Growth: at 3 per 15 minutes, one number sends the 35th first text about 2 hours 45 minutes after the first. Three numbers share the load and finish in about 45 minutes.
• A five-touch cadence on either ZeroSettle plan: a lead who never replies gets 2 messages; the third returns 403 awaiting_reply.

The way around the new-contact caps is the same on both: get the lead to text first, for example from a button that opens Messages. The guide to real estate lead follow-up over iMessage walks through that pattern.

When ZeroSettle is not a fit (and Project Blue is the better choice)

Project Blue is the better choice when reps, not developers, run the conversations, or when you need calling, SMS or group chats.

• Your reps live in GoHighLevel or HubSpot and want iMessage there with no code.
• You need calling, with recordings and transcripts, or FaceTime Audio from the same number.
• Some leads use Android. ZeroSettle's docs: “The address must be on someone's iMessage; there is no SMS or email fallback.”
• A rep must keep an existing number. ZeroSettle numbers remain ZeroSettle's property.
• You close deals in group threads, or want send effects and AI voice memos in a rep's voice.
• You want onboarding built around your CRM, with implementation consultation and optimization check-ins in the plan.
• You want 50 new contacts a day on one line at a published price. ZeroSettle allows 50 a day per number only on Growth, priced after a demo.

When ZeroSettle is the better choice

ZeroSettle fits a developer or small team that wants to buy one number without a demo, wire it to its own code, and get signing, retries and STOP enforcement built in.

• No demo: Pro is $49 a month from the console, with unlimited messages with people who message you first and a money-back guarantee instead of non-refundable periods.
• Webhooks you can verify and debug, plus STOP enforcement, so a CRM sequence sending through ZeroSettle cannot text anyone who has texted STOP to one of your numbers.
• A hosted AI agent: with “Managed by AI Agent” (Beta), “our hosted agent answers every inbound text on the group's lines, from your business context,” working toward a demo_booked goal with your booking link. Pro includes 1,000 AI credits a month, one per text (AI agent docs).
• A live stream (server-sent events at /api/imessage/stream) for your own rep dashboard.

Compare ZeroSettle's plans, read the API docs, or get a number.

How we checked

We read Project Blue's public pages and support articles on October 8, 2026 and viewed its status page; we did not buy a Project Blue line, book its demo, or test delivery on either product.

1. Project Blue's home, pricing, messaging, dialer and GoHighLevel pages, API reference, terms, and three support articles.
2. Project Blue's status page: “All services are online”, Messaging Gateway “100% uptime” over about 90 days. Its messaging page says both “99.9% uptime” and “Uptime 99%”.
3. ZeroSettle's docs, homepage and terms. ZeroSettle reports “99.9% uptime” on its homepage, a published figure, not an SLA.

Neither vendor promises delivery: Project Blue “does not guarantee message delivery,” and ZeroSettle's terms say “delivery of any particular message or feature is not guaranteed.”