SMS

When is the best time to send an SMS?

Send within the destination's permitted window in the recipient's local time, then choose an hour using your own response data.

Apply the timing rule that covers your message and recipient. Check whether it restricts initiating contact or delivery. A sending timestamp and a delivery report describe different events.

Inside the window, no published hour transfers. An hour measured on one list, in one country, for one kind of message describes that list.

When am I allowed to send?

Inside the window the destination sets, measured in the recipient's local time.

Some destinations restrict the hours for covered promotional messages. Use the clock and event named by the applicable rule. One instant can fall inside the permitted window for one recipient and outside it for another. What are SMS quiet hours covers those windows and the scheduling work your integration must perform. SMS destinations publishes country requirements with the date of the source snapshot.

In the United States the window comes from the FCC's rule under the TCPA, and the operative part is the local-time clause. What is the TCPA quotes it.

Is there a best hour inside that window?

Not one that transfers between audiences.

A recommended hour is measured on one audience, in one country, for one kind of message, against one response. Change any of those and the number describes something else.

  • Audiences are distributed differently. A commuter list and a shift-worker list have different good hours, and an aggregate over both has neither.
  • Content changes the hour. A reminder is timed to the event it references. A promotion is timed to when someone will read an offer.

The method below finds the hour for your own audience from data you already collect.

Why is 9am not a send time?

A schedule fires at an instant, and 9am is a different instant in every time zone.

Your own scheduler holds the timer. Bird's SMS API has no send-later field in service: scheduled_at on the send request is reserved, so supplying it is refused with a 422. A campaign meant for 9am across twelve zones is twelve calls at twelve instants.

The input to that arithmetic decides whether it works. A time zone from a person's profile or account settings is a fact. One inferred from a number's prefix is a guess, and the failure is a message at four in the morning. What is SMS scheduling covers why a number is weak evidence of where its owner stands.

Does the send arrive when it starts?

No. It arrives over the time the send takes to clear.

Your schedule decides when a send begins. Queueing, capacity, network conditions and recipient availability determine the subsequent outcomes. A forty-minute submission window does not establish a forty-minute delivery window. What is SMS throughput covers the ceilings that set that duration.

Two consequences. Start early enough that the whole send lands inside the window you intended. And where a message must be read before a deadline, work backwards through the clearing time.

How do I find the best time for my own audience?

Measure arrival separately from response. They fail differently.

  • Arrival comes from the delivery receipt, which carries the moment the network reported delivery. Comparing accepted time with delivered time across a send shows how much the network moved your timing. What is a delivery receipt covers what that event does and does not tell you.
  • Response comes from your own funnel: replies, visits, redemptions. What is click-through rate covers the measure and its traps.

Split one campaign rather than comparing two. Send the same content to comparable halves of one audience at two local hours, and compare the response rather than the delivery rate. Two campaigns a week apart differ in content, list state and season as well as in hour.

Re-run it periodically. An audience's best hour moves as the audience does.

Which sending time should I choose?

  1. For a message with a restricted sending window, choose a permitted hour in the recipient’s local time.
  2. For an event reminder, work back from the event and allow time for processing and delivery.
  3. For a promotion, compare two permitted local hours using comparable groups in the same campaign.
  4. Keep the better response time for that audience. Repeat the comparison as the audience changes.

In short

  1. The destination sets a window before preference enters it.

    Where a destination restricts promotional messaging to certain hours, that window decides when you may send, in the recipient's local time.

  2. A published best hour describes another audience.

    An hour measured on one list, in one country, for one kind of message, carries no claim about yours.

  3. A local hour is not a send time.

    A schedule fires at an instant, and an hour in a recipient's day is a different instant in every time zone, so a local-hour campaign is one send per zone.

  4. A large send arrives over a period, not at an instant.

    Processing and delivery take time. Individual recipients can have different outcomes and delays.

  5. Your delivery receipts and your funnel answer the question.

    Receipts describe network-reported delivery outcomes. Your funnel records responses, so evaluate the two separately.

Build on the same network.

A test API key is yours immediately. Production unlocks when you add a payment method and verify a sender.

Your next idea.
Ready to connect.