Front desk appointment confirmation board for the next 3 days

Build me a confirmation desk app that my front desk opens first thing every morning to work the next three days of appointments. The whole point is that one person can clear the confirmation status of every upcoming booking in a few minutes instead of reading message threads one by one.

The main surface is a board of upcoming bookings. Pull events with Google Calendar List Events across the calendars I select, over a window that defaults to the next three days, sorted by start time. Show one row per appointment with the client name, the appointment time, the service (parsed from the event title or description), and a big confirmation status badge that reads Confirmed, No reply yet, Reschedule requested, or Cancelled. Use Google Calendar List Calendars to populate a calendar picker in settings so I can choose which calendars feed the board.

Calendar invites carry email addresses rather than phone numbers, so client phone numbers come from a Google Sheets client roster. Read it with Google Sheets Get Values and match the attendee email from the calendar event to the roster row to get the number. LoopMessage requires the contact to be either an iMessage email or a phone number in +E.164 international format, so normalize roster numbers to E.164 before sending, and on any row where the lookup fails show an explicit no number on file state with the attendee email offered as a fallback contact rather than silently skipping the row.

Every row has two actions: Send confirmation and Nudge. Both fire a templated text through LoopMessage Send Message. Before any send, call LoopMessage Check Contact Status and refuse to send to a contact who is unsubscribed, showing an opted out badge on the row instead. This guard applies to the manual buttons and to anything the background agent sends. Store the returned message id on the row and show the delivery state from LoopMessage Get Message Status, so staff can tell a failed send apart from a client who simply has not replied yet. Those two states must look clearly different on the row.

The piece that makes this worth opening daily is a read the replies background agent that I kick off from a button at the top of the board. It walks every appointment in the window, pulls that client's thread with LoopMessage Get Message History for Contact, interprets the latest inbound reply in plain language, and writes back a status plus a one line summary onto the row. "yeah see you then" should land as Confirmed, "can we do 4 instead" as Reschedule requested, "sorry have to cancel" as Cancelled, and no inbound reply stays No reply yet. Show progress while it runs and let staff keep using the board. If the agent sends anything in a batch, respect the LoopMessage throttle of at least two minutes between outbound messages to the same contact.

For reschedule requests the agent goes one step further: it looks across the selected calendars for open slots near the time the client asked about, and drafts a suggested reply offering two or three of them. The draft lands on the row in an editable text box. Staff edit it and hit send, which goes out through LoopMessage Send Message. The agent never sends a reschedule reply on its own.

Anything still unconfirmed inside 24 hours of its start time gets pinned to a red call list section at the top of the board. That section is the morning phone call queue, so it should be the first thing visible when the app opens, with a count in the heading.

Persist confirmation status, the one line summary, the last message id, and the last send time per calendar event id in the app's own storage, so state survives reloads and every staff member sees the same board. Also mirror the status and summary back to a Confirmations tab in the roster spreadsheet using Google Sheets Update Values, keyed on the calendar event id, so there is a record outside the app.

Settings I want to control: which calendars feed the board, how many days ahead it looks (default three), how many hours before an appointment the first confirmation goes out, and the wording of the confirmation and nudge templates with placeholders for client name, appointment time, and service. Default the reminder cadence to 72, 48, and 24 hours before the appointment, since that is the pattern that works for confirmation programs, and make the first confirmation hour setting easy to find because I will tune it.