Healthcare provider · Implementation in progress
Redesigning patient access with voice and SMS automation
Measured Intuition is redesigning patient-access operations to reduce missed demand, waiting and administrative workload. The rollout started with voice and SMS, with a phased expansion into electronic health record workflows.
Business impact comes first
The operating goals are straightforward: no missed calls, no missed appointments and less dependence on manual front-desk coordination. Voice intake is designed to shorten the wait before intake by 95%. That figure is a rollout target, not a measured production result.
SMS automation reduces the manual work needed to coordinate patient requests. As more of that work moves into software, the provider expects to need less front-desk staffing. Later phases address repetitive back-office record entry and maintenance.
A report the provider did not have
Before selecting the automation, Measured Intuition built a consolidated operational report from phone-system events, conversation records and frontline workflow observations. The provider did not previously have this view.
The report reconstructed where callers waited, where repeated contact occurred and where follow-through remained exposed. It separated three events that are often mistaken for the same result: a call being answered, a request being captured and the requested action actually being completed.
That distinction shaped the implementation. Answering more calls has limited value if the underlying requests disappear into another queue.
Strategic approach
The rollout started with voice and SMS because those channels sit at the point where patient demand enters the business. The design connects intake, request history and staff handoff rather than adding an isolated answering tool.
The next phase extends that continuity into record entry, updates and maintenance in the existing clinical system. The intended operating change is a reduced staffing requirement for routine coordination and back-office data handling, with staff focused on exceptions and patient needs.
Technical implementation
The implementation uses TypeScript and PostgreSQL to preserve request state outside the conversation. Model interpretation is separated from the code that determines which actions are permitted.
- Durable request records carry context into staff handoffs.
- Request-bound permissions and confirmations constrain actions.
- Stale-context checks prevent earlier assumptions from silently authorizing later work.
- Verification exercises interruption, tool failure, replay and recovery.
Clinical judgment stays with people. Caller-declared urgency is captured and routed, rather than treated as an automated medical diagnosis.
What has changed, and what comes next
The custom operating report and voice/SMS implementation establish a clearer connection between incoming demand and the work required to resolve it. Controlled testing and hosted components are in place.
Full caller acceptance, live clinical-system actions and production outcome measurement remain rollout gates. The 95% wait reduction, missed-appointment goal and eventual staffing changes are objectives to verify as deployment expands.
Discuss a workflow worth changing.
Start with the operating constraint, the current process and the business result that would justify changing it.