Nobody misses the window.
The window was booked two months ago. The reminder goes out two hours before it, to a phone.
An SMS at N hours before
The problem
A meeting booked two months ago is a meeting people forget.
It is in the calendar, but the owner is in a meeting, and at 2am there is nobody to ask whether it is safe to start. The window burns.
- −60 daysEvent created, invite sent
- −7 daysWindow revised, updated invite sent
- −2 hoursSMS to the system owner
What it looks like
One message
- 01
Configuration
Each update type carries its own message text and its own lead time in hours. The same template variables are available in the message.
- 02
The number
The phone number is taken from Active Directory when the event is created and stored on it, so it cannot change under you between booking and sending.
- 03
Sending
An in-process poller checks each minute which events have entered their lead window and not yet been messaged. No external scheduler is involved.
- 04
Failure
Failures are recorded and counted. There is a retry budget, and then it stops — so a gateway outage cannot turn into thirty messages to the same person.
A corporate SMS gateway, over one HTTP call.
- SMS gateway
- Active Directory
- The event calendar
Show us your worst window.
Bring the one that keeps slipping. Thirty minutes, your estate, no slides.