Staff operations layer created after charting and messaging were operating.
Stage 03 / Staff Operations Layer
Telegram CRM Bridge
Staff-facing operations layer built after operating charting and messaging tools revealed faster lookup and controlled action needs.
Operating both systems exposed staff workflow limits.
A Telegram-based staff operations layer.
Continue toward one integrated workflow platform.
Problem
Staff needed faster operational lookup and approved communication actions without unsafe free-form write access.
Solution
I separated lookup actions from write actions and added approved templates, confirmation gates, audit behavior, feature flags, and reversible rollout controls.
My Role
Workflow analyst, TypeScript developer, safety-control designer, rollout planner, and operations-focused builder.
Key Features
- Telegram Bot API webhook service
- Customer and booking lookup
- Approved template message preview and send flow
- Confirmation gates, audit logging, feature flags, and legacy command compatibility
Development Log
Operational notifications and internal workflow automation were added to reduce manual checking and improve awareness.
View development logScreenshots
Public screenshots are limited to sanitized portfolio visuals without patient data or private clinic information.
Technology Used
Node.js, TypeScript, Telegram Bot API, HTTP webhook service, feature flags, JSON action schemas, allowlisted actions, automated tests, Mac mini LaunchAgent.
What I Learned
Operational interfaces need clear boundaries, predictable interaction patterns, fallback paths, and rollout controls.