Skip to content
AgentZforiMIS®

Fundraising and giving recipes

Prompts for donor context, gifts, pledges, receipts, Gift Aid, recurring giving, and lapsed-donor engagement. The recipes protect donor trust by checking evidence before money, receipts, or outreach are changed.

Copy a request into your AI app and replace the words in square brackets with your own. See Using a recipe.

Review a major donor before a stewardship call

Section titled “Review a major donor before a stewardship call”

Recipe R-03-01 · Kind of request: Look up · For: Fundraising team, Leadership team

When to use it: Use this before a donor meeting, thank-you call, board introduction, or cultivation conversation. Fundraisers need the whole relationship, not just the last gift amount.

What AgentZ does: AgentZ pulls together donor, member, event, finance, and communication evidence into a concise brief. It should identify relationship context and risks, while keeping the work read-only.

Before you begin: Have the donor name, organisation, or ID and the purpose of the call ready.

Keep in mind: Sensitive giving context needs discretion. Confirm the donor match and do not include speculative notes as facts.

Record a one-off gift with campaign, recognition, and tribute details

Section titled “Record a one-off gift with campaign, recognition, and tribute details”

Recipe R-03-02 · Kind of request: Review then change · For: Fundraising team, Finance team

When to use it: Use this when entering cheques, bank transfers, phone gifts, or staff-assisted donations. The fundraising team wants the gift tied to the right donor, campaign, and acknowledgement path from the start.

What AgentZ does: AgentZ confirms the donor, checks campaign/source context and pledge or tribute clues, then prepares the gift record for approval. After approval it should read back the gift details and next receipt or acknowledgement step.

Before you begin: Have donor details, amount, payment method, date received, appeal/source codes, and tribute or soft-credit instructions.

Keep in mind: Gift entry affects finance, donor history, receipts, and campaign reporting. Confirm codes and donor identity before writing.

Recipe R-03-03 · Kind of request: Review then change · For: Fundraising team, Finance team

When to use it: Use this when a donor commits to give over time. Staff need the pledge schedule to match the donor promise and future finance follow-up.

What AgentZ does: AgentZ reviews the donor and existing pledge context, builds the proposed installment schedule, and highlights overlaps or missing details. It should pause before creating the pledge or schedule and then read back the approved setup.

Before you begin: Have the pledge amount, campaign/fund, start date, frequency, installment count, and any restrictions or recognition notes.

Keep in mind: A pledge is a commitment, not a received gift. Keep pledge setup separate from payment receipt unless the donor is paying immediately.

Recipe R-03-04 · Kind of request: Review then change · For: Fundraising team, Finance team

When to use it: Use this when a pledge installment arrives by cheque, transfer, card, or staff-entered payment. The goal is to reduce pledge balance correctly without creating an unrelated gift.

What AgentZ does: AgentZ finds the donor pledge, compares the payment against the schedule, checks for recent duplicate entries, and prepares the payment application. It should wait for approval and then report the new pledge status.

Before you begin: Have the donor, amount, date, payment method, and any bank or receipt reference ready.

Keep in mind: If the payment does not match the schedule, decide whether it is partial, extra, or a correction before recording it.

Check whether a gift receipt or acknowledgement has gone out

Section titled “Check whether a gift receipt or acknowledgement has gone out”

Recipe R-03-05 · Kind of request: Look up · For: Fundraising team, Support team

When to use it: Use this when a donor asks for a receipt, a trustee wants evidence of acknowledgement, or staff suspect a receipt failed. The team needs clear evidence before resending or changing a gift.

What AgentZ does: AgentZ reads gift, receipt, and communication evidence, then explains what appears to have happened. It should suggest the next action and separate read-only findings from resend or correction steps.

Before you begin: Have the donor name, gift date, amount, receipt number, or support ticket details ready.

Keep in mind: Do not resend receipts automatically. Check whether the original gift details are correct first.

Prepare a card gift through the approved payment flow

Section titled “Prepare a card gift through the approved payment flow”

Recipe R-03-06 · Kind of request: Guided handoff · For: Fundraising team, Finance team

When to use it: Use this when staff take a donation over the phone or help a donor complete a card gift. The important job is to use the secure payment route while still coding the gift correctly.

