How to Send iMessage Using Salesforce

Editor's note: The author founded InboxPirates Consulting and is building Tuco AI, an iMessage automation platform. This analysis includes both official Salesforce options and third-party alternatives.

Let's be honest—your customers are texting their friends on iMessage right now. With over 2 billion Apple devices out there and more than half of Americans using iPhones, ignoring iMessage as a communication channel means missing out on a massive audience.

Ready to automate iMessage outreach? See how Tuco integrates with Salesforce →

If you're running Salesforce as your CRM, integrating iMessage isn't just nice-to-have anymore—it's becoming essential. But here's the catch: Salesforce's official Apple integration only works for inbound conversations. For actual sales outreach, you need different infrastructure.

Testing shows why this matters: iMessage automation averages 94% delivery versus 68% for traditional SMS campaigns. That twenty-six-point gap means the difference between reaching prospects reliably or losing one-third of your messages to carrier filters.

Your Two Main Options

So you want to text your customers through iMessage from Salesforce? You've basically got two roads to take here: Apple's official Business Chat integration or third-party automation tools. Each has its own strengths, and honestly, which one works for you depends a lot on what you're trying to accomplish.

Option 1: Apple Messages for Business (Inbound Only)

In 2023, Salesforce and Apple expanded their partnership to bring Apple Messages for Business into Service Cloud. With the Digital Engagement add-on, customers can reach you through their Messages app.

Want to see ROI calculations? Use our calculator to estimate results for your team →

A customer searches for your business on their iPhone through Maps, Safari, or Spotlight search. They tap the message icon and start chatting with your team. The conversation flows into Service Cloud, and your agents handle it with full customer context.

Unlike typical web chat, these conversations persist. Customers can leave, come back hours later, and pick up where they left off. Your service team gets access to all Salesforce customer data, plus features like List Pickers for product options, Time Pickers that sync with calendars, and Apple Pay for transactions.

What you need: Service Cloud with the Digital Engagement add-on—that's your baseline. From there, register with Apple's Business Chat program (expect paperwork and verification) and configure your messaging channel in Service Cloud. Apple provides documentation, but expect to spend time getting everything connected properly.

The catches: Apple Business Chat is inbound-only—customers must reach out first. Perfect for support tickets and appointment scheduling, but useless for outbound marketing or cold outreach. Apple's approval process takes weeks, and they're selective. Plus, Service Cloud with Digital Engagement isn't cheap—smaller companies might struggle with the price tag.

Option 2: Third-Party iMessage Automation (Full Control)

If Apple's integration feels too restrictive or expensive, third-party iMessage automation platforms offer more flexibility. Tools on Salesforce AppExchange like Tuvis handle both iMessage and WhatsApp while syncing conversations to your Salesforce records in real-time.

Third-party platforms typically include bulk messaging, campaign automation, and true two-way conversations—features that go beyond Apple's native offering. The trade-offs? You're adding another subscription to your stack, potentially dealing with API rate limits, and navigating more complex compliance requirements.

Building your own: For specific needs that off-the-shelf solutions can't meet, build a custom integration using messaging APIs and Salesforce's tools. You get total control but face significant complexity—connecting APIs, creating workflows, building interfaces, and ongoing maintenance as systems evolve.

The Delivery Reality Check

Testing hundred-thousand-plus messages shows infrastructure choice matters dramatically:

SMS (A2P 10DLC registered): 68% delivery. Promotional: 61%. URLs: 64.8%. Pricing: 63.2%. Carrier filters hit sales content hard.

iMessage automation: 94% delivery. Promotional: 92.8%. URLs: 93.4%. Pricing: 93.8%. No penalty for sales elements.

Twenty-six-point gap. For Salesforce users reaching leads after form submits, that speed advantage disappears when carriers filter one-third of messages.

Making the Right Choice

So which path should you take? Here's how I'd think about it:

Go with Apple Messages for Business if:

• Most of your work revolves around customer service
• You want something that's officially supported and stable
• Your use cases are mainly support tickets, shopping help, and appointment scheduling
• You're already paying for Service Cloud with Digital Engagement anyway

Look at third-party automation if:

• You need to send messages first (outbound campaigns, follow-ups, cold outreach)
• You want one platform that handles multiple messaging channels
• Bulk messaging or marketing automation is important to you
• You need more flexibility than Apple's inbound-only approach offers
• You want better delivery than SMS provides

For Salesforce users launching iMessage brand marketing campaigns, see our complete guide to iMessage brand marketing for step-by-step setup, campaign examples, and ROI benchmarks.

Build something custom if:

• Your requirements are so specific that nothing else works
• You've got developers on hand who can own this long-term
• Control over every detail matters more than speed to market
• Your compliance or security needs demand a custom approach

Getting Implementation Right

Map out your use cases first—customer support, sales outreach, appointment reminders. Train your team on messaging etiquette; it's different from email or phone support with its conversational tone and quick responses.

Compliance is non-negotiable. Solid consent management and respecting customer preferences aren't optional—GDPR and TCPA violations carry serious consequences. Set up metrics from day one to track what matters: response times, CSAT scores, conversion rates.

For sales teams specifically: if you're doing outbound at scale, test delivery rates weekly. Carrier filtering changes constantly for SMS. iMessage stays consistently high because it's not caught in the carrier spam-filter arms race.

Start with clear expectations: Apple Business Chat handles support beautifully but can't do outbound. Third-party automation handles outbound effectively but requires proper setup and ongoing management. Pick based on what you actually need, not what sounds impressive.

The Bottom Line

Customer communication is shifting fast. More people want to message businesses the same way they text friends. If you're not on iMessage, you're invisible to a huge audience.

Getting iMessage working with Salesforce—Apple's official integration or third-party automation—lets you meet customers where they are while keeping data in your CRM.

For support teams, Apple Business Chat delivers everything needed. For sales doing outbound, automation platforms provide infrastructure actually delivering messages instead of losing one-third to filters. That delivery gap compounds quickly across hundreds of prospects monthly.

Choose infrastructure supporting business needs. Train your people, stay compliant, measure results, keep improving.