Send iMessages from Gmail — The Email Bridge No Competitor Offers

Every iMessage automation platform assumes you will use their dashboard or API. Tuco does too — but it also offers something no competitor has: the ability to send an iMessage by sending an email.

No API key. No code. No new tool to learn. Just compose an email.

What Competitors Require

To send an iMessage with Linq Blue, Sendblue, or Blooio, you need to either:

1. Log into their dashboard and send from there
2. Use their REST API (requires developer resources)
3. Set up a CRM integration (requires CRM access and configuration)

All three approaches work. But they all require your team to learn a new interface or invest engineering time. For a customer success team that lives in Gmail, that is a barrier.

How the Email Bridge Works

Four steps. No setup beyond adding your email to the sender allowlist.

Step 1: Compose a new email in Gmail (or Outlook, or any email client).

Step 2: Set the "To" field to the recipient's phone number at send.tuco.ai. For example: +12125551234@send.tuco.ai

Step 3: Write your message in the email body. Plain text only — the first line becomes the iMessage.

Step 4: Hit send. Tuco receives the email, extracts the phone number and message, and sends it as an iMessage from your Tuco line.

That is it. The recipient sees a normal iMessage in their Messages app. They have no idea it originated from an email.

Line Number Shorthand

If you have multiple Tuco lines, you can specify which line to send from using shorthand notation:

+12125551234-1@send.tuco.ai — sends from line 1

+12125551234-2@send.tuco.ai — sends from line 2

If you omit the line number, Tuco uses your default line. This is useful for teams that split outreach across multiple numbers for volume management.

Sender Allowlist for Teams

Not just anyone can send iMessages through your Tuco account by emailing send.tuco.ai. The Email Bridge uses a sender allowlist — only approved email addresses can trigger messages.

You manage the allowlist from your Tuco dashboard. Add your sales team's emails, your customer success team, your agency partners. Anyone not on the list gets their email rejected silently.

This means you can give your entire team iMessage sending capability without giving them dashboard access, API keys, or any Tuco training at all.

Use Case: Customer Success Follow-Ups

A customer success manager needs to send a follow-up after an onboarding call. They already have the client's phone number. They already have Gmail open.

Instead of logging into Tuco, finding the contact, and composing from the dashboard, they type:

To: +14155559876@send.tuco.ai

Body: Hey Sarah — great call today. I'm sending over the onboarding doc now. Text me here if any questions come up.

The client receives an iMessage. The CS manager never left Gmail. The whole process took 15 seconds.

For teams that send 5-10 follow-up messages per day, this saves meaningful time. For teams that send 50+, it is the difference between adoption and abandonment — if the tool is hard to use, people stop using it.

Who This Is For

The Email Bridge is built for teams where:

• The people sending messages are not technical (no API comfort)
• The team already lives in Gmail or Outlook and adding another tool creates friction
• You want to give iMessage access to people without giving them dashboard logins
• Quick one-off messages are more common than large campaign sends

If you are running high-volume campaigns with hundreds of messages, the dashboard or API is a better fit. The Email Bridge is for the ad-hoc, one-to-one messages that happen throughout the day.

Get Started

Add your team's email addresses to the sender allowlist in your Tuco dashboard, and start sending.

Full setup guide: tuco.ai/integrations/email-bridge

Questions? support@tuco.ai