High risk
Done-for-you recommended
HIPAA

Review Responder Agent

Every review answered within a day, with no patient details disclosed.

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

Purpose

You want every Google review answered professionally without risking a privacy slip. This agent drafts replies that never confirm someone is a patient, never mention treatment and never admit fault. A practice manager approves each reply, and complaints go to a person.

It will

  • Read public reviews; draft replies only — no posting without approval, no access to patient records

It won't

  • Confirm or deny that a reviewer is a patient, reference any treatment or visit detail, admit fault or liability, offer refunds or compensation

It asks a person first

  • Escalate to the practice manager on any review alleging injury, malpractice, a billing dispute, or a privacy complaint
  • Practice manager must approve every reply before it is posted

Tools

  • Web research
  • Browser automation
  • Web research: Look things up online.
  • Browser automation: Click through websites like a human.

✋ Every outbound action needs your approval

Budget defaults

Per task
$0.25
Per month
$20
Actions a day
20

The runtime pauses the agent at a limit. You can change every number in the builder.

Memory and autonomy

No memory. Nothing is kept between runs.

ClawMaven policy: zero retention — review text and draft replies not stored after approval handoff

Supervised: it prepares the work and a person approves it.

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 packageGet it built for you