Background
Bookings were tracked manually in chat messages. Conflicts and missed entries happened weekly; in peak season the front desk spent half the day replying.
Approach
- 1
Abstracted "service – staff – time slot" into configurable resources instead of hard-coded logic
- 2
Defined cancellation and rescheduling rules that automatically release slots
- 3
Subscription-message reminders before arrival to cut no-shows
- 4
Daily and weekly scheduling and revenue exports in the backend
Results
- Booking conflicts reduced to zero
- Front-desk message volume dropped noticeably
- Ops reporting went from manual rollups to automatic tables
Tech Stack
TaroTypeScriptNode.jsPostgreSQLSubscription Messages
