Scheduled Messaging API: UTC SendAt timestamps ignore local DST transitions

Problem

When using Twilio’s Programmable Messaging API to schedule a message, the SendAt parameter requires an ISO‑8601 UTC timestamp. The API returns all timestamp fields in UTC and does not perform any automatic conversion to a user’s local time zone or account time zone. This can lead to messages being delivered earlier or later than intended during daylight‑saving transitions in the target region.

Unresolved Questions

• Does Twilio plan to expose a time‑zone or local‑time parameter for scheduled messages to simplify local‑time scheduling?
• Will Twilio add automatic daylight‑saving handling for the SendAt value in future releases?
• What is the recommended approach for developers to guarantee delivery at a specific local time when the target region observes DST changes?