Scheduling iMessages: phone tricks vs business messaging tools

People search "how to schedule an iMessage" for two different reasons. Some want to send a birthday text at midnight without staying up. Others run a business and want texts to go out at 9 AM without someone at a phone. The first group has decent built-in options now. The second group runs into limits that the phone tricks were never built to handle.

This post covers both. It starts with the iPhone and Mac workarounds and where they stop working. Then it covers how scheduling works on a business messaging platform with blue-bubble (iMessage) support. That includes one limit you should know before you commit: scheduled campaigns and drip campaigns go out as SMS, not iMessage. We make Ready, so the business half uses our product as the example, with the real prices and limits.

The personal options: what your iPhone and Mac can do

Send Later in Messages

Recent versions of iOS added a native Send Later option in Messages. You write the message, tap the plus button, choose Send Later, and pick a time. The message waits in the thread until then. You can edit or cancel it before it goes. For one text to one person, this is the right tool. It's free, and the text arrives blue because it really is an iMessage from your Apple ID.

Some details, such as how far ahead you can schedule and what happens if your device is offline, have changed between iOS versions. Test it on your own device before you rely on it for something time-sensitive.

Shortcuts automations

Before Send Later existed, the common workaround was a Shortcuts personal automation. You trigger on a time of day, add a Send Message action, and turn off "Ask Before Running." It works for recurring texts, such as a daily "leaving work" message. It's clumsy for one-off dates, and if the automation is set to ask first, nothing sends until you tap the notification.

Mac workarounds

On a Mac, you can schedule iMessages with AppleScript, Automator or a calendar event that runs a script. These work, but they need the Mac to be awake, logged in and signed in to Messages at send time. If the laptop is asleep in a bag at 9 AM, nothing goes out.

Where the phone tricks break for a business

All of these send from a personal Apple ID. That's fine for a birthday text. It becomes a problem once a business depends on it:

• One person, one device. Scheduled messages sit on one person's phone. If that person leaves, goes on vacation or loses the phone, the follow-ups go with them. Nobody else can see what's queued.
• No shared inbox. Replies land on that one phone. Your team can't pick up the thread, and nothing is logged in a CRM.
• No opt-out handling. If someone replies STOP, nothing records it. The next scheduled text still goes, and texting someone who opted out is the kind of mistake TCPA claims are built on. Exposure is commonly cited at $500 to $1,500 per text.
• No quiet hours. A Shortcut set to 8 AM Eastern fires at 5 AM for a customer in California.
• No Android path. If the recipient has an Android phone, your iPhone usually falls back to SMS from your personal number. Your scheduled "blue" text turns green anyway, from a number that isn't registered for business traffic.
• Apple ID risk. Sending lots of similar texts to many people from a personal Apple ID isn't what iMessage was designed for. You're risking your personal account to save a few dollars.

None of this means you should stop using Send Later. It means it's a personal tool. Once more than one person needs to see a thread, or more than a handful of customers get the same text, you want a platform.

How scheduling works on a business platform

A business platform splits scheduling into two jobs. The difference affects whether your texts go out blue.

Job 1: timed sends to many people (campaigns and drip campaigns)

Reminders, follow-up series and announcements go through campaigns and drip campaigns. On Ready, campaigns and drip campaigns send from your regular numbers, not the blue line. That means they go out as SMS on your registered A2P 10DLC campaign, to iPhones and Android phones alike.

That's deliberate, and we think it's correct. Timed sends to many people are exactly the traffic that carriers want registered and that iMessage limits (more on those below). The compliance layer does the scheduling hygiene the phone can't:

• Quiet-hours enforcement. Sends are held outside permitted local hours, based on the recipient's area. A campaign or automation text sent during someone's quiet hours is held and sent later, and you're only charged when it actually goes out. A single text is held only when the window opens within about 6 hours; otherwise it is refused and not charged.
• Opt-out propagation. STOP is honored, and the number can't be texted again across campaigns. Opted-out numbers are refused up front and not charged.
• Attestation trail. Your opt-in attestation is recorded per bulk send and per API send that sets consent_attested: who sent, to how many, and when. This isn't a per-contact consent record. Your store or signup form still needs to keep when and how each person opted in.

