The latest articles on DEV Community by Luis Montoya Martinez (@luis-montoya). https://dev.to/luis-montoya https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4112960%2Fe3a63612-9a39-444d-af66-f2ed364e89c4.png https://dev.to/luis-montoya en Luis Montoya Martinez Mon, 07 Sep 2026 01:50:27 +0000 https://dev.to/luis-montoya/designing-reliable-appointment-confirmations-with-google-calendar-and-whatsapp-24fg https://dev.to/luis-montoya/designing-reliable-appointment-confirmations-with-google-calendar-and-whatsapp-24fg <p>Many appointment systems solve only the calendar event. Reliability depends on the handoff between the calendar, the messaging provider, and the person who booked the appointment.</p> <h2> A practical architecture </h2> <ol> <li><p><strong>Use the calendar as the source of truth.</strong> Read availability from the calendar and write the appointment there first. Do not let a message thread become a second, conflicting schedule.</p></li> <li><p><strong>Give every appointment an idempotency key.</strong> A webhook can be retried, a provider can time out, and a user can click twice. Store a stable appointment ID and make confirmation, rescheduling, and cancellation safe to repeat.</p></li> <li><p><strong>Separate event state from message state.</strong> An appointment can be confirmed while its reminder is queued, delivered, or failed. Keeping those states separate makes support and retries much easier.</p></li> <li><p><strong>Make time zones explicit.</strong> Store timestamps in a consistent format, keep the business time zone in the appointment context, and render the final message in the customers time zone. Daylight-saving changes are a common source of avoidable mistakes.</p></li> <li><p><strong>Design for opt-in and templates.</strong> WhatsApp Business messaging has policy and template requirements. Capture consent, use an approved template when a conversation is outside the service window, and provide a clear way for a person to stop receiving messages.</p></li> </ol> <h2> What to measure </h2> <p>A useful minimum dashboard includes confirmation rate, delivery rate, response time, rescheduling rate, cancellation rate, and no-show rate. Track failures by cause: invalid number, provider rejection, expired token, calendar conflict, or an internal retry limit. A single success metric hides where the workflow is actually breaking.</p> <h2> A simple failure policy </h2> <p>Retry transient provider and network errors with backoff. Do not retry permanent errors such as an invalid recipient or a rejected template. If a reminder cannot be delivered, surface the problem to the team and keep the appointment visible in the calendar. Silent failure is worse than a manual follow-up.</p> <p>The goal is not to send more messages. It is to keep the calendar, customer, and team aligned with the fewest ambiguous states possible.</p> <p>Teams that prefer a ready-made workflow can use <a href="https://confirmatodo.com/" rel="noopener noreferrer">Confirmatodo</a> to connect Google Calendar with WhatsApp confirmations and reminders.</p> architecture backend systemdesign