Calendar and SMS Sequences Built on Consented Push Audiences

We run calendar push for one thing: a reminder somebody asked for, delivered through a webcal subscription they added themselves. A departure, a fare window closing, the last day of a giving campaign. We do not buy calendar injection inventory and will not source it, so if that is what the brief means, this is the wrong desk. The sequence that does work is push notification, then SMS at the decision moment, then a calendar entry for the date, and in Singapore two registries govern the SMS leg before a single message sends. The chain, and why each step is there: The push notification carries the reach and costs the least. It converts poorly on a dated offer because it is dismissed and gone within seconds. The SMS carries the decision moment and requires explicit consent captured on your own page and tied to the click identifier that produced it. The calendar entry survives both: the notification is dismissed, the message is buried, the event sits in the diary until the date arrives and opens the app that shows it. Singapore compliance, which is neither optional nor fast: Since 31 January 2023 sender IDs used for SMS into Singapore must sit in the SMS Sender ID Registry, and unregistered senders are labelled Likely-SCAM by the carriers, which ends the campaign on arrival. Registration takes weeks and belongs to your entity rather than ours. Do Not Call registers under the PDPA are checked before every send and the check receipt retained. Across the region, Vietnam's Decree 91/2020 requires registration and a working opt-out for advertising messages, and Indonesia's 2022 personal data law changes what the consent copy must say. Where this fits: Dated offers only. Airline and ferry departures out of Changi and the regional secondaries, tour departures with a booking cutoff, off-peak tariff windows for energy retailers, giving days where the date is the entire campaign. Nothing in this sequence improves an always-on offer, and the SMS leg on an undated offer is simply an expensive push notification. Refused: Purchased or scraped phone files. Sender IDs resembling a bank, a courier or a government agency. Calendar events created for anyone who did not subscribe to the feed themselves. Grey routes: we send through carrier-approved aggregators only, and the price difference against a grey route is real and is precisely the point. Consent copy written to be read: One field, one checkbox, one sentence naming who will message them, about what, how often, and how to stop. Your counsel reviews it before anything sends. We would rather lose opt-ins than hold consent that would not survive a complaint to the PDPC, because the entity that receives that complaint is yours. Not for: Anyone without a date in the offer. Also not for teams expecting us to send from our own sender ID or our own consent base. No such base exists here and none will, which is the reason to hire us rather than an objection to it. What arrives: The sequence built and running, with drop-off measured at each step rather than end to end. The hosted .ics feed specification and the calendar entry copy. The consent record schema tying each number to the click that produced it and the timestamp it happened. The sender ID registration filed in your name. The Do Not Call check procedure documented so your team runs it correctly after we leave, which is the part that matters in month six.