- Trigger / problem
- A new owner-office message arrives or an existing thread crosses an agreed deadline without a recorded disposition.
- What it reads
- The message, thread history, sender address, attachments where approved, deadline language, the practice's contact map, decision-rights map, and Workstation routing rules.
- What it decides
- Which approved queue the item fits, whether the sender and request match known routing rules, which Workstation appears to own the operating issue, and whether the item needs the owner's review. Unverified identities and uncertain requests always go to a person.
- What it does
- Labels and groups the item, prepares a concise decision packet with source links and deadline, proposes a routing task, and places any reply in a review queue. It does not send or commit on its own.
- Human approval / takeover
- The owner or designated leader approves decisions, external messages, commitments, payments, staffing actions, and changes in priority. Suspicious or unverified instructions are isolated and surfaced without being followed.
- Systems needed
- Approved mailbox access, contact and permissions records, a task or review queue, document access for permitted attachments, and a Workstation ownership map.
- Privacy / access
- Inbox access is limited to the accounts and folders approved for this workflow. Employee, legal, financial, and patient information keeps its source restrictions. The system retrieves only the context needed for the item.
- Logging & failure handling
- Every classification, source, draft, routing proposal, approval, and send outcome is logged. Unknown senders, conflicting instructions, unsafe attachments, and uncertain ownership route to manual review.
- Success metric
- Age of decision items, share routed correctly on first review, owner review time, reopened items, and operating exceptions returned to the correct Workstation.
- What the practice owns at handoff
- The routing taxonomy, decision-packet template, contact and ownership maps, configured inbox rules, review workflow, security controls, logs, and operating guide.
- Good fit when
- A meaningful share of the owner's inbox is repeatable coordination and routing, while the owner still wants control of decisions and messages.
- Not a fit when
- The owner wants an autonomous sender or has not defined delegation and decision rights. We organize the queue first and keep representation behind review.