Connectors

/

Chorus

/

Find Chorus donor conversations missing from Bloomerang
Report
Cross-Connector

Find donor calls in Chorus that never reached Bloomerang

For fundraising operations teams who want every recorded donor conversation logged in Bloomerang, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Find Chorus donor conversations missing from Bloomerang
Which donor conversations in Chorus from the last 30 days haven't been logged in Bloomerang?
7 donor conversations from the last 30 days have no Bloomerang interaction. - Unlogged: Jordan Lee call with Alex Morgan, 24 September - Counts: 42 checked, 28 logged, 7 unlogged, 7 with no Bloomerang match - By owner: Jordan Lee 4, Sam Patel 3 Want the full table of unlogged conversations?
Chorus
Sample figures. Your results come from your own account.
chorus-get-engagements
chorus-get-conversation-participants
bloomerang-get-email-address
bloomerang-get-interaction

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Chorus

Chorus
Run it on your own Chorus data.

Connect Chorus, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Donor records miss conversations that happened

Fundraisers record calls in Chorus but do not always log them in Bloomerang, so donor records miss real conversations. Finding the gaps means checking each call's participants against constituents and hunting for a matching interaction.

Without PopdockAI

  • List recent recorded calls
  • Match outside participants to constituents by email
  • Search for an interaction near each call date
  • Tally gaps per fundraiser by hand

With PopdockAI

  • Outside participants are matched to constituents by email
  • Interactions within a day of each call are checked
  • Unlogged donor conversations come back with owner and constituent
  • Counts and a tally per owner are shown, nothing written

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** List every Chorus conversation in the last `{lookback-days}` days (default 30) that involved a Bloomerang constituent but has no matching Bloomerang interaction, optionally limited to conversations owned by the Chorus user `{rep-email}` (if empty, include every user).

**Step 1: List the conversations in Chorus**

Call `chorus-get-engagements` with `date.from` set to the start of the window and, if `{rep-email}` is given, `user-email` set to it. Use `max-records` 50. If the result is capped at 50, say so in the report and suggest a shorter window.

**Step 2: Find the donors on each conversation**

For each conversation, call `chorus-get-conversation-participants` with its `conversation-id`. Keep external participants only (no `user-id`, and not typed as internal). For each distinct external email, call `bloomerang-get-email-address` with `value` set to it and take `account-id`. Cache the result so each email is looked up once.

**Step 3: Check Bloomerang for a logged interaction**

For each conversation and matched account id, call `bloomerang-get-interaction` with `account-id`, and with `date.from` and `date.to` set to one day either side of the conversation date. The conversation counts as logged if any interaction comes back in that range.

**Step 4: Report**

* A table of unlogged conversations: date, subject, Chorus owner (`user-name`), constituent name, Bloomerang account id, `conversation-id`.
* A count of conversations checked, logged, unlogged, and with no Bloomerang match at all.
* Per Chorus owner: how many of their donor conversations are unlogged.
* Close by suggesting the `log-conversation-to-bloomerang` prompt for any row the user wants recorded.

**Rules & Guidelines:**

* Tools whose names start with chorus are on the chorus server; tools whose names start with bloomerang are on the bloomerang server.
* This prompt is read-only. Do not call `bloomerang-add-interaction`, `bloomerang-add-note`, `bloomerang-add-task` or any other Bloomerang add or update tool, and do not call any Chorus action such as `chorus-add-moment`.
* Conversations whose participants match no constituent are not unlogged donor conversations; count them separately and do not list them individually.

**Validation:**

* If Chorus returns no conversations in the window, say so and stop.
* Chorus dates carry a time; compare by calendar day. Match emails case-insensitively.

Who it's for

One answer, three teams that use it

Development directors

See who is behind on logging

A tally per owner shows which fundraisers need to catch up.

Which donor conversations in Chorus from the last 60 days are not logged in Bloomerang, by owner?

Major gift officers

Log your missing conversations

Limit it to yourself to get the calls you still need to log.

Which of my Chorus calls with donors this month have no Bloomerang interaction?

Database managers

Keep donor history complete

Counts of checked, logged and unmatched calls show how complete donor records are.

How many Chorus donor calls last quarter were logged in Bloomerang, and how many were not?

How it works

What PopdockAI does when you ask

You choose a look-back period and your AI assistant finds donor conversations missing from Bloomerang. It warns when the result was capped so you can shorten the window.

01

Ask

You choose a look-back period, and optionally one Chorus user.

Your AI tool

02

Match

It matches outside participants to Bloomerang constituents by email.

chorus-get-engagements
chorus-get-conversation-participants
bloomerang-get-email-address

03

Check

It looks for an interaction logged within a day of each call.

bloomerang-get-interaction

04

Report

You get unlogged donor conversations, counts and a tally per owner.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Chorus and one secure connection to your AI tool. No code, no exports.

get-data

chorus-get-engagements

Returns recorded calls and meetings from Chorus, with the subject, date, duration, participants and the account each conversation relates to. Filter by date range, owner or account to pull the conversations behind a deal or a period.
get-data

chorus-get-conversation-participants

Returns the people who took part in Chorus conversations, with their name, email, title and company. Use it to see who was on a call, and which side they were on.
get-data

bloomerang-get-email-address

Returns constituent email addresses from Bloomerang. Filter by address, type or primary flag, and include or exclude addresses flagged bad.
get-data

bloomerang-get-interaction

Returns logged interactions with constituents in Bloomerang: calls, emails, meetings and mailings. Filter by date range, channel, purpose or subject.
Read only.Nothing in Chorus Changes

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.

How Popdock AI secures your data

The outcome

Every recorded donor conversation on the donor record

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

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.

Try PopdockAI Free
See Documentation