[Blog](https://sparetext.dev/blog)

# Why texts leave your phone in seconds again: this week in Sparetext

We put alarms on every link between our server and your phones. The first one went off within minutes, and it was right. Here's what it found and what we changed.

Sparetext

5 min read · Nov 9, 2026 · Updated Nov 14, 2026

Last Monday we added alarms to Sparetext. Every link between our server and your phones would now tell us when it failed, instead of failing quietly in a log nobody reads. We put it on our test server, went to make tea, and by the time the water boiled the first alarm had gone off.

Honestly, my first thought was that the alarm was broken. It wasn't. The link that wakes your phone when a text is waiting had been failing for a while, and we had no idea.

## What was going wrong

When your script or your AI agent asks Sparetext to send a text, the text waits on our server and we wake your phone to come and get it. For that wake we used a free public notification service. It counts its free quota per internet address, and our server's requests leave from addresses shared with lots of other Cloudflare customers. So most days the quota was gone before we got there, and most of our wake-ups were refused.

Our old code never read the answer. A refused wake counted as a wake sent. That's the embarrassing part.

The good news is that no text was lost. Android phones also wake through Google's push, and every phone checks in once a minute anyway. But the Mac had only that service and its one-minute check, so a text from a Mac could sit for up to a minute before it left. For an SMS gateway that's supposed to feel instant, that's a long minute.

## Your phone now listens to us directly

We could have paid for a bigger quota. Instead we built our own wake channel. Each phone keeps one quiet line open to Sparetext, and when a text is waiting, the wake goes down that line. No shared quota, nobody else's traffic, and nothing new for you to set up.

On our test server we let a line sit quiet for more than three minutes, then queued a text. The phone heard about it two seconds later. The old service is still there as a backup, only for older apps and for a phone that isn't listening on the new line.

To get it, update to Android 1.8.1, Mac 1.4.2 or iPhone 1.5.0. A phone you pair from now on uses the new channel with any app version, and older apps keep working the old way.

## The iPhone tells you which half failed

Sending while an iPhone is locked works through a Shortcuts automation that starts when Sparetext's notification arrives. When it didn't run, we used to know only that much: it didn't run. Was the notification lost? Was it there and the automation just didn't start? You had to guess, and so did we.

iPhone 1.5.0 answers that. When the notification lands, the app quietly tells our server it arrived. So if a locked send doesn't happen, Home says either that the notification reached this iPhone but the automation didn't start, or that it never arrived, and the setup screen lists only the checks for that case. The Phones page in your dashboard says the same thing. The notification itself now says how many texts are waiting, like "2 texts are waiting to go out."

![The Sparetext iPhone app: three texts to 555 numbers waiting on this iPhone, the Pro plan at 1,204 of 10,000 texts this month, and two SIM cards on 5G and LTE.](https://sparetext.dev/blog/img/iphone-home.webp)

Home on the iPhone. When a locked send is missed, this is where it tells you why.

## Every link has an alarm now

The alarms stayed after they found their first bug. Each call to Apple's push, Google's push, our wake channel, our emails and the payment services writes down whether it worked. Three failures in a row and I get a message on Telegram, then another when it recovers. On our test server a pretend phone also sends a text through the whole chain every hour, wake included, so a broken link shows up there before it shows up for you. That pretend phone never reaches a carrier.

> A refused wake used to count as a wake sent. Now it rings a bell.

## Four bugs we found by looking at every state

The same week we went through every state a text, a recurring text and a SIM can be in, and asked what happens on each move. It found real bugs, and they're fixed:

- On a dual-SIM Android phone, a text that failed because one SIM lost service was supposed to go out from the other SIM. It got the old failure repeated back instead. Now it's a fresh send from the healthy SIM.
- Resuming a paused recurring text queued one text for every slot it missed. A daily reminder paused for 30 days would have texted each person 30 times. Now it picks up at the next slot from today.
- Retry on a text that failed on the iPhone now really sends it again (iPhone 1.4.0), instead of repeating the old failure.
- After a Mac updated because Sparetext needed a newer version, it stayed stopped until you paired it again. Mac 1.4.1 starts sending again by itself.

One more for campaigns: someone who opted out or said "wrong number" stays that way, even if their number shows up again in a later list.

## New accounts get a little help

Here's a number that bugged me: three of our four newest accounts signed up and never connected a phone. People who get stuck at install rarely write in to say why. So now they get a short email from Sparetext an hour after signing up, with the three ways to connect a phone. If there's still no phone two days later, a second one says what usually stops people, and a few days after that, a third just asks what happened. A day after a phone connects, one last email suggests up to three things you haven't tried yet, like an automation or a webhook.

Added on 14 November: once a phone connects, if nothing has been sent an hour later, one email shows three ways to send your first text, and that takes the place of the tips. If a text of yours fails before any has gone out, one email says why and how to fix it. Replies come straight to me. Every one has a one-click unsubscribe, and under Settings › Emails each kind has its own switch.

## What to do now

Update your phone app so it uses the new wake channel: Android 1.8.1, Sparetext for Mac 1.4.2, or iPhone 1.5.0, which you install from TestFlight. All three are on the [Download page](https://sparetext.dev/download), and every change is listed on [What's new](https://sparetext.dev/changelog). Then send yourself a text from the dashboard and count the seconds.

what's new reliability iphone android mac

Try it with the phone you have

Free for 1 phone and 300 texts a month. Pair it in about two minutes.

[Start free](https://sparetext.dev/signup)

## Responses

[Sign in](https://sparetext.dev/login?next=%2Fblog%2Fwhy-texts-leave-your-phone-in-seconds-again%23responses) or [create an account](https://sparetext.dev/signup?next=%2Fblog%2Fwhy-texts-leave-your-phone-in-seconds-again%23responses) to respond.

## More from the blog

- **[Your first text from code in five minutes, timed against Twilio's steps](https://sparetext.dev/blog/first-text-from-code-in-five-minutes)**
   5 min read
- **[We handed our dashboard to two AI agents: this week in Sparetext](https://sparetext.dev/blog/we-handed-our-dashboard-to-two-ai-agents)**
   5 min read
- **[How to text a big list from your own phone without burning the SIM](https://sparetext.dev/blog/text-a-big-list-from-your-own-phone)**
   5 min read

---

This is the Markdown copy of https://sparetext.dev/blog/why-texts-leave-your-phone-in-seconds-again for AI agents. Every public page has one: add .md to its address (the home page is https://sparetext.dev/index.md). Sparetext for agents in one file: https://sparetext.dev/llms.txt
