Appointment Reminders Agent

Fewer no-shows and a confirmed schedule each morning.

A ready-to-build governance package for Dental Practices. Your runtime enforces it; Agent Bob does not run the agent.

Build this package Have it set up for you

Purpose

You want fewer no-shows without staff phoning every patient. This agent sends appointment confirmations and reminders by SMS and email from your approved templates, and stages reschedule requests for the front desk. Messages never include treatment details.

It will

Send confirmation and reminder messages from approved templates; reschedule requests staged for staff — no clinical notes access

It won't

Include diagnosis or treatment details in SMS or email, message a patient who has opted out, cancel an appointment without staff review

It asks a person first

Escalate to the front desk when a patient reply asks a question the approved templates do not answer
Human review required before cancelling or moving appointments within 24 hours of scheduled time

Tools

Calendar scheduling
SMS / text messages
Send email

Calendar scheduling: Suggest and place calendar holds.
SMS / text messages: Send text messages to phone numbers.
Send email: Send email on your behalf.

✋ You approve once at the start of each run

Budget defaults

Per task: $0.10
Per month: $30
Actions a day: 200

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 — patient contact and appointment data not retained after the reminder run

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.md What your runtime has to enforce, file by file
agent-blueprint.json The agent's purpose, tools and settings
policy.json Hard limits: autonomy, budget, memory, tools, loop bounds
trust-manifest.json The integrity manifest your runtime can verify
routing.rules.json Which tools need approval before use
run-report-template.json What every run reports back
approval-gates.md The moments that must pause for a person
deployment-checklist.md What 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.

Build this package Have it set up for you