Why did my Postscript texts arrive later than I scheduled?
The Postscript help pages give 3 common reasons. The first to rule out: Sending many messages in a short time can overflow your message queue, so texts can take longer to go out.
Is it broken, or just quiet?
A number can fall because fewer people came, or because something stopped counting them. Below are the causes the Postscript help pages give, and how to check each one yourself.
What causes it?
Sending many messages in a short time can overflow your message queue, so texts can take longer to go out.
In the Postscript help:
When shops send a large number of messages in a short period of time, it can cause their message queue to overflow.
Guide to Message Deliverability and Throughput, read 2026-11-12.At peak sending times the routes to phones are busier, so messages can take longer to arrive.
In the Postscript help:
When you send during peak sending times, the roadways are smaller and heavily trafficked.
Guide to Message Deliverability and Throughput, read 2026-11-12.If a scheduled campaign is set to send in each subscriber's time zone, it stays in progress until every time zone has been sent, so sends can spread across the day.
In the Postscript help:
Campaigns will remain in progress until messages are sent to all cohorts across different time zones.
Message Scheduling in Campaign Flows, read 2026-11-12.
How do I check it myself?
If the campaign sends by subscriber time zone, check the launch time shown for each time zone segment.
In the Postscript help:
The launch time and date for each time zone segment are displayed.
Message Scheduling in Campaign Flows, read 2026-11-12.For campaigns, look at the send-times view, which groups messages by the day and hour they were received, to see when the texts actually landed.
In the Postscript help:
Each cell shows how your campaigns performed for messages received in that day/hour slot.
Guide to Campaign Send Times, read 2026-11-12.
How does Postscript work with Feder?
- Connect Postscript to Feder and it joins your Reach apps.
- When you connect Postscript, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.
Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.
See whether you can trust the numbers in Postscript, one of your Reach apps. Feder only reads. It never changes anything in Postscript.
What else goes wrong with these numbers?
- Why did fewer subscribers get my Postscript campaign than are on my list?Postscript
- Why did my subscriber count drop in Postscript?Postscript
- Why did Google Analytics stop collecting data?Google Analytics
- Why aren't my key events showing in Google Analytics?Google Analytics
- Why does Google Analytics show (not set)?Google Analytics
See every question.
Where do these answers come from?
Every cause and check on this page comes from the Postscript help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.