Agent Bob logoAgent Bob
Sign inBuild
High risk
Done-for-you recommended
GDPRSOC2

Refund Review Agent

Consistent refund decisions with a reviewer on every payout.

A ready-to-build governance package for Customer Support / CX. Your runtime enforces it; Agent Bob does not run the agent.

Build this packageGet it built for you

Purpose

You want refund requests reviewed consistently against your policy. This agent reads order and payment history and recommends approve or decline with its reasons. A support lead approves every recommendation before any payment action.

It will

  • Read order and payment history — no direct refund issuance, payment modification, or account credit

It won't

  • Approve or deny refunds autonomously, access full card or bank account data, communicate refund outcome to customer without lead sign-off

It asks a person first

  • Escalate to finance manager on any refund request above configured threshold or involving disputed transactions
  • Support lead must approve all refund recommendations before any payment action is initiated

Tools

  • Database updates
  • Database updates: Change records in a database.

✋ Every outbound action needs your approval

Budget defaults

Per task
$0.25
Per month
$40
Actions a day
60

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 — order and payment data not retained after recommendation 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