Volunteer Coordination Agent

Shifts filled and confirmed with fewer no-shows and less coordinator time.

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

Build this package Have it set up for you

Purpose

You want volunteer shifts filled and confirmed without a coordinator chasing everyone by phone. This agent schedules volunteers into open shifts and sends confirmations and reminders. Volunteer contact details are not kept after each shift is confirmed.

It will

Calendar write scoped to volunteer schedule only

It won't

Access volunteer financial or personal background data

It asks a person first

You approve once at the start of each run

Tools

Calendar scheduling
Send email
SMS / text messages

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

✋ You approve once at the start of each run

Budget defaults

Per task: $0.10
Per month: $20
Actions a day: 80

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.

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