/
/
Refund the right Bloomerang gift, exactly once
For gift processors and finance teams who want refunds recorded against the right transaction, with a reason and no surprise processor payouts.
On this page
Connector
Connect Bloomerang, pick your AI tool and paste the prompt.
The problem
Refund the wrong gift, or the same gift twice
Refunding a Bloomerang gift means finding the exact transaction, making sure it was not already refunded and deciding whether the processor should move money. Get it wrong and you refund twice, refund the wrong gift, or send back money you cannot recover.
Without PopdockAI
- Scroll the donor's history for the gift
- Check whether it was already refunded
- Decide on the processor option
- Refund and hope it was the right one
With PopdockAI
- The donor and the exact transaction are found, stopping if several fit
- An existing refund is checked for first
- You confirm the gift and the processor option, which stays off by default
- The refund is written once and the gift checked as refunded
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Refund the transaction of `{amount}` recorded against `{donor-name}`, after confirming it is the right one, and leave an audit trail of why.
**Step 1: Resolve the donor**
Call `bloomerang-get-constituent` with `full-name.contains` set to `{donor-name}`. If more than one matches, list them and stop until told which. If none matches, say so and stop.
Keep the id as the account-id.
**Step 2: Find the transaction**
Call `bloomerang-get-transaction` with that account-id, `amount.min` and `amount.max` both set to `{amount}`, and a date window wide enough to cover it. Show every match with its id, transaction number, date, method, amount and whether it is already marked refunded.
* if exactly one matches and it is not already refunded, carry its id forward
* if more than one matches, list them and stop until told which
* if the only match is already marked refunded, say so and stop
**Step 3: Check what has already been refunded**
Call `bloomerang-get-refund` with `transaction-id` set to the transaction id. If a refund already exists, show it and stop. Refunding twice takes real money out.
**Step 4: Confirm before writing**
Show exactly what will happen: donor name and account number, transaction id, transaction number, original amount and date, the refund date, the reason from `{refund-reason}`, and whether the payment processor will be asked to move money. State that plainly, because a processor refund is not reversible from here.
Wait for explicit confirmation of both the transaction and whether the processor should run the refund.
**Step 5: Write it**
Call `bloomerang-add-refund` once with the confirmed transaction id, date, note and processor flag. Once only. If it fails, report the error verbatim and stop. Do not retry, because the refund may have been taken even when the call reported an error; step 3 is how a person checks.
**Step 6: Verify and record why**
Call `bloomerang-get-refund` with the transaction id and read the stored refund back. Then call `bloomerang-get-transaction` with the account-id and confirm the original now shows as refunded.
Report the outcome: what was refunded, when, for what reason, and whether the processor was involved.
**Rules and Guidelines:**
* The only tool permitted to write here is `bloomerang-add-refund`, once, after explicit confirmation.
* Do not call `bloomerang-update-transaction`, `bloomerang-update-refund`, `bloomerang-add-transaction`, or any other tool whose name starts with bloomerang-add- or bloomerang-update-. Do not correct a transaction by refunding and re-entering it.
* Never set the processor refund flag on your own initiative. It defaults to off and is turned on only when the user says so in this conversation.
* Do not proceed on a partial match of the amount. The figure must match exactly.
**Validation:**
* If `{refund-reason}` is empty, ask for one. A refund with no stated reason should not be written.
* If no transaction matches the amount, widen the date window once and report what the donor actually gave, rather than refunding the nearest figure.Who it's for
One answer, three teams that use it
Gift processors
Fix a duplicate entry
Refund the extra gift with a recorded reason, without touching the processor.
Refund Alex Kim's 100 gift, it was entered twice by mistake.
Nonprofit accountants
Control processor refunds
Processor payouts only happen when you turn them on, so money is not sent back by accident.
Refund Maria Lopez's 500 card gift and return the money through the processor.
Donor relations staff
Handle a donor's refund request
Find the exact gift and confirm it before anything is changed.
Sam Patel asked for his 50 gift back because he gave the wrong amount. Refund it.
How it works
What PopdockAI does when you ask
You name the donor, amount and reason, and your AI assistant finds the exact gift to refund. Nothing is written until you confirm, and a refund with no reason is never written.
01
Ask
You name the donor, the amount and the reason.
02
Find
It finds the exact transaction and checks for an existing refund.
03
Confirm
You confirm the gift and whether the processor returns money.
04
Refund
It writes the refund once and reads it back.
What PopdockAI provides
The tools behind the answer
Ready made tools for Bloomerang and one secure connection to your AI tool. No code, no exports.
bloomerang-get-constituent
bloomerang-get-transaction
bloomerang-get-refund
bloomerang-add-refund
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
The right gift refunded exactly once
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
