VoiceDesk

Partly built — inside Phone Calls, and honest about the half that cannot run. THIS IS NOT A SEPARATE APP. The phone line, its webhook credential, the call log and the missed-call handover are Phone Calls (CallDesk), and the answering rules were built there rather than beside them. What is there: an answering policy per line, a bounded list of what the assistant may answer, a rehearsal so staff can try a sentence against the rules, and a transcript of every exchange. What is not: answering by telephone. A line can carry a calling account, entered under Phone Calls → Phone lines, that places reminder calls and records how each one ended, but nothing picks up an incoming call, so the assistant cannot be switched on at all — the switch refuses, and says why. Find it under Phone Calls → Answering assistant.

VoiceDesk reads the hospital’s own opening hours and address, the answering rules and writes answering policies, rehearsals and their transcripts, handovers. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.

It answers two things — when the hospital is open and where it is — and hands over everything else, including every appointment and every report enquiry: those need to know who is calling, and a phone number is not an identification. It is a keyword matcher and not a model, English-only, so any other language hands over too. It always says it is automated: the column that would let it not is refused by the database. And nothing answers your telephone — a line’s calling account places calls but does not pick them up — which the screen states rather than implying with a switch.

Every record stays; only the workflow leaves.

VoiceDesk is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.