It's possible to schedule campaigns using a TZ (for example "Hobart GMT+10"), however Hobart has Daylight Savings (DST) during summer. In this case the TZ for Hobart is actually GMT+11.

I had a situation recently where I was "in GMT+10", but scheduling a message after the rollover to DST, and I wasn't clear when the message would actually be delivered.

Can the wording / communication on the user interface be improved, to clarify when the message will actually be sent? (hopefully this would be simple).

Ideally the system would become more DST aware, so that if you schedule a meeting using any arbitrary TZ, you can then see what "local time" it will be delivered to a user.