Route front-desk messages at a clinic to the right queue
Patient messages to a clinic's front desk are sorted by a decision model into scheduling, billing, records, or clinical question, with clinical and unclear messages always sent straight to staff and never answered automatically.
An example pattern written by Agents Lookup. We have not yet found a public build of this exact job.
The use case
Small clinics receive messages through a portal, email, and web forms, and front-desk staff sort them by hand. Jev reads each message and picks which queue it belongs to from a fixed list, and answers whether it mentions a symptom or a clinical concern. Scheduling, billing, and records messages classified with a confidence of 0.9 or higher go to those queues. Any message that may be clinical, or that Jev is unsure about, goes to the clinical staff queue right away. Jev never gives medical advice, triages symptoms, or decides on care. Staff read every message and respond, and clinicians handle anything clinical. Run it alongside the current manual sort for a few weeks first, and compare the queues before letting it place any messages on its own.
Example workflow
- Patient messages arrive through the clinic's portal, a shared inbox, or a web form.
- Make sends the message text, without attachments, to Jev using an account covered by your data agreements.
- Jev answers a Choice question, which queue does this message belong to, with the allowed answers scheduling, billing or insurance, records request, clinical question, and other, and a Noul question, the message mentions a symptom, medication, or health concern.
- Code sends any message with a likely clinical mention, or below the confidence threshold, to the clinical staff queue.
- Other messages are placed in the matching queue in the practice tool or a shared sheet.
- Staff work each queue and reply to patients, and clinicians handle every clinical message.
Tools
- Jev (TypeSafe AI)
- Make
- Gmail
- Google Sheets
- Slack
- Jotform
Risks and guardrails
- A clinical message sorted as scheduling could delay care — guardrail: any message with a possible clinical mention goes to clinical staff regardless of the queue answer.
- Patients may treat a portal as an emergency channel — guardrail: an auto-reply written by staff tells patients to call emergency services for urgent concerns.
- Health information carries legal duties — guardrail: confirm a data agreement with every tool before sending any patient text, or keep this step off patient data.
Related recipe
Support Ticket and Review Triage with Policy-Cited Draft Replies: An agent tags every helpdesk ticket and public review by intent, urgency, and sentiment, routes it, and drafts a reply that cites your help center. People approve refunds and all public replies.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- Jotform MCP server (official page): www.jotform.com/developers/mcp (checked 2026-11-09)