For reminder timing and templates specifically, see our appointment reminder SMS guide.

Job 2: conversations that should feel personal (the blue line)

A blue line sends texts as iMessage. They show up blue on iPhones with your business name and photo. It needs no 10DLC registration, so you can start texting as soon as the line is set up. Unlike Apple Messages for Business, a blue line can text first. Our post on iMessage for business vs Apple Messages for Business covers that difference.

Blue lines are built for one-to-one conversations, and the limits reflect that:

• Unlimited texting with people you already talk to
• Up to 50 new conversations a day per line
• Up to 2 texts to someone until they reply
• Photos only after they reply

So the honest answer to "can I schedule a blue-bubble announcement to my whole list" is no, and the 50-new-a-day limit would stop it anyway. What you can do is run the personal follow-up on the blue line. Replies, reactions and typing indicators land in the same inbox thread as your SMS, so the customer sees one conversation.

Scheduling from your own app via the API

If you're a platform building scheduling into your own product, the usual pattern is this: your job queue holds the scheduled send, then calls the API at the right time. Send an Idempotency-Key so a retry doesn't send twice:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: 7f3c9a1e-2b4d-4e8a-9c61-0d5f2e8b7a13

{"to": "+12125550199", "body": "Reminder: your appointment is tomorrow at 10 AM. Reply C to confirm.", "consent_attested": true}

For larger lists, POST /v1/messages/bulk takes up to 100 recipients per call. Quiet hours still apply on our side, so a job that fires too early for a West Coast recipient is held rather than delivered at dawn. For blue-line sending from code, the request details are in the blue line API docs. Our post on an SMS API with iMessage fallback explains how blue and green land in one thread. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.

Phone tricks vs a business platform, side by side

What it costs: a worked example

Assumptions for this example: a business with one blue line sends 1,000 one-to-one texts a month, each 1 segment (under 160 plain characters, no emoji). It gets 400 replies. It also runs a monthly SMS reminder campaign to 2,000 consented contacts at 1 segment each.

Blue line:

• Line: $99
• Sent: 1,000 × $0.06 = $60
• Replies: 400 × $0.06 = $24
• Reactions: free
• Blue line total: $183/mo

SMS reminder campaign (Standard):

• 2,000 × $0.0075 = $15, plus 2,000 × $0.0045 carrier fee
• That's all-in, but it excludes the optional compliance surcharge. Scrubbing and landline validation are each $0.003 extra per segment when switched on, and both are off by default.
• Replies to SMS are billed like sent texts at the same rate.

Registration for the SMS side: no setup fee. You pay $25 at submit for the first month, then $25/mo for registration and $2 per number. Most approvals take 2 to 7 days.

Watch your segment counts. One emoji drops a segment to 70 characters, so a 140-character reminder with a smiley becomes 3 segments instead of 1. That triples the per-text cost on both SMS and the blue line.

Which approach fits you

• Texting friends and family: use Send Later. It's free and it's the right tool.
• Solo operator texting a few customers a week: Send Later works until you need a record of opt-outs or a second person on the thread. Once you do, move.
• Business sending reminders or follow-ups on a schedule: use SMS campaigns and drip campaigns on a registered number, with quiet hours and STOP handling built in.
• Business that wants the blue-bubble feel for conversations: add a blue line for one-to-one threads, and size it at 50 new conversations a day per line.

The practical takeaway

Scheduling one iMessage is a solved problem on the iPhone. Scheduling business texts is a different job: it needs opt-out handling, quiet hours, a shared inbox and a path for Android. Blue-bubble iMessage is best for conversations, not timed sends to a list, which is why campaigns go out as SMS.

If you want to try the business side, you can sign up with a card on file. Your first 20 one-to-one texts are free, so use them before you register. Pricing for each piece is on the pricing page.