Live — Riverside Community Trust
Foyer answers the questions your community asks over and over, and notices the donors who quietly stopped giving. Anything that goes out in your name waits for you first.
Hi! I'm the front desk for Riverside Community Trust. Ask me about events, parking, sign-ups, or your donations.
When is it. Where do I park. Can I still sign up. Is there a waitlist. Every one is easy, every one needs answering, and they arrive while the people who could answer them are running the actual event.
In the demo data: 2 events, 1 already at capacity, 50 spots to track by hand.
Nobody sends a note to say they have stopped giving. They just stop, and six months later someone notices. The window to say something useful has already closed.
In the demo data: James Okafor last gave 194 days ago, against a 45-day pattern. Nobody flagged it.
It does not answer anything itself. A question about parking goes to the Front Desk. A question about a donor goes to the Donor Steward. Both sub-agents are exposed to it as tools, so routing is a decision it makes and logs, not a keyword match.
ask_front_deskask_donor_stewardEvent times, parking, remaining spots, sign-ups. It can write an RSVP straight to the roster and refuse one when an event is full. These are small and reversible, so nobody needs to approve them.
get_event_infomake_rsvpIt reads giving history, spots donors who have drifted past their own pattern, and writes the message. Then it stops. There is no send tool in its hands to reach for — the draft goes to the approval queue with the reasoning that produced it, and waits.
get_donor_profilecheck_lapsing_donorsdraft_followup_messagequeue_approvalWhat the agent did, why it did it, and what the human decided — written in language a board member can read without a technical briefing. Approvals and rejections go in the same trail as the agent's own actions.
log_decisionAnswers the questions that arrive over and over, and writes RSVPs straight to the roster. Small, reversible, no approval needed.
Measures each donor against their own giving rhythm, not a generic threshold. Someone who gives monthly is late at 45 days; someone who gives twice a year is not.
Nothing donor-facing leaves without a person tapping approve. The reasoning travels with the draft, and the decision joins the same log as the agent's own actions.
Small nonprofits run on volunteers and rotating boards. The person who set the agent up may not be there in a year. So the question is never just whether it worked — it is whether anyone can explain what it did.
The front desk above is live. Queue a donor message and it will be waiting in the approval panel, reasoning attached.