Front Desk Agent
No missed inquiry, and booking requests waiting for one-click staff confirmation.
A ready-to-build governance package for Dental Practices. Your runtime enforces it; Agent Bob does not run the agent.
Purpose
You want every inquiry answered quickly, even when the front desk is busy. This agent answers questions about hours, services and accepted insurance, and turns booking requests into staged appointments for staff to confirm. It never gives dental advice and sends anyone describing an emergency straight to staff.
It will
- Read practice FAQ and open appointment slots; booking requests staged only — no direct schedule write, no clinical record access
It won't
- Give clinical or dental advice, quote treatment prices not on the published fee schedule, store PHI beyond the session
It asks a person first
- Escalate to front-desk staff immediately if a message describes pain, swelling, bleeding, trauma, or any other emergency symptom
- Front-desk staff must confirm every booking request before it is added to the schedule
Tools
- Send email
- SMS / text messages
- Calendar scheduling
- Send email: Send email on your behalf.
- SMS / text messages: Send text messages to phone numbers.
- Calendar scheduling: Suggest and place calendar holds.
✋ Every outbound action needs your approval
Budget defaults
- Per task
- $0.25
- Per month
- $30
- Actions a day
- 120
The runtime pauses the agent at a limit. You can change every number in the builder.
Memory and autonomy
Session only. Nothing is kept once the session ends.
ClawMaven policy: session-only — inquiry content and patient identity not retained after staff handoff
Acts within limits: low-risk steps on its own, everything gated still stops for a person.
What you get
The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.
HANDOFF.mdWhat your runtime has to enforce, file by fileagent-blueprint.jsonThe agent's purpose, tools and settingspolicy.jsonHard limits: autonomy, budget, memory, tools, loop boundstrust-manifest.jsonThe integrity manifest your runtime can verifyrouting.rules.jsonWhich tools need approval before userun-report-template.jsonWhat every run reports backapproval-gates.mdThe moments that must pause for a persondeployment-checklist.mdWhat to check before it goes live
This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.
Start from this package
Bob pre-fills the builder with it and drafts the rest. You confirm every step.