# The Best iMessage Automation for Canada in 2026: Tuco AI vs Sendblue

> Canada is a more iMessage-dense market than the United States, and not one vendor in this category has published a word of Canadian delivery data — so we published ours

*By BG · Published 2026-10-03T00:00:00.000Z*

**Canonical URL:** https://tuco.ai/blog/best-imessage-automation-canada-sendblue-alternative
**Tags:** iMessage automation, Canada, Sendblue alternative, CASL, A2P 10DLC, Sendblue

## Summary

Canada runs 64.87% iOS — more than the US — yet A2P 10DLC does not exist there. We measured 1,415 iMessages to 635 Canadian numbers. Tuco AI vs Sendblue.

---


**Canada is a better iMessage market than the United States and a worse SMS market, which is why the two should not share a playbook.** 64.87% of Canadian mobile page views are iOS versus 53.59% in the US, and A2P 10DLC — the registration that makes automated SMS deliverable south of the border — does not exist in Canada at all.

We make one of the two products compared here, so read this as a first-party argument with the data attached. The query, the sample sizes, the checks that failed and the places Sendblue is the better buy are all below.

### What "best for Canada" means here, exactly

Nobody has named us anything. **There is no third-party ranking of iMessage automation tools for Canada, and as of October 2026 Tuco AI has no G2, Capterra or Trustpilot profile** — a competitor's own review page says so, and they are right. Treat any vendor claiming an award in this category with suspicion, including us.

So the claim in the title is narrow, and it is falsifiable. On one specific test — **publishing measured Canadian delivery data** — we are the only vendor in this category who has done it:

| The claim | How to falsify it |
|---|---|
| No iMessage vendor publishes Canadian delivery data | Find one. We checked Sendblue, Blooio, Linq Blue and LoopMessage |
| Sendblue's site never mentions Canada | `curl` it and grep. Command is below |
| Canada beats the US on our iMessage hit rate | 76.5% vs 70.6%, method and sample in the Methodology section |
| Our Canadian reply rate is trustworthy | **It is not.** It fails our own concentration gate. We say so below |

If what you need is SOC 2, a HIPAA BAA, group chats or FaceTime, we are not the best anything for you and the section near the end says which vendor is.

## The short answer

| Question | Answer |
|---|---|
| Which market is more iMessage-dense? | **Canada.** 64.87% iOS vs 53.59% US (StatCounter, Sept 2026) |
| Does A2P 10DLC apply in Canada? | **No.** It is a US carrier framework. Canadian carriers never adopted it |
| What is the Canadian A2P SMS route? | Short codes — **12–16 weeks**, ~$500–$1,000/month |
| Does any vendor publish Canadian support? | **No.** Zero "canad" matches across 1.59 MB from 4 vendors |
| Is Sendblue the same company as Raz? | **Yes** — Raz came first, `tryraz.com` redirects to sendblue.com |
| Can Sendblue's published tier do outbound? | **No.** $100/mo is inbound-first; outbound is quoted on request |
| Does CASL apply to iMessage? | **Yes.** "Instant messaging account" is named in the Act |
| Has anyone measured Canadian iMessage delivery? | We have — **1,415 sends, 635 numbers, 42 area codes** |

## Why does Canada need its own answer?

Because the thing that makes iMessage automation work is iPhone density, and Canada has more of it than the United States.

![Bar chart comparing mobile operating system share in Canada and the United States for September 2026. Canada is 64.87% iOS and 35.13% Android; the United States is 53.59% iOS and 46.39% Android.](/blog/canada/canada-vs-us-ios-share-2026.png)

That 11.3-point gap is the entire commercial case. Every argument for iMessage over SMS — the blue bubble, read receipts, typing indicators, no per-message carrier fee, no character limit — applies to a larger share of the addressable market in Toronto than in Chicago.

Our own sends agree. Of 1,308 completed sends to Canadian numbers, 1,000 went out over iMessage: **76.5%**, against **70.6%** for the same platform's US traffic over the same period. Canada runs 5.9 points hotter.

