Yes. There are four ways, and they are not close to equivalent. Ranked by how well they survive contact with a real business:
| Approach | Cost | Holds up in production? |
|---|---|---|
| AppleScript on your own Mac | Free | No |
| Shortcuts automation | Free | No |
| Self-hosted bridge (BlueBubbles) | Free + a Mac | Barely |
| A managed provider | $40–200/mo | Yes |
1. AppleScript on your own Mac
macOS lets you script the Messages app. A few lines of AppleScript will send a message to a number, and this is the answer most people find first because it is free and it genuinely works.
tell application "Messages"
set targetService to 1st service whose service type = iMessage
set targetBuddy to buddy "+19998887777" of targetService
send "Your appointment is confirmed for Thursday at 2pm." to targetBuddy
end tellThis works. That is the problem — it works well enough to build something on, and then fails in ways that are hard to notice.
What breaks: the Mac has to be awake, unlocked and signed in. macOS updates change Messages' scripting behaviour without warning. There is no delivery confirmation you can act on, no way to receive replies programmatically, and no record of what sent. When it silently stops, you find out because a customer did not show up.
2. Shortcuts
Apple's Shortcuts app can send messages on a trigger, and on iOS it can run automations on a schedule or an event. For personal use — texting your partner when you leave work — it is genuinely good.
For business it fails on the same axis as AppleScript plus one more: many Shortcuts message actions require confirmation on the device. An automation that needs someone to tap a button is not automation.
3. A self-hosted bridge
BlueBubbles is the serious version of the DIY approach: an open-source server that runs on a Mac you own and exposes a real API, including receiving messages. It is free, it is legitimate software, and it does what it says.
It also means you now operate a Mac as production infrastructure — always on, always signed in, with your office internet as the uptime story and every macOS update as an unscheduled outage risk. There is a fuller comparison in BlueBubbles vs a paid API.
The risk that is easy to miss
All three free approaches send from your personal Apple ID. A personal account sending business volumes can be flagged, and when it is, you have lost your own iMessage — not just the automation. Managed providers isolate that risk onto infrastructure they own. See why numbers get flagged.
4. A managed provider
You send a web request; they send the message from a phone number provisioned for your business. You get delivery confirmations, inbound replies as events your software can act on, and somebody to call when it breaks.
Costs roughly $40–200 a month depending on provider and whether the number is dedicated. All five compared here, and four of them let you build and test for free before paying.
How to choose
- Personal use, a few messages: Shortcuts or AppleScript. Genuinely fine.
- A side project or an experiment: BlueBubbles, on a Mac you do not mind babysitting.
- Anything a customer depends on: a managed provider. Not because the free options cannot send — they can — but because you need to know when they did not.
The dividing line is not technical capability. It is whether a silent failure costs you a customer. Once the answer is yes, free stops being cheap.