Corrections
This corrections log lists every factual change we make to this site, with the date, the page, what it said before, what it says now and the source behind the fix. Typos and layout changes aren't logged. If you spot an error, use the contact link in the footer; we check every report against the original source.
The short answer
This corrections log lists every factual change we make to this site, with the date, the page, what it said before, what it says now, and the source behind the fix. A factual change is anything that changes what a reader would do: a menu path, a number, a rule, a date, or what our app does. Typos, layout and meaning-neutral wording are not logged. Every page also shows a "Last checked" date under its title, and that date moves when the page is re-checked even if nothing changed. The site hasn't launched yet, so the first entries are fixes made during review, before any reader saw the old text. We log them anyway: they show where this topic is easy to get wrong.
How a correction works
- Someone reports a problem, or our own re-check finds one. Re-checks happen when Apple updates a cited support page, when iOS gets a major version, and on preset dates (for example, a rule's effective date).
- We open the original source again. For iPhone facts that means the support.apple.com page; for rules, the FCC or the Federal Register; for SMS counts, the 3GPP standard and our counting script. The source tiers are explained on how we test and source this site.
- We fix every page that carries the fact, not just the one in the report, and change each page's "Last checked" date.
- We add a row below with date, page, old claim, new claim and source.
- We reply to the person who reported it within 7 days, saying what we changed or why we didn't.
We never delete rows; a wrong correction gets its own new row.
Log
| Date | Page | What it said before | What it says now | Source |
|---|---|---|---|---|
| 6 Nov 2026 (pre-launch) | Group chat check | Asked "All iPhone?" and read that answer as "everyone uses iMessage" | Asks "Does everyone on the list use iMessage?"; an iPhone with iMessage off counts as "Not all". Old share links (who=iphone) now mean "everyone uses iMessage" | Apple Support 118236 |
| 6 Nov 2026 (pre-launch) | Home, app page, send reminder, schedule a text, ways to mass text, compare apps, llms.txt | "No iPhone app can send texts by itself" / "iPhone can't send it for you" | What Batchrunner and our tools do: they open Messages and you tap Send. Send Later and Shortcuts automations are covered on their own pages | Apple Developer, MFMessageComposeViewController; Apple Support, Send Later |
| 6 Nov 2026 (pre-launch) | Compare apps, app page | Name merge "also forces one text per person" (stated for all apps); the app page called the name-token rule "this site's" rule | A name token personalizes the greeting; how each app sends is checked separately. The token rule is Batchrunner 2.2's condition; outside Batchrunner, privacy comes from one recipient per conversation | Batchrunner 2.2 behaviour; Apple Support 118236 |
| 4 Nov 2026 (pre-launch) | All pages with an app link; home; message writer | The app's name-token line worded as general advice, without the app's name | A text is private because it goes to one person per conversation. The name token only fills in names. The token-means-own-text rule belongs to the Batchrunner app and is now always stated with its name. Under every Copy button: pasting one text into a message with several people in To still makes a group. | Apple 118236 (group types); how the Batchrunner app opens messages |
| 4 Nov 2026 (pre-launch) | Text many people individually | A table of minutes per method (about 25 seconds per text by hand, 8 with the send list) | Actions per person, counted from the steps. No timing until we measure it on an iOS 26 iPhone. The "Open in Messages" step now says prefilled text isn't yet confirmed on iOS 26. | Our own steps; untested on device |
| 4 Nov 2026 (pre-launch) | Texting consent basics | FCC 26-67: "Not in force yet" | Effective 25 Nov 2026; texts before that date fall under the current rules, texts on or after it under the new opt-out rules | Federal Register doc 2026-21821 |
| 4 Nov 2026 (pre-launch) | Why replies go to everyone | Draft: "Apple removed the Group Messaging switch" (stated as fact) | Apple's current pages no longer describe what the switch does; only Apple's archived 2014 text does, and a 2026 community report says the trick no longer works. Labelled by tier. | Apple 118236; Apple HT202724 (archived 2014); Apple Community report |
Scheduled re-checks
These facts are most likely to change; we re-open the source on these dates whether or not anyone reports a problem.
| Re-check date | Fact | Pages affected | Why that date |
|---|---|---|---|
| 25 Nov 2026 | FCC 26-67 opt-out rules in force | Texting consent basics, appointment reminder text | Effective date in the Federal Register |
| At each major iOS release | Settings paths (Settings > Messages vs Settings > Apps > Messages), Send Later limits, RCS | Every iPhone how-to | Apple moves menus between versions |
| Before launch | Whether sms: links with a message open prefilled on iOS 26; group type for the rows marked untested | Text many people individually, the group-text table | Not yet tested on a device |
| Monthly | Batchrunner price and free-plan limits | App page and every app link | Prices are set in the App Store and can change |
What we won't change on request
We correct facts, not opinions or our recommendations. A request to add an app to our comparison, remove a criterion we use, or soften what Apple's pages say is not a correction. Fixes about the Batchrunner app follow the same rules as everything else: if the app changes how it sends, every page that describes it changes the same day and gets a row here.
Report an error
Use the contact link in the footer. Tell us the page, the sentence, and, if you can, the source that says otherwise. No account or phone number needed. Before reporting, see why replies to your group text go to everyone or text many people individually, which show their sources line by line.
Sources (3)
- Apple Support 118236, Send a group text message on your iPhone or iPad (checked 4 Nov 2026)
- Apple Support HT202724, archived 23 Nov 2014 (checked 3 Nov 2026)
- Federal Register, FCC 26-67 final rule, doc 2026-21821 (checked 4 Nov 2026)