Sarah
AI Front Desk Receptionist · Front desk
Answers every call, message and visitor request, 24/7, no hold music.
What Sarah owns
- Every call answered: day, night, weekend, holiday. No hold music.
- Messages and requests routed to the right desk with full context.
- Visitors pre-registered and expected before they arrive.
- A daily digest so staff start the shift already caught up.
What stays human
- The conversation that needs a person: Sarah hands off warm, with context.
- The face at the door: your team greets everyone who walks in.
- Anything clinical: routed to staff immediately, never answered by AI.
The work
Sarah at work.
Sarah
AI Front Desk Receptionist
Take over the front desk line for the weekend.
- Every call answered, all weekend
- Requests routed with full context
- Monday digest ready
Stays human: the conversation a family needs a person for, Sarah hands off warm.
Live · Sarah
Sarah is on the desk. Ring her.
Sarah, answering out loud, over the same telephone-quality audio a caller on a real phone hears. Ask for one of her colleagues by name and listen to what she does when they cannot pick up: the handling is the job, and it is the only part a page cannot show you.
In the record
What Sarah works in.
These are the screens Sarah works in: the same ones your staff open, under the same roles and the same audit trail. Everything below is in the product today. The entries carrying a second paragraph are where this goes deeper than a feature list; the rest is table stakes, and named as much.
Care and the chart
Appointments and Transport
Fourteen appointment types per resident, and the facility-wide ride board behind them.
Communications
AI front desk
She answers the phone, screens the caller, transfers or takes a message, and files it.
One text inbox
Candidates, staff and front-desk callers on the same number, in one thread list.
Which link a message carries is how the inbox knows what a thread is, and the database enforces that a message has exactly one other end. Threads are labeled rather than split, because a split inbox routes on the same guess and hides whatever it got wrong, and someone who applied and then phoned is still the hiring team's to answer. Delivery reports are recorded, so a text that failed is known rather than assumed. A number that cannot receive texts is learned from the carrier's own rejection codes and the Send button withholds itself. Replying from a community's line is reply-only; cold-texting an arbitrary number stays an administrator's power.
A fax number per building
The fax line is part of the record, not a machine in the corner.
Numbers belong to a facility or are shared across the organization, each with its own inbound notification group and optionally its own provider credentials. Inbound faxes route by the number that was dialed, are stored in object storage rather than the database, and notify by email with the PDF attached. Every send produces a transmission report. Several PDFs merge in order behind a generated or uploaded cover sheet.
Fax and email straight from the chart
Send the MAR, the referral or the packet without printing it.
The chart catalogues what is sendable, face sheet, admission and therapy packets, consents, referrals, evaluations and recertifications, care plans, the physician plan of care and the month-to-date MAR, and a signed-upload kind is offered only once the signed copy exists. Email sends the same documents as individual attachments to a handful of recipients.
Push to chart
An inbound fax becomes a filed note on the resident or the lead.
The fax and its transmission report attach to a note carrying a footer that says where it came from, the file is referenced rather than copied, and a medication order can be raised from the same dialog, so a returned physician order closes the item it belongs to instead of landing loose in Documents.
The Directory
One address book of everyone a community writes to.
It copies nothing: it is a view over providers, pharmacies, institutions, saved contacts, and residents' family, POA and emergency contacts, with lead contacts when the plan includes CRM. Rows sharing a normalized number or an email merge into one entry carrying every source, and the directory record's name wins over a saved copy of it. Each entry shows when it was last faxed, or says plainly that it never was. Sends to a number nobody owns collect in an unfiled queue, one row per number, each with a File action that creates the record where it belongs, or a way to say it is not a contact at all.
Shift Handoff Board
A wall tablet at the nurses' station that is not anybody's login.
The tablet holds a revocable device token that can read one facility's board and nothing else. Every action additionally needs an actor pass minted from a six-digit quick code, so a change always carries a person's name; a missing pass is the signal the tablet turns into its PIN pad. Shift change is a recorded two-code ceremony with a snapshot of what was open at the time. Tiles are calls needing attention, texts awaiting a reply and manual handoff tickets, ageing live, with one claim per tile and re-claiming handing it over.
@Mentions
Name a colleague in a note, a task comment or a move-in step, and grade how much it matters.
On the record
Every interaction Sarah handles (caller, question, request, routing) is logged to the record, so a family never has to repeat themselves and staff never wonder what was said.