Review and referral requests fail when timing, customer satisfaction, ownership, and attribution are left to memory. The fix is not more messages or more dashboards. The fix is one controlled workflow with a clear owner at every handoff.
This guide breaks the Review and Referral Operating System into 24 agents. Four agents control the system. Five departments do the work. The labels are roles, not a recommendation to buy 24 separate tools. One workflow can perform several roles when the boundaries are clear.
What the control layer does
The control layer keeps the workflow safe and readable. The orchestrator moves work between steps. The context librarian holds the trusted record. The human approval gate stops claims, consent decisions, budget changes, and judgment calls. The audit agent records what happened and why.
A useful rule is simple: an AI agent may prepare a decision, but it should not approve its own risky action.
1. Success Signal
The goal is simple: confirm the work is really complete. This step should produce a visible record that the next owner can verify.
- Job Watcher: Handles one clear part of the handoff with Hubspot in the visible tool stack.
- Payment Matcher: Handles one clear part of the handoff with Stripe in the visible tool stack.
- Outcome Checker: Handles one clear part of the handoff with C2C in the visible tool stack.
- Issue Checker: Handles one clear part of the handoff with Gmail in the visible tool stack.
Do not move forward when the required identity, permission, owner, or source record is missing. Route the exception to a person instead.
2. Eligibility
The goal is simple: ask the right customer at the right time. This step should produce a visible record that the next owner can verify.
- Satisfaction Scorer: Handles one clear part of the handoff with Anthropic in the visible tool stack.
- Timing Checker: Handles one clear part of the handoff with N8N in the visible tool stack.
- Suppression Checker: Handles one clear part of the handoff with Postgresql in the visible tool stack.
- Human Gate: Handles one clear part of the handoff with Slack in the visible tool stack.
Do not move forward when the required identity, permission, owner, or source record is missing. Route the exception to a person instead.
3. Review Loop
The goal is simple: make the review request simple. This step should produce a visible record that the next owner can verify.
- Request Drafter: Handles one clear part of the handoff with Openai in the visible tool stack.
- Sms Sender: Handles one clear part of the handoff with Twilio in the visible tool stack.
- Email Sender: Handles one clear part of the handoff with Gmail in the visible tool stack.
- Review Logger: Handles one clear part of the handoff with Googleanalytics in the visible tool stack.
Do not move forward when the required identity, permission, owner, or source record is missing. Route the exception to a person instead.
4. Referral Loop
The goal is simple: capture context before the handoff. This step should produce a visible record that the next owner can verify.
- Referral Form: Handles one clear part of the handoff with Typeform in the visible tool stack.
- Identity Matcher: Handles one clear part of the handoff with Supabase in the visible tool stack.
- Owner Router: Handles one clear part of the handoff with Hubspot in the visible tool stack.
- Intro Copilot: Handles one clear part of the handoff with C2C in the visible tool stack.
Do not move forward when the required identity, permission, owner, or source record is missing. Route the exception to a person instead.
5. Revenue Match
The goal is simple: connect the referral to cash. This step should produce a visible record that the next owner can verify.
- Booking Matcher: Handles one clear part of the handoff with Calendly in the visible tool stack.
- Source Stamper: Handles one clear part of the handoff with Googleanalytics in the visible tool stack.
- Cash Matcher: Handles one clear part of the handoff with Stripe in the visible tool stack.
- Program Report: Handles one clear part of the handoff with Slack in the visible tool stack.
Do not move forward when the required identity, permission, owner, or source record is missing. Route the exception to a person instead.
Build order
- Pick one real record and trace it from the first source event to the final outcome.
- Define the trusted identifier, consent state, owner, next action, and service level.
- Add one assisted action that a person can review.
- Write a receipt after every handoff. A receipt can be a CRM event, task, booking, call, or payment match.
- Test a missing-data path and a provider-failure path before sending anything to a real lead or customer.
- Measure the outcome that matters. Do not treat a sent message or API success as a booked call, sale, or retained customer.
Use the map as an audit
Take one recent successful record and one failed record. Mark the first step where source, identity, permission, ownership, timing, or outcome became unclear. Fix that step before adding another agent. This keeps the build tied to a business need instead of a tool demo.
Get the full map
If you want the map, tool stack, and build order, comment REFERRAL on the reel and follow @antoniorevenue so the DM can reach you.