In practice · Healthcare

The front desk that remembers

An example of what is possible. The same four steps apply wherever work moves between people and systems, and each time round, the operation knows a little more than it did.

The problem

Every day the same phone: reschedules, exam requests, a prescription that ran out, the doctor interrupted between patients to sign something. What the receptionist knows (who only comes in the morning, who needs the prescription sent to the pharmacy near work, who always forgets to fast) lives in her head, and leaves with her at six.

With Uffici

One agent runs the front desk from the first call to the follow-up; the doctor only sees what needs a signature, never the phone. Every preference is kept from the moment it’s said, every exam is filed with the reason the doctor gave, and the next visit starts from everything the last one learned. By the third visit the patient is greeted like a regular.

SYSTEMSAGENTSTHE PERSONTHE RECORD01 · THE CALLA patient gets in touch02 · THE BOOKINGA slot that fits03 · THE VISITThe doctor’s ten minutes04 · AFTEREverything sentWhatsAppPhoneEmailSMSCalendarPatient fileWaitlistPatient filePrescriptionPharmacyLabSMSWhatsAppThe agentPicks up, voice or text:who it is, what’s pending,what they preferThe agentBooks the slot that fits:morning only, same doctor,before the exam expires.Sends the prep; refills acancellation from thewaitlistThe agentSends the prescription tothe patient and thepharmacy, the request tothe lab; routes theresults back to thedoctor; books the returnThe doctorExamines, decides, signs,with the history and thepending exams already onthe screenTHE SIGNATURE, NOT THE PAPERWORKEvery contact kept, withwhat the patient askedforEvery preference keptfrom the moment it wassaidEvery exam ordered withthe reason the doctorgaveEvery prescriptiontraced: sent, received,filled · retained,auditable, the clinic’sEverything the patient says this visit is what the front desk knows on the next call
A patient who only comes in the morning →never offered an afternoon again
Third visit in →greeted like a regular, nothing asked twice

What every loop runs on

Agent

One agent, in context

It knows the company and the job in front of it, and remembers what it learned.

Connections

A curated catalog

The systems the operation already runs on, through connectors we build and maintain.

Surfaces

Board, tables, files

Where the work becomes visible, structured and stored.

Record

The history

Every action the agents took, kept apart from the operational database.

Ground

The foundations

Isolation, secrets and metering, per organization.

Nobody has to learn a second system, and nobody has to learn our words for things: the agent says quote, invoice, work order or candidate, whatever the people doing the job already say.

This is one. The next is yours.

A rental yard, a law firm’s intake, a dispatch board, an accountant’s month-end. If it runs on people handing each other work, it runs on Uffici.