Communication layer created after documentation workflows were operating.
Stage 02 / Communication Layer
Skmsg
Messaging automation built after operating SkincareChart revealed appointment communication and follow-up bottlenecks.
Real use showed scheduling and communication stayed disconnected.
A controlled communication automation layer.
Staff needed faster operational access.
Problem
Operating the documentation workflow showed that appointment communication remained separate from scheduling and staff operations.
Solution
I connected appointment data, approved templates, inbound replies, and staff confirmation workflows into a controlled messaging layer.
My Role
Workflow analyst, backend developer, integration builder, deployment operator, and iteration lead.
Key Features
- Twilio SMS/MMS sending and incoming webhook handling
- Google Calendar appointment integration
- Reminder, confirmation, cancellation, and rescheduling templates
- Contact synchronization and selected Telegram confirmation flows
Development Log
Message templates and SMS workflow support were added to make recurring patient communication more consistent.
View development logScreenshots
Public screenshots are limited to sanitized portfolio visuals without patient data or private clinic information.
Technology Used
Python, Flask, SQLAlchemy, SQLite, PostgreSQL, Railway, Twilio API, Google Calendar API, Telegram Bot API, Cloudflare/DNS.
What I Learned
Healthcare automation needs guardrails, confirmation steps, deployment discipline, templates, logging, and failure handling.