Repository navigation
SMS reminders for attendees — natively, or via a booking.reminder webhook event #259
dominik-myszkowski
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
First of all - I am very impressed with Calnode - great job!!! I was going to write such thing on my own but then I found it. I will allow myself to suggest a few ideas which would make it even greater, starting with this one. I can contribute to some of them as PR if approved.
The one thing I still miss is SMS reminders to attendees. For phone and video calls, an SMS a few hours before the meeting noticeably reduces no-shows, more so than email, which often goes unread. In our market (Poland), SMS is cheap (under €0.03 per message) and usually sent with an alphanumeric sender ID.
Option A: native SMS reminders. The same hours_before list that event types already use for email reminders (event_type_reminders), with an "also send SMS" toggle and a per-event-type SMS template. To avoid tying Calnode to one vendor, the transport could be a generic HTTP provider: URL, method, headers (API key), and a body template with {{to}}, {{sender}}, {{text}} placeholders. That covers most SMS gateways (Twilio-style and the many regional ones) without per-vendor code.
Option B (smaller, and probably enough for us): a booking.reminder webhook event. It would fire from the existing reminder.send job at each configured hours_before, with the usual booking payload plus hours_before. Any external SMS/WhatsApp/push sender then becomes stateless: receive the event, send the message. It wouldn't have to re-implement scheduling, rescheduling and cancellation, which Calnode already handles correctly for emails. Whether the event fires for an attendee could follow the same notification preferences as reminder emails.
Both options need a reliable attendee phone number, see the related idea about a phone question type (#2 in our list).
Would you accept either of these? We'd be happy to send a PR for option B if the design sounds right to you.
All reactions