1. Beneficiary Tracking
  2. Your Beneficiary Tracking Agent
Reference

Put an AI agent to work in Beneficiary Tracking

Use Proto to configure case work and help your team inspect the next application handoff.

Set it up

  1. Teach your agent ERP.AI

    Load the ERP.AI skill and paste the output into your agent. It explains how to read and update records in your workspace.

    curl -fsSL https://www.erp.ai/skill.md
  2. Give it a role

    Assign the agent its own user and one of the 5 roles. It gets exactly the access that role has, and no more.

  3. Check what it can reach

    Confirm which records, actions and connections the agent can use in your workspace before you point it at real data.

  4. Review its work and usage

    Check the drafts and changes it proposes, and watch its usage receipts as you give it more to do. Agent work uses prepaid credits.

What the agent can do

  • Citizen Service Portal Operator: Find my submitted applications and identify the requirement or follow-up action that needs attention before the next handoff.
  • Citizen Service Portal Reviewer: Summarize the evidence and pending decision for this application revision, keeping the decision for my review.
  • Citizen Service Portal Administrator: Compare the pilot service definition with the policy reference and effective dates I provide for setup.
  • Read Only Analyst: Summarize permitted delivery results and overdue follow-up by service and assigned staff member.

What stays with a person

  • An assistant cannot supply the independent human approval for a case it prepares or declare a service delivered without the required outcome.
  • The deciding reviewer remains responsible for the recorded reason.
  • External identity and fulfillment connections need authorized setup, and an uncertain provider response needs investigation before another action is taken.
  • Use an application number when requesting help and review the selected case before changing it.

An assistant cannot supply the independent human approval for a case it prepares or declare a service delivered without the required outcome. The deciding reviewer remains responsible for the recorded reason. External identity and fulfillment connections need authorized setup, and an uncertain provider response needs investigation before another action is taken.

Use an application number when requesting help and review the selected case before changing it. Keep beneficiary information within the team's permitted access scope.

Agent usage follows the platform's metering terms. Review [pricing](/beneficiary-tracking/pricing) when estimating imports, connection activity and workflow usage for the pilot.

Set up Beneficiary Tracking your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started