The message finds the role, not the inbox.
Secure messaging between clinicians, coordinators, administrators and facilities. In-app notifications routed to the role that must act. Shift-aware support that already knows which shift and which facility it is about. And a communication history that does not vanish when the shift changes.
Every message is attached to something.
A shift changes at 05:40 and somebody has to be told — not everybody, and not an inbox: the role that must act. Below, one shift event and the thread it carries. Every message is routed by role, every answer is kept with the shift, and the whole conversation is still there for whoever opens the record next.
A message with no context is another thing to chase.
CareTech puts messaging where the work is: secure messaging between clinicians, coordinators, administrators and facilities, and in-app notifications routed to the role that must act.
Routing is the point. A notification does not go to everyone who might care about a shift; it goes to the role that has to do something about it, because roles are enforced at the boundary rather than suggested in the interface. A scheduler cannot request a shift on a worker's behalf, and a worker cannot confirm their own request, so a message asking for either reaches the person who actually holds that power.
Onboarding support channels, real-time updates and a communication history that does not vanish. What was said about a shift is still attached to that shift when the next coordinator opens it, months later, and asks why the second nurse was sent.
A ticket that already knows which shift.
CareTech gives a working clinician shift-aware support: a ticket that already knows which shift and which facility it is about, escalation to the person who can resolve it, mobile access, and a history the next coordinator can read.
Raise, attach context, route, escalate, resolve, keep the history. Context is not typed in by a person who is already late; it comes with the ticket, because the ticket was raised from the shift.
Three screens a clinician actually opens.
It is 06:40 and you are in the car park. You have worked this ward before, but not this entrance, and the badge you were handed last week may or may not open it. Somebody knows the answer. You do not know which somebody, and the number you were given rings a desk that opens at nine. Your shift starts in twenty minutes.
The requirement list, live readiness status, the specific gap and the route to close it. The one thing a professional actually wants to know, answered without a phone call.
Booked schedule management, calendar visibility, shift reminders and mobile scheduling workflows: the confirmed assignment in one place rather than four.
Onboarding status a person can read at any point: what is done, what is outstanding, and who is holding it.
Communication is the connective tissue, not a product on its own.
It runs against the workflows either side of it, in the settings where a shift is worked by somebody who was not there yesterday.
Shift & Schedule Management
The shift is what a message is about. Discovery by role and readiness, approval-led confirmation, calendar visibility, and double-bookings refused at the gate.
02Clinician Workforce Enablement
Onboarding support channels are where most of the early conversation happens: guided onboarding, document upload, credential tracking and a readiness status a clinician can read.
03Payout & Account Visibility
Most support tickets that are not about a door are about a timecard. The support history and the timecard exception route to the same place.
04Every setting CareTech is built for
Hospitals, clinics, home care, schools, behavioral health, rehabilitation, post-acute, senior living, correctional healthcare, diagnostic centers and longevity programs.
Five decisions that make a message findable in March.
Communication software is easy to demonstrate and hard to keep. These are the engineering choices that decide whether a conversation is still useful after the people in it have moved on.
Delivered to the role
Notifications are delivered in the app, to the role that must act, not broadcast to everyone attached to a facility.
Roles enforced at the boundary
A scheduler cannot request on a worker's behalf; a worker cannot confirm their own request; a scheduler cannot approve a timecard.
History attached to the context
History is attached to the thing it is about (a shift, a request, a facility), so it survives the shift change and the staff change.
Tenant isolation in the database
Tenant isolation is enforced in PostgreSQL row-level security, set per transaction so it dies with the transaction and cannot leak across a pooled connection.
Escalation reaches a person who can resolve it, and who escalated what, to whom, and when is recorded alongside the resolution.
How the governance chain works →What coordinators ask first.
Five questions that decide whether a communication layer holds an operation together or just adds a second inbox to it.