## What happens when you try to run A2P SMS in Canada?

You discover that the US compliance work you already did does not transfer.

A2P 10DLC is a framework the American carriers built. Canadian carriers never adopted it, so there is no Canadian 10DLC registration to complete — and no registered-sender status to earn. [Twilio's Canada SMS guidelines](https://www.twilio.com/en-us/guidelines/ca/sms) are blunt about what is left:

> Canadian mobile carriers enforce strict filtering on A2P messages. Carriers will not cease filtering, but mobile subscribers may wish to reach out to their mobile carrier to petition them to do so.

Twilio recommends short codes or verified toll-free numbers for A2P traffic in Canada. Its published short-code provisioning time is **12 to 16 weeks**. Alphanumeric sender ID is marked **not supported**.

![Two-panel comparison. Left: 76.5 percent of 1,308 completed Tuco sends to Canadian numbers went over iMessage versus 70.6 percent for US traffic. Right: the Canadian A2P SMS route requires a short code at 12 to 16 weeks provisioning and 500 to 1,000 dollars per month, with 10DLC not applying and alphanumeric sender ID unsupported.](/blog/canada/canada-imessage-vs-a2p-sms.png)

The honest half of that picture is in the grey box: 282 of our Canadian sends (21.6%) found no iMessage account and dropped to the fallback path, and exactly one was actually forwarded as an SMS. On 211 of 630 Canadian contacts we have never landed a blue bubble. Anyone telling you iMessage automation is a complete Canadian channel on its own is selling you the 76.5% and hiding the rest.

If you want the longer version of the A2P argument, we wrote it up separately in [how to send SMS without A2P 10DLC](/blog/how-to-send-sms-without-a2p-10dlc).

## Does Sendblue support Canadian numbers?

Their documentation does not say, in either direction.

We fetched every public Sendblue marketing and docs page we could reach and grepped the rendered HTML for `canad`, case-insensitive. Across 532,575 bytes the string appears zero times. The docs FAQ gets closest, noting that "dedicated numbers are priced differently depending on country, area code, functionalities, and use-case" — without naming a single country.

![Audit table showing a curl and grep command run against Sendblue, Blooio, Linq Blue, LoopMessage and Tuco AI pages on 3 October 2026. Every competitor page returns zero matches for the string canad, totalling 1,593,765 bytes across eight pages from four vendors. Tuco's own homepage and pricing page also return zero. Only a Tuco help centre article returns 8 matches.](/blog/canada/sendblue-tuco-canada-mention-audit.png)

Run it yourself:

```bash
curl -sL https://sendblue.com | grep -oic canad
```

We are not scoring a point with that table. **Our own homepage and pricing page mention Canada exactly as often as everyone else's do — never.** The only page in the whole category that addresses Canadian numbers is a Tuco help-centre article. Marketing copy is not the differentiator here; production data is, and that is the next section.

It is not just Sendblue, either. We ran the same grep across Blooio, Linq Blue and LoopMessage: **zero occurrences of `canad` across 1,593,765 bytes and eight pages from four vendors.** Nobody in this category has written a Canadian page. That is the gap this article exists to fill.

### Who is Sendblue, exactly? (It used to be Raz)

Worth knowing if you are evaluating them, because the name has changed and the old one is still visible in the plumbing.

Sendblue is **Round One Inc.**, 344 West End Avenue, New York. It went through Y Combinator's **Summer 2023** batch, founded by Rob Haber (CEO, previously an ML engineer at Scale AI) and Alex Luis (previously a PM at PwC). The company now has around 50 people.

Before it was Sendblue, it was **Raz** — an AI forms product. The evidence is still sitting on their own site:

| Artefact | What it shows |
|---|---|
| `tryraz.com` | **301-redirects to sendblue.com** |
| Their Webflow stylesheet | served as `raz-2025.webflow.shared.*.min.css` |
| Their partner program script | loads from `partners.tryraz.com` |
| Their YC launch post | titled *"Raz: Next-generation AI forms"*, signed "we are Rob and Alex, the co-founders of Raz" |

Their YC company page today reads "Sendblue — iMessage for Sales," and both founders' bios now say Sendblue. So the sequence is Raz first, Sendblue after a pivot, same founders and same corporate entity throughout. None of that is a criticism — pivoting is normal and the iMessage product is the real business now. It matters only because searching for reviews or documentation under the old name pulls up an AI forms company, which is confusing if you do not know why.

### The published-tier problem

Separately from geography, there is a structural issue with Sendblue's published pricing for anyone who wants to run outreach.

![Screenshot of Sendblue's pricing page showing three tiers: Free Sandbox at zero dollars with no outbound messaging, AI Agent at 100 dollars per month described as inbound-first messaging, and Enterprise at custom pricing listing full outbound messaging and a Contact Sales button.](/blog/canada/sendblue-pricing-inbound-only-enterprise-outbound.png)

The $100/month AI Agent tier is **inbound-first**: the contact has to text you before you can text them. Full outbound messaging sits in the Enterprise tier, priced on request. For a Canadian business that wants to start conversations — follow up on a lead form, chase a no-show, reactivate a dead pipeline — the published price is not a price at all. Our [Sendblue pricing breakdown](/blog/sendblue-pricing-2026-complete-breakdown) goes through the tiers in detail.

## What we actually measured in Canada

Every Canadian message row in our production database between 19 December 2025 and 3 October 2026.

![Horizontal bar chart of distinct Canadian mobile numbers messaged by area code. 647 Toronto leads with 89 numbers, then 416 Toronto 61, 604 Vancouver 46, 514 Montreal 45, 778 British Columbia 39, 403 Calgary 32, 437 Toronto 32, 226 Southwest Ontario 30, 905 Greater Toronto 24, 438 Montreal 20, 204 Manitoba 19, 613 Ottawa 19, 780 Edmonton 18 and 250 Interior BC 16. Totals: 635 numbers, 42 area codes, all 10 provinces, 20 workspaces.](/blog/canada/tuco-canadian-area-code-coverage.png)

| Measure | Canada | US control |
|---|---|---|
| Outbound message rows | 1,415 | 53,590 |
| Completed sends over iMessage | **76.5%** (1,000 / 1,308) | 70.6% (32,971 / 46,725) |
| Dropped to fallback | 21.6% (282) | 27.3% (12,773) |
| Distinct numbers messaged | 635 | 22,726 |
| Numbers reached over iMessage at least once | **54.9%** | 51.3% |
| Numbers that replied | **12.76%** (81) | 14.40% (3,272) |
| Distinct area codes | 42 | — |
| Customer workspaces sending | 20 | — |

Canada beats the US on every delivery measure here and loses narrowly on reply rate. Both findings need a concentration check before anyone leans on them.

### The check that passed, and the one that failed

This is the part most vendor comparisons skip, and it is the reason we published [the copy-rules study](/blog/imessage-copy-rules-tested-45217-messages) that found six of seven popular texting rules were really one customer's house style.

**The delivery finding passes.** Eight workspaces sent 20 or more Canadian messages; the largest contributed 30.0% of completed sends, under our 40% single-account ceiling. Per-workspace iMessage rates range from 41.7% to 100%. The Canada-beats-US delivery gap survives.

**The reply-rate finding fails.** One workspace supplied 284 of 635 Canadian numbers — **44.7%**, over the ceiling — and it replies at 2.8%. Per-workspace Canadian reply rates run from 0% to 53.4%. The pooled 12.76% is an average over wildly different audiences, so treat the Canada-vs-US reply comparison as indicative and nothing more.

There is a third measurement we ran and will not report as a finding. Our iMessage availability probe returned 313 available and 186 unavailable for Canadian numbers — 62.7% of 499 conclusive checks, which is *lower* than the US figure of 67.4% and therefore points the opposite way to both StatCounter and our own send data. With 499 Canadian checks against 19,441 US ones, and a different population (leads uploaded for checking, not leads messaged), we think the send data is the better evidence. We are flagging the disagreement rather than quietly dropping it.

## Tuco AI vs Sendblue for a Canadian business

| | Tuco AI | Sendblue |
|---|---|---|
| Published price that can send outbound | **$149/mo** + $335 setup | Not published — Enterprise quote |
| Published entry price | $149/mo (outbound included) | $100/mo (inbound-first) |
| Entry tier can message a lead first | **Yes** | No |
| Canadian production data published | **1,415 sends, 635 numbers** | None found |
| Canadian area code live today | **Yes** — +1 647 Toronto | Not published |
| Mentions Canada on its site | No | No |
| Billing | Monthly or annual | Quarterly |
| SOC 2 Type II | No | **Yes** |
| HIPAA BAA | No | **Yes** |
| Group chats / FaceTime | No | **Yes** |
| Chrome extension | No | **Yes** |
| GoHighLevel native | **Yes** | Yes |
| HubSpot native | Yes | Yes |
| MCP server for AI agents | **Yes** | No |
| Automatic opt-out keyword handling | **Yes** — 5 keywords, terminal block | Not published |

Pricing is from [our pricing page](/pricing) and Sendblue's, both read on 3 October 2026. The full feature-by-feature version lives on [the Sendblue comparison page](/compare/sendblue).

## Does CASL apply to iMessage?

Yes, and this is worth getting right because the opposite is widely assumed.

Canada's Anti-Spam Legislation does not care which app carries the message. The Act defines an electronic message as "a message sent by any means of telecommunication, including a text, sound, voice or image message," and defines an electronic address to include "(b) an instant messaging account" and "(c) a telephone account." A commercial iMessage to a Canadian number is inside both definitions.

What section 6 requires of every commercial electronic message:

| Requirement | Source |
|---|---|
| Express or implied consent before sending | CASL s.6(1)(a) |
| Identify the sender, and whoever it is sent on behalf of | s.6(2)(a) |
| Contact information valid for **at least 60 days** | s.6(3) |
| A working unsubscribe mechanism | s.6(2)(c), s.11(1) |
| Unsubscribe honoured "without delay," and **no later than 10 business days** | s.11(3) |
| Maximum penalty: **$1,000,000** individual / **$10,000,000** otherwise | s.20(4) |

Enforcement sits with the CRTC. Penalties are assessed per violation.

On our side, inbound replies matching any of five opt-out keywords — `stop`, `unsubscribe`, `opt out`, `remove me`, `do not contact` — are written to a do-not-contact list on the inbound webhook, in the same request, and the send planner treats that as a terminal block at priority zero before any other rule is evaluated. Fleet-wide that has fired 30 times automatically. Zero Canadian numbers are currently on it.

That is faster than CASL's 10 business days, but it is not a compliance product and we will not pretend otherwise: consent capture, sender identification and record-keeping are yours to run.

## What Tuco does not do for Canada yet

Four things, stated plainly, because you will find them out in week one otherwise.

1. **We provision US +1 numbers by default.** Our help centre says Tuco is "primarily built for US (+1) phone numbers" and that our carrier contracts are with US eSIM providers such as T-Mobile. A US +1 number messages Canadian numbers with no geographic restriction — that is how all 1,415 sends in this article were delivered — but it is a US number.
2. **The Canadian line is new.** One +1 647 Toronto line, provisioned 1 October 2026, healthy, and carrying zero traffic at the time of writing. Canadian-carrier lines go through support, not self-serve checkout.
3. **A specific area code needs a registered entity at that address.** Same rule as the US. No Canadian entity, no guaranteed 647.
4. **No SOC 2 Type II and no HIPAA BAA.** Sendblue has both. If your procurement team requires either, that decision is already made and it is not us.

## Where Sendblue is the better pick

If you need SOC 2 Type II or a signed HIPAA BAA, Sendblue has them and we do not. If your use case is genuinely inbound — a support line, an AI agent that answers people who text in first — their $100/month tier is well-priced for exactly that and you should take it. If you need group chats, FaceTime or a Chrome extension, those are theirs and not ours.

The case for us is narrower and specific: published outbound pricing, a platform that can start the conversation on its entry tier, and the only Canadian delivery data either of us has put in public.

## How to start, in Canada, this week

1. **Check your list first.** Run your Canadian numbers through the [free iMessage checker](/tools/imessage-checker). On our data roughly three in four Canadian sends land as iMessage — knowing which quarter will not is the difference between a working sequence and a silent one.
2. **Decide the fallback deliberately.** 21.6% of Canadian sends found no iMessage account. Plan email, phone or a Canadian SMS route for them before launch, not after.
3. **Get consent right before volume.** CASL's express-or-implied consent test, 60-day contact validity and 10-business-day unsubscribe apply from message one.
4. **Start on one line.** [$149/month plus $335 setup](/pricing), monthly billing, outbound included. If you are leaving Sendblue, the [migration guide](/blog/sendblue-to-tuco-migration-guide) covers the port.

## Methodology

Message-level figures come from the Tuco AI production MongoDB, filtered to recipient phone numbers matching Canadian NANP area codes, 19 December 2025 to 3 October 2026. 1,415 outbound rows, 239 inbound rows, 635 distinct numbers, 42 area codes, 20 workspaces.

iMessage success counts rows in status `sent` or `delivered`. The denominator counts only terminal statuses — `sent`, `delivered`, `fallback`, `failed` — and excludes `queued`, `scheduled` and `cancelled`, which have no outcome yet. "Fallback" means the platform found no iMessage account for that number and routed to the SMS fallback path. Reply rate is per distinct number: replied if any inbound row exists for that number. Features were computed inside the database query; no message content was read or exported.

The concentration gate is the one we use on all internal findings: no single customer workspace may contribute more than 40% of an arm. The delivery finding clears it at 30.0%; the reply-rate finding does not, at 44.7%, and is labelled accordingly.

The vendor audit fetched the rendered HTML of each page once with `curl` and counted case-insensitive matches for `canad`: sendblue.com and /pricing, docs.sendblue.com/faq/ and /llms.txt, blooio.com and /pricing, linqapp.com, loopmessage.com and /pricing — 1,593,765 bytes, zero matches. Tuco's own homepage and pricing page were run as a control and also returned zero. Corporate history for Sendblue comes from its [Y Combinator company page](https://www.ycombinator.com/companies/sendblue) (Summer 2023, founded 2023, Rob Haber and Alex Luis), its own site footer (Round One Inc., 344 West End Avenue, New York), and the live redirect from `tryraz.com` to `sendblue.com`.

External figures: [StatCounter GlobalStats](https://gs.statcounter.com/os-market-share/mobile/canada) mobile OS market share for September 2026, which measures page views rather than handset ownership. [Twilio's Canada SMS guidelines](https://www.twilio.com/en-us/guidelines/ca/sms) for short-code provisioning time, sender ID support and carrier filtering. [CASL, S.C. 2010, c. 23](https://laws-lois.justice.gc.ca/eng/acts/E-1.6/) for every statutory requirement and penalty quoted. Vendor pricing and the Canada-mention audit were read on 3 October 2026 and will drift; the commands are in the article so you can re-run them.


## Frequently Asked Questions

### Does Sendblue support Canadian phone numbers?

Sendblue's public documentation does not say. We fetched sendblue.com, its pricing and CLI pages, the docs FAQ and docs llms.txt on 3 October 2026 — 532,575 bytes in total — and the string "canad" appears zero times, case-insensitive. The docs FAQ states only that "dedicated numbers are priced differently depending on country, area code, functionalities, and use-case" without naming any country. Sendblue is Round One Inc. of New York — the same company that was previously Raz. To get a definitive answer on Canadian provisioning you would have to ask their sales team, because it is not published.

### Was Sendblue previously called Raz?

Yes. Sendblue and Raz are the same company — Round One Inc. of New York, Y Combinator Summer 2023, founded by Rob Haber and Alex Luis. Raz was an AI forms product and came first; the company pivoted to iMessage and became Sendblue. The old identity is still visible on their own infrastructure: tryraz.com 301-redirects to sendblue.com, their Webflow stylesheet is still served as raz-2025.webflow.shared.min.css, their partner-program script loads from partners.tryraz.com, and their Y Combinator launch post is titled "Raz: Next-generation AI forms" and signed "we are Rob and Alex, the co-founders of Raz." Their YC company page now reads "Sendblue — iMessage for Sales." Pivoting is unremarkable; it matters only because searching the old name surfaces an unrelated-looking forms product.

### Who is the best iMessage automation provider for Canada?

No independent body ranks iMessage automation tools for Canada, and as of October 2026 Tuco AI has no G2, Capterra or Trustpilot profile — so treat any award claim in this category, including ours, as marketing. On the narrow and checkable test of publishing measured Canadian delivery data, Tuco AI is currently the only vendor that has done it: 1,415 outbound messages to 635 distinct Canadian numbers across 42 area codes and every province, with 76.5% of completed sends going over iMessage against 70.6% for the same platform's US traffic. We grepped Sendblue, Blooio, Linq Blue and LoopMessage for the string "canad" across 1,593,765 bytes of their public pages and found zero occurrences. If your requirement is SOC 2 Type II or a HIPAA BAA rather than Canadian delivery evidence, Sendblue has both and Tuco AI has neither.

### Is A2P 10DLC required to send SMS in Canada?

No, because 10DLC does not exist in Canada. A2P 10DLC is a framework created by the US carriers, and Canadian carriers never adopted it, so there is no Canadian 10DLC registration to complete. The practical consequence is worse, not better: Twilio's Canada guidelines recommend short codes or verified toll-free numbers for application-to-person traffic, list short code provisioning at 12 to 16 weeks, mark alphanumeric sender ID as not supported, and state that "Canadian mobile carriers enforce strict filtering on A2P messages." iMessage avoids this path entirely because it is carried by Apple rather than by Rogers, Bell or Telus.

### Does CASL apply to iMessage?

Yes. iMessage is not a CASL loophole. Canada's Anti-Spam Legislation defines an "electronic message" as "a message sent by any means of telecommunication, including a text, sound, voice or image message," and defines an "electronic address" to include "an instant messaging account" and "a telephone account." A commercial iMessage sits squarely inside both definitions. You need express or implied consent, sender identification, contact details valid for at least 60 days, and an unsubscribe mechanism honoured no later than 10 business days. Maximum penalties are $1,000,000 for an individual and $10,000,000 for any other person.

### Do Canadian numbers reply less than American ones?

Slightly less in our data, and the gap is small enough that we would not act on it. Across 635 distinct Canadian numbers, 81 replied — 12.76%. The US control over the same period was 3,272 replies from 22,726 numbers, or 14.40%. That is a 1.6 point difference. We also have to flag that the Canadian figure fails our own concentration gate: a single customer workspace contributed 44.7% of the Canadian numbers, and per-workspace reply rates range from 0% to 53.4%. Audience dominates geography.

### Can Tuco AI give me a Canadian area code?

We have one live Canadian line today — a +1 647 Toronto number, provisioned 1 October 2026, healthy at the time of writing and carrying no traffic yet. Our help centre is explicit that Tuco is primarily built for US (+1) numbers and that our carrier contracts are with US eSIM providers such as T-Mobile, so +1 US numbers are what we provision by default. Canadian-carrier lines go through support rather than self-serve checkout, and matching a specific area code requires a registered business entity at that address. A US +1 number can message Canadian numbers with no geographic restriction, which is how the 1,415 sends in this article were delivered.

### How was this measured?

Every message row in the Tuco AI production database whose recipient phone matches a Canadian area code in the North American Numbering Plan, between 19 December 2025 and 3 October 2026. That gives 1,415 outbound rows and 239 inbound rows across 635 distinct numbers, 42 area codes and 20 customer workspaces. iMessage success counts rows in status sent or delivered; the denominator counts only terminal statuses (sent, delivered, fallback, failed) and excludes queued, scheduled and cancelled. Reply rate is measured per distinct number: a number counts as replied if any inbound message exists for it. No message content was read or exported.