/
/
Log Bloomerang donor conversations once, on the right record
For fundraisers who want a call logged as an interaction, and any promise turned into a task, by telling their AI assistant.
On this page
Connector
Connect Bloomerang, pick your AI tool and paste the prompt.
The problem
Calls logged on the wrong donor, twice, or not at all
After a donor call the conversation should be logged in Bloomerang and any promise turned into a task. It is easy to put it on the wrong constituent, log it twice or forget the follow-up, and typing it later adds detail never said.
Without PopdockAI
- Search for the donor and pick a record
- Check whether someone already logged it
- Type the interaction from memory
- Forget to create the follow-up task
With PopdockAI
- The constituent is found, asking which when several match
- The last week is checked for a similar interaction
- You approve the exact interaction and any follow-up task
- Each is written once and read back with its id
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Record that a conversation took place with `{constituent-name}`, writing it to their record as an interaction, and open a follow up task if one is needed. What was said is in `{contact-summary}`, over the channel `{channel}` (default Phone).
**Step 1: Resolve the constituent before writing anything**
Call `bloomerang-get-constituent` with `full-name.contains` set to `{constituent-name}`. If more than one record comes back, list each with full name, primary email, city and account number, then stop and ask which is meant. If nothing comes back, retry once with the surname only, and if it still finds nothing, say so and stop. Never create a constituent to make this prompt work.
Keep the id. It is the account-id for every write below.
**Step 2: Check this is not already logged**
Call `bloomerang-get-interaction` with that account-id and `date.from` set to seven days ago. If an interaction already exists with the same channel and a materially similar subject, show it and ask whether to log a second one before going further.
**Step 3: Confirm what will be written**
Show the exact interaction you intend to create: the constituent name and account number, the date, the channel, the purpose, a subject line of at most eight words drawn from `{contact-summary}`, whether it was inbound, and the note body.
Wait for the user to confirm. Do not write on an assumed yes.
**Step 4: Write it**
Call `bloomerang-add-interaction` once, with the confirmed values. Once only. If it fails, report the error and stop; do not retry with altered values in the hope of getting it through.
**Step 5: Follow up, only if one is warranted**
If `{contact-summary}` describes something that has to happen next, propose a task: subject, purpose, channel, due date and owner. Show it, wait for a second confirmation, then call `bloomerang-add-task` once with the same account-id.
If nothing was promised, do not create a task.
**Step 6: Confirm it landed**
Call `bloomerang-get-interaction` with the account-id and today as `date.from`, and report the stored record back with its id. If a task was created, call `bloomerang-get-task` with the account-id and confirm it the same way.
**Rules and Guidelines:**
* The only tools permitted to write here are `bloomerang-add-interaction` and `bloomerang-add-task`, each at most once, each after its own explicit confirmation.
* Do not call `bloomerang-update-constituent`, `bloomerang-add-note`, `bloomerang-add-constituent`, or any other tool whose name starts with bloomerang-add- or bloomerang-update-. If the conversation revealed a new email address or phone number, report it for someone to apply and leave the record alone.
* Do not invent detail. Anything not present in `{contact-summary}` does not go in the note.
* Write the note in plain past tense, naming what was discussed and what was agreed.
**Validation:**
* If `{contact-summary}` is empty, ask what was discussed. Do not log an empty interaction.
* If `{channel}` is not one of the values the existing interactions use, ask rather than guessing.Who it's for
One answer, three teams that use it
Major gift officers
Log visits while they are fresh
Describe the meeting in a sentence and approve the exact entry, with a follow-up task if promised.
Log an in person visit with Maria Lopez today. We talked about the scholarship fund and I will send a proposal next week.
Development officers
Avoid double logging
A similar entry from this week is flagged before anything is written.
Log an email with Sam Patel about his matching gift, but check nobody logged it already.
Executive directors
Record calls without the admin
Your summary becomes the note, with nothing added that you did not say.
Log a phone call with Alex Kim: thanked him for his gift and invited him to the gala.
How it works
What PopdockAI does when you ask
You describe the conversation and your AI assistant prepares the Bloomerang interaction. Nothing is written until you have seen it and said yes, and no new constituent is ever created.
01
Ask
You name the donor and describe the conversation and channel.
02
Check
It finds the constituent and looks for a similar entry this week.
03
Confirm
You approve the exact interaction, and any follow up task.
04
Create
It writes each once and reads it back with its id.
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-interaction
bloomerang-add-interaction
bloomerang-add-task
bloomerang-get-task
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
Every conversation logged once, follow-ups captured
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)