What AgentZ does: AgentZ checks the donor and gift coding, confirms payment-readiness context, and guides staff to the hosted or approved payment surface. It should never collect card details in the prompt and should read back the gift or payment evidence after completion where available.

Before you begin: Have donor details, amount, campaign/fund, receipt preference, and the approved payment process ready.

Keep in mind: Never type card numbers, CVV, or full payment credentials into AgentZ. Use the secure payment surface.

Set up an appeal or campaign tracking structure

Section titled “Set up an appeal or campaign tracking structure”

Recipe R-03-07 · Kind of request: Review then change · For: Fundraising team, Communications team

When to use it: Use this before fundraising staff launch an email, mail pack, event appeal, or digital campaign. Good campaign tracking setup makes later fundraising reporting much easier.

What AgentZ does: AgentZ searches current campaign and source-code records, identifies naming conflicts, and proposes a clean tracking structure. It can help create supported setup records after approval and gives the team the codes to use in communications.

Before you begin: Have campaign name, fund, audiences, channels, dates, and reporting needs ready.

Keep in mind: Tracking setup should be agreed before gifts arrive. Avoid creating several similar source codes for the same audience unless reporting needs them.

Capture Gift Aid evidence and preview claim readiness

Section titled “Capture Gift Aid evidence and preview claim readiness”

Recipe R-03-08 · Kind of request: Review then change · For: Fundraising team, Finance team

When to use it: Use this for UK charities when a donor signs a declaration or before a Gift Aid claim is prepared. Staff need confidence that reclaimable gifts are supported by the right evidence.

What AgentZ does: AgentZ checks donor and gift evidence relevant to Gift Aid, separates eligible from questionable gifts, and estimates the claim. It does not record declarations: staff record them on the donor’s Giving tab > Gift Aid > Declarations, and iMIS submits the claim to HMRC from Process Claims.

Before you begin: Have the donor, declaration date/source, gift date range, and charity Gift Aid policy ready.

Keep in mind: Gift Aid is compliance-sensitive. AgentZ can help organise evidence, but finance remains responsible for claim approval.

Check recurring donation or Direct Debit setup

Section titled “Check recurring donation or Direct Debit setup”

Recipe R-03-09 · Kind of request: Look up · For: Fundraising team, Finance team

When to use it: Use this when a donor asks about a regular gift, a collection seems missed, or finance wants to confirm Direct Debit readiness. The team needs the schedule and payment posture in one view.

What AgentZ does: AgentZ reads recurring gift, scheduled payment, donor, and recent transaction evidence, then explains what is active, failed, paused, or unclear. It should recommend the next safe staff action rather than changing bank/payment details casually.

Before you begin: Have the donor name/ID and the date range or collection month in question ready.

Keep in mind: Recurring payment details are sensitive. Use approved finance processes for bank or card changes.

Find lapsed donors for a thoughtful re-engagement appeal

Section titled “Find lapsed donors for a thoughtful re-engagement appeal”

Recipe R-03-10 · Kind of request: Multi-step plan · For: Fundraising team, Communications team

When to use it: Use this when planning LYBUNT, SYBUNT, or reactivation campaigns. Fundraisers want to prioritise people with a real past relationship and avoid insensitive outreach.

What AgentZ does: AgentZ analyses giving history alongside communication preferences and other engagement evidence, then builds practical segments for review. It should flag exclusions, data-quality issues, and consent concerns before any export or campaign step.

Before you begin: Set the gift years, minimum gift level if any, exclusions, and intended campaign channel.

Keep in mind: Lapsed-donor outreach must respect preferences and sensitive statuses. Review the exclusion logic before sending anything.

Correct a gift date and prepare the receipt follow-up

Section titled “Correct a gift date and prepare the receipt follow-up”

Recipe R-03-11 · Kind of request: Review then change · For: Fundraising team, Finance team

When to use it: Use this when a gift was entered under the wrong date or period. The correction may affect receipts, campaign reports, finance reconciliation, and Gift Aid or tax treatment.

What AgentZ does: AgentZ finds the gift, reviews related receipt and coding evidence, and explains the consequences of changing the date. It should wait for finance approval before updating and then outline any receipt or acknowledgement follow-up.

Before you begin: Have the gift identifier, correct date, reason for correction, and finance approval path ready.

Keep in mind: Changing gift dates can affect financial reporting. Do not make the correction without finance agreement.