Not for profit
DonorPerfect
Connect your AI to DonorPerfect
Fundraising managers, database administrators, and executive directors keep every donor, gift, and pledge in DonorPerfect, but year-end summaries, lapsed donor lists, and pledge follow-ups still take hours of report building. AI can answer in minutes, but only if it keeps donor records private and records gifts and pledges only through steps your team approves.
Why it matters
Capabilities that matter most for DonorPerfect
01
Year-end and lapsed reports ready
Install ready-made DonorPerfect lists for giving summaries, lapsed donors and pledges from the app store.
02
Donors beside campaigns
Join DonorPerfect gifts with email marketing or event lists to see which appeals actually raised money.
03
Gifts recorded through approved steps
AI tools keep donor records private and record gifts and pledges only through actions you approve.
Use cases
Example AI Use Cases for DonorPerfect
scenario
-
Prospective supporters often join calls recorded in Chorus long before they are in DonorPerfect. Adding them means checking each email against donor records and additional addresses, then keying in names and a donor type by hand.
What popdock provides
--
Choose how many days of Chorus conversations to look back over, and optionally one account. It gathers the outside participants with an email and checks each against DonorPerfect donors and their additional addresses, keeping only people found in neither. You see each person with their company and recent conversations, choose which to add and the DonorPerfect donor type, and nothing is written without that selection. Names that do not split cleanly are shown to you to enter, and each new donor is read back with its new id.
Business outcome
---
New supporters from your calls become DonorPerfect donors, with no duplicate records and no guessed names.
scenario
-
Before calling a donor you need their giving history, open pledges and flags from DonorPerfect, plus what was said on the last few Chorus calls. Gathering it means two systems and a lot of scrolling, and a follow-up promised last time is easy to miss.
What popdock provides
--
Give the DonorPerfect donor by id or email, and how many recent conversations to include. It reads the donor's gifts, open pledges, recent and overdue contacts and flags from DonorPerfect, then finds their Chorus conversations and emails using every email on file. The one-page brief covers giving, recent conversations, outstanding follow-ups and three talking points grounded in the data. A follow-up counts only when a meeting summary states it, and nothing is changed in either system.
Business outcome
---
You start every donor call knowing their giving, their open pledges and what was promised last time.
scenario
-
Piecing together every conversation with one donor means searching Chorus for each email address they have used, plus calls filed under their organization. It is slow, and it is hard to tell a real match from a company with a similar name.
What popdock provides
--
Give the DonorPerfect donor by id or email, and how far back to look. It collects every email on the donor and their additional addresses, then lists their Chorus calls, meetings and emails in date order. Conversations found only through the organization name are labelled as weaker evidence, and ones that look unrelated are set apart as possible matches. It never widens the search to name matching, ends with totals and the most recent touch, and changes nothing.
Business outcome
---
You see the full conversation history with a donor in one timeline, with weak matches clearly labelled.
scenario
-
Your largest donors can go months without a conversation, and nothing in DonorPerfect raises a flag. Finding them means checking each major donor against Chorus calls, meetings and emails one at a time.
What popdock provides
--
Set the lifetime giving threshold and how far back to look. It reads DonorPerfect donors above the threshold and checks Chorus for recent calls, meetings and emails by email and by organization name, labelling organization matches as weaker evidence. Donors with no recent touch are listed by lifetime giving, with their last touch at any time if one exists, and donors with no email or organization are listed as cannot check. It warns when the list is capped and changes nothing.
Business outcome
---
Your most generous donors are not left without contact, because the ones gone quiet are listed by giving.
scenario
-
Pledges with a balance still owing need someone to talk to the donor, but DonorPerfect does not show whether that has happened. Checking means looking up each pledge and searching Chorus for conversations since the pledge date.
What popdock provides
--
Choose the earliest pledge date, or use the default of a year ago. It reads DonorPerfect pledges with a balance above zero, then checks Chorus for any call, meeting or email with each donor since the pledge was made. Pledges nobody has followed up are listed by balance, largest first, and ones with contact show the latest conversation and any summary line about the pledge or a payment. It never says a pledge was discussed unless the summary says so, and changes nothing.
Business outcome
---
Outstanding pledge balances get a timely follow-up, starting with the largest amounts nobody has discussed.
scenario
-
Every conversation with a donor should be recorded as a DonorPerfect contact, but logging a Chorus call means working out which participants are donors and writing the same summary for each. Calls go unlogged, or get logged twice.
What popdock provides
--
Give the Chorus conversation and, optionally, the activity code. It reads the call and its outside participants, matches each to a DonorPerfect donor by email only, and checks for a contact already logged that day. You see each participant's status and the exact contact to be written, can pick from the activity codes, and nothing is saved without your confirmation. Existing contacts are never overwritten, ambiguous and already logged donors are skipped and listed, and each new contact is read back.
Business outcome
---
Donor conversations are recorded in DonorPerfect once, against every donor who took part, with the summary attached.
scenario
-
Calls with donors recorded in Chorus often never become DonorPerfect contacts, so the donor history misses real conversations. Finding them means matching each participant to a donor and checking the contact log around each call date.
What popdock provides
--
Choose how far back to look, and optionally one Chorus user. It reads the Chorus conversations and their outside participants, matches each email to a DonorPerfect donor, and checks for a contact within two days of the call. You get a table of unlogged conversation and donor pairs, a count of logged ones, and outside participants who are not donors counted by company. Emails matching more than one donor are listed as ambiguous, the list warns when capped, and nothing is written.
Business outcome
---
Your donor records reflect every conversation, because you know exactly which calls still need logging.
scenario
-
Reporting on a DonorPerfect campaign means confirming the right campaign code, pulling every gift in the date range, and adding up totals, averages and monthly giving in a spreadsheet. Naming the top donors and comparing them with their usual giving takes another round of lookups.
What popdock provides
--
Name the campaign and a date range, or default to the last twelve months, and it confirms the exact campaign code before reading any gifts, stopping if several codes match. It totals what was raised, the gift count, average gift, distinct donors, the split between outright gifts and pledge payments, and giving by month. The top ten donors are named with their lifetime totals for comparison. Every figure comes from the gifts it read, it says when results were capped, and nothing in DonorPerfect is changed.
Business outcome
---
You get a campaign results summary with top donors and monthly trend, grounded in the actual gift records, in minutes.
scenario
-
Before a donor visit or call, a fundraiser has to piece together giving history, open pledges, recent contacts, flags, linked relationships and addresses from different screens in DonorPerfect. Missing one of them, such as an unpaid pledge, can make the conversation awkward.
What popdock provides
--
Give a donor name or email and it identifies the donor, listing the candidates and stopping if more than one matches. It then reads their gifts, pledges with outstanding balances, last contacts, flags, linked donors, addresses and committee or volunteer notes. The briefing covers lifetime and year-to-date giving, open pledges, the last three contacts and two or three observations a fundraiser can act on. Empty sections are stated as empty, nothing is estimated, and nothing in DonorPerfect is changed.
Business outcome
---
Fundraisers walk into every donor conversation with a complete, accurate briefing instead of fragments from several screens.
scenario
-
Stored donor cards expire quietly, and the first sign is a failed pledge instalment. Finding them in DonorPerfect means filtering payment methods by expiry date, looking up each donor, and checking who still has a pledge billing against that card.
What popdock provides
--
Give a cutoff date, three months ahead by default, and it lists the stored payment methods expiring by then, resolves each donor's name and email, and checks for pledges with an outstanding balance. The results are sorted by expiry and split into urgent, where a pledge is open or the card is the default, and routine, with urgent donors lacking an email marked for a call. Only the last four digits are ever shown, cards without a donor are listed separately, and nothing is updated.
Business outcome
---
You reach donors before their card fails, protecting recurring pledge income with a prioritized contact list.
scenario
-
Lapsed donors are often worth more than new prospects, but finding them in DonorPerfect means checking every substantial donor for gifts since a cutoff date. Ranking who to call first, and spotting the ones with an unpaid pledge, usually takes a day of exports.
What popdock provides
--
Set a minimum lifetime total and a lapse date, 500 and one year ago by default, and optionally a state, and it tests each candidate for recent gifts, keeping only those who have stopped. For each lapsed donor it adds the last gift amount and date and when they were last contacted, and flags open pledge balances. The list is ranked by lifetime value into call first, write to, and check the record groups. It says how many donors it examined, does not speculate on why anyone lapsed, and writes nothing.
Business outcome
---
You work a ranked reactivation list from the top down, starting with the lapsed donors most worth reclaiming.
scenario
-
Families often ask who gave in memory of a loved one, but in DonorPerfect tributes connect to donors only through individual gifts. Answering means finding the tribute, listing its gifts, opening each one and then looking up each donor, a slow chain that is easy to get wrong.
What popdock provides
--
Name the tribute and it finds it, asking you to choose if several match, then follows each attached gift to its amount, date, campaign and donor. You get the tribute's own totals, a table of gifts with donor names, the total of the gifts resolved with a note if it differs from the tribute record, repeat givers, and which donors have an email for acknowledgement. Unresolved gifts are listed rather than dropped, no commentary is added about the person honoured, and nothing is changed.
Business outcome
---
You can answer a family's question about tribute gifts accurately and sensitively, with acknowledgement contacts ready.
scenario
-
Tagging a group of DonorPerfect donors with a segmentation flag means building the selection from several filters, checking who already carries the flag and then setting it donor by donor. A wrong criterion flags the wrong people, and there is no easy way to undo a large batch.
What popdock provides
--
Name the flag and describe who should get it, for example donors in a state above a giving level, and it confirms the flag exists before anything else, never inventing one. The criteria are translated into donor filters, narrowed with gift history where needed, and donors who already carry the flag are removed. You see the full list with what qualified each donor, and lists over 50 need a second confirmation. Only confirmed donors are flagged, it stops on the first failure, and a spot check confirms the count rose.
Business outcome
---
Donor segments are flagged accurately in one pass, with nobody outside your criteria tagged by mistake.
scenario
-
Linking household members or related donors in DonorPerfect sounds simple, but it is easy to pick the wrong donor with a common surname or record a relationship that already exists in the other direction. Untangling a wrong link later takes more time than making it.
What popdock provides
--
Name both donors and the relationship code, and it identifies each donor, stopping if either name returns nothing or more than one match. The code is checked against your valid relationship codes, and existing links are checked in both directions so a duplicate is never created. You see the full link, with names, ids, code and direction, and it is saved only once you confirm, then read back. Direction is never swapped to fit a code, and a reciprocal link is treated as a separate confirmed step.
Business outcome
---
Household and relationship links are recorded once, between the right donors, in the right direction.
scenario
-
After a call or visit, logging the activity in DonorPerfect is easy to put off, and when two people log the same touchpoint the history gets cluttered. Getting the donor, the activity code and the date right each time takes more care than it should.
What popdock provides
--
Give the donor's name or email, what happened and optionally an activity code, and it identifies the donor and shows their last three contacts. If a contact with the same code is already logged on the same date, it asks whether this is a separate interaction. The activity code is checked against your valid codes, the summary is recorded exactly as you wrote it without embellishment, and the contact is saved only after you confirm, then read back with its id.
Business outcome
---
Every donor touchpoint is logged once, accurately, keeping the contact history clean for the whole team.
scenario
-
Entering a gift by hand in DonorPerfect means finding the right donor, checking the campaign and GL codes exist, and making sure the same gift was not already entered by a colleague. A typo in a code or a double entry throws off receipts and reconciliation.
What popdock provides
--
Give the amount, the donor's name or email, the date and optionally a campaign, and it identifies the donor, stopping rather than creating one if there is no single match. The campaign and any GL or solicitation code are checked against the code list and never invented. A gift of the same amount on the same date is flagged as a likely duplicate and stops the process. You see the exact gift before it is saved, it is written only once after you confirm, then read back with its new gift id.
Business outcome
---
Gifts are recorded once with valid codes, so receipts and reconciliation start from clean data.
scenario
-
Setting up a recurring pledge in DonorPerfect means checking whether the donor already has one, validating the campaign and GL codes and getting the amount, total and frequency right. A duplicate pledge or a wrong total causes billing confusion that is hard to explain to a donor.
What popdock provides
--
Give the donor, instalment amount, frequency and start date, and it identifies the donor and reviews their existing pledges and giving so far. If an open pledge already exists at the same amount and frequency, it asks before going further. Campaign, solicitation and GL codes are checked against your valid codes, and if no total is given, the arithmetic is shown. The pledge is saved only once after you confirm, then read back with its balance; no instalments are recorded.
Business outcome
---
Recurring pledges are set up correctly the first time, without duplicates or wrong totals reaching the donor.
scenario
-
DonorPerfect assigns a GL code to every gift, and each one needs a matching Dynamics 365 Business Central account that can take a posting. When an account has been blocked, renamed or turned into a heading, gift entries start failing and nobody knows which codes are affected.
What popdock provides
--
Optionally name the Business Central company and whether to include inactive codes, and it collects every DonorPerfect GL code and every campaign mapped to an account, then looks up each account in Dynamics 365 Business Central. Each code is classed as missing, blocked, not a posting account, closed to direct posting, a balance sheet account worth reviewing, or OK. Formatting differences are retried once and reported. You get a table and one line per problem group saying what to fix and where. Nothing is changed in either system.
Business outcome
---
Broken GL code mappings are found and explained before they cause rejected journal lines at month end.
scenario
-
Organisations that both donate to you and invoice you deserve a closer look, but DonorPerfect and Dynamics 365 Business Central never compare notes. Finding the overlap means matching vendor names and emails against donor records and then adding up gifts and purchases for each.
What popdock provides
--
Give a start date, the first of the year by default, and it reads your active Dynamics 365 Business Central vendors and searches DonorPerfect for each by email, then by name with legal suffixes removed. A name-only match counts as confirmed only when city or state agree. For each match it totals gifts, including in-kind gifts, and posted purchase invoices. Patterns such as rising gifts alongside rising purchases are flagged for a human to review, clearly not as findings of wrongdoing, and nothing is changed.
Business outcome
---
Potential conflicts of interest between donors and vendors surface for review, backed by real gift and purchase totals.
scenario
-
Some of your donors are also customers you invoice, but development staff work in DonorPerfect and finance works in Dynamics 365 Business Central. Without a combined view, a team can make a major ask of an organisation that has unpaid invoices outstanding.
What popdock provides
--
Set a minimum lifetime giving level, 1000 by default, and optionally a name, and it reads matching DonorPerfect organisation donors and looks for each in Dynamics 365 Business Central by email, then by name. A name-only match is labelled as such unless city or state agree, and multiple candidates are all listed rather than one picked. Each match shows giving next to sales, balance due and open invoices, and donors with money owed who gave this year are called out. It is read-only.
Business outcome
---
Development and finance see the same relationship picture, so asks and invoices are coordinated rather than colliding.
scenario
-
Getting gifts from DonorPerfect into Dynamics 365 Business Central usually means retyping them as journal lines, checking each GL code is a valid account, and hoping none were entered last week too. A duplicate or a line against a blocked account means rework for the accountant.
What popdock provides
--
Give a date range and a balancing account, and it reads the DonorPerfect cash gifts, leaving out pledges, soft credits and gifts with no GL code. Each gift is checked against Dynamics 365 Business Central journal lines and ledger entries by its reference number, and each GL code against the chart for a usable posting account. You see the full plan with every skipped gift and its reason, and lines are created only after you confirm. The journal is never posted, and DonorPerfect is never changed.
Business outcome
---
Gift revenue arrives in Business Central as a review-ready journal, with no duplicates and no lines against unusable accounts.
scenario
-
Proving that gift revenue in DonorPerfect matches the Dynamics 365 Business Central ledger means totalling gifts by GL code, pulling posted entries for each account and chasing every difference item by item. Pledges and soft credits make the totals look wrong even when they are not.
What popdock provides
--
Give a date range and optionally one GL code, and it totals DonorPerfect cash gifts per code, excluding pledges and soft credits, then sums net credits on each matching Dynamics 365 Business Central account, ignoring reversed entries. Each code shows both totals and the difference, and codes with no account or no postings are named. For the three largest differences it lists the gifts and entries behind them and points out likely matches. It asks for the period rather than guessing and changes nothing.
Business outcome
---
Month-end gift revenue reconciliation is done in one pass, with the items behind every difference already identified.
scenario
-
A sponsor organisation can appear as a donor in DonorPerfect and a customer in Dynamics 365 Business Central at the same time. Before a renewal ask or a collections call, someone has to gather gifts, pledges, invoices and notes from both systems to avoid an embarrassing overlap.
What popdock provides
--
Name the organisation and a lookback period, 365 days by default, and it finds the DonorPerfect donor, asking you to pick if several match, and reads its gifts, open pledges and recent contacts. The same organisation is found in Dynamics 365 Business Central and its invoices, open balances, quotes, orders and customer comments are read. The combined view adds watch points such as overdue invoices next to an open pledge or a payment that may be recorded twice. It is read-only.
Business outcome
---
You see the whole sponsor relationship, giving and billing together, before the next ask or invoice goes out.
scenario
-
When a donor needs to be invoiced, someone has to retype their name and address from DonorPerfect into Dynamics 365 Business Central and check they are not already a customer. Without a note back on the donor, the next person has no idea a customer record exists.
What popdock provides
--
Give a DonorPerfect donor id and it reads the donor and their main or billing address, then searches Dynamics 365 Business Central by email and by name. If a customer already exists, it shows it and stops. Otherwise you see the exact customer to be created, with the country converted to a two-letter code, and it is created only after you confirm, then read back. The new customer number is then noted on the donor in DonorPerfect, and if that note fails you are given the number to add by hand.
Business outcome
---
Donors become invoiceable customers once, with no duplicates, and both systems record the link between them.
scenario
-
Finance asks how fundraising is tracking against budget, but gifts sit in DonorPerfect and the budget sits in Sage Intacct. Mapping GL codes to accounts, splitting pledges from payments and lining up budget periods is slow, and pledge payments are easy to count twice.
What popdock provides
--
Give a date range and optionally a budget, the default one if blank, and it totals DonorPerfect outright gifts, new pledges and pledge payments by GL code, keeping pledge payments separate so nothing is counted twice. Each code is mapped to its Sage Intacct account using DonorPerfect's own mapping, and the budget is read for whole periods only, never prorated. Revenue already posted in Sage Intacct is shown alongside, with not yet posted revenue and unbudgeted codes called out. Nothing is changed.
Business outcome
---
Leadership sees fundraising against budget by account, including gifts not yet in the ledger, without a manual crosswalk.
scenario
-
Posting each day's DonorPerfect gifts to Sage Intacct means totalling them by GL code, finding the right revenue account for each and building journal entries by hand. It is easy to post a day twice, or to post gifts that already arrived through a deposit.
What popdock provides
--
Give the gift date and a debit account, and it totals that day's outright DonorPerfect gifts by GL code and maps each code to its Sage Intacct revenue account, never guessing one. It checks for an existing entry with the same reference and for credits that already match the day's total, and asks for any required department or location. You approve a table of ready, already posted and unmapped codes, then one balanced entry per code is created as a draft unless you ask to post, and each is read back.
Business outcome
---
Daily gift revenue reaches Sage Intacct as balanced entries, one per GL code, with no day posted twice.
scenario
-
Auditors and finance teams need gift revenue in DonorPerfect to agree with what Sage Intacct posted, but differences hide in pledges, pledge payments and batch deposits. Finding which gifts are missing from the ledger, or which ledger rows no gift explains, takes days.
What popdock provides
--
Give a date range and optionally one GL code, and it splits DonorPerfect gifts into outright gifts, pledge payments and pledges for each code, then reads net posted revenue on the mapped Sage Intacct account. It tests which combination closes the gap, which shows how your organisation books pledges, then matches gifts to ledger rows one to one by amount and date, switching to daily totals when deposits are batched. Unmapped codes are reported, not guessed, and neither system is adjusted.
Business outcome
---
Gift revenue reconciles by GL code with every unmatched item named, ready for audit or month-end review.
scenario
-
Donations sometimes arrive straight into Sage Intacct as other receipts and never get entered in DonorPerfect, so donors go unthanked and giving history is incomplete. Finding them means comparing receipts on contribution accounts against gifts and then working out who each payer is.
What popdock provides
--
Give a date range and optionally a GL code, and it uses DonorPerfect's GL code mapping to find the Sage Intacct contribution accounts, reads the receipt lines on them and matches each to DonorPerfect gifts by amount and date, treating batch deposits as matched. For each unmatched line it proposes a donor, lists candidates, or says none was found. You choose which rows to record, each is checked again for an existing gift, and only then saved. Missing donors are listed for you to add, never created.
Business outcome
---
Donations received in the ledger find their way into DonorPerfect, so every donor is credited and thanked.
scenario
-
Related-party reviews, such as for an audit or Form 990, ask what the organisation paid to board members, their family and their businesses. Board members are flagged in DonorPerfect, payments live in Sage Intacct, and matching names between the two by hand is slow and unreliable.
What popdock provides
--
Name the flag, BOARD by default, and a date range, and it lists the flagged DonorPerfect donors and the donors linked to them. Each is searched among Sage Intacct vendors and graded strong or possible, with name-only matches never graded above possible; flagged people who are employees are noted. Payments and bills are totalled for each matched vendor. Unmatched donors are listed to show they were checked, and the report states findings, not conclusions. Nothing is changed.
Business outcome
---
Your related-party review starts from a complete, graded list of payments, with every flagged person accounted for.
scenario
-
When a donor asks whether their gift was received, or an auditor picks one gift to test, someone has to search Sage Intacct for a matching receipt, payment or ledger entry. Batch deposits and check numbers that do not match make one gift surprisingly hard to find.
What popdock provides
--
Give a DonorPerfect gift id and a window of days, 5 by default, and it reads the gift and its donor, explaining when a soft credit or pledge has nothing to trace. It maps the GL code to its Sage Intacct account, then searches by check reference, ledger amount and other receipts around the gift date. Each hit is graded confirmed or possible, possible is never reported as confirmed, and if nothing matches it lists larger rows that could be batch deposits. It is read-only.
Business outcome
---
You can show exactly where a gift landed in Sage Intacct, or prove it never arrived, in one read.
scenario
-
Targeting a DonorPerfect group in Mailchimp, such as major donors or event attendees, means exporting the flagged donors, checking who is actually in the audience and adding them to a segment one by one. Adding someone who unsubscribed is a compliance problem.
What popdock provides
--
Name the DonorPerfect flag and the Mailchimp segment or tag, and it confirms the segment exists and is static, stopping if it cannot take members directly. It reads the flagged donors with an email and skips those already in the segment. Only members of the segment's audience who are subscribed or pending are added, never anyone unsubscribed or cleaned. You see the donors to add and the counts left out, nothing is written until you confirm, and DonorPerfect is not changed.
Business outcome
---
Flagged donor groups become targetable in Mailchimp without ever adding someone who opted out.
scenario
-
Donors entered in DonorPerfect do not appear in your Mailchimp audience until someone exports and imports them. Doing it by hand risks adding people twice or, worse, re-adding someone who unsubscribed or whose address was cleaned.
What popdock provides
--
Name the Mailchimp audience and optionally a minimum lifetime giving level, and it reads DonorPerfect donors with an email and keeps only those with no member record in that audience at all. Anyone present as unsubscribed or cleaned is skipped and never re-added. You confirm the list, and can remove rows, before donors are added as pending by default so they receive a double opt-in, with subscribed used only when you confirm you have consent. Each addition is read back to confirm it.
Business outcome
---
New donors reach your Mailchimp audience with consent respected, and opted-out donors stay out.
scenario
-
After a Mailchimp appeal goes out, the question is whether it brought in gifts, but opens and clicks are in Mailchimp and gifts are in DonorPerfect. Matching recipients to donors and checking gift dates by hand is tedious and usually skipped.
What popdock provides
--
Name the campaign and an attribution window, 14 days by default, and it reads the campaign report, collects everyone who opened or clicked, and matches each email to a DonorPerfect donor or address. Gifts and pledge payments within the window after the send date are totalled, with pledge totals left out. You get a headline, a table of givers and totals split between clickers and openers. It is read-only and says clearly that this is correlation within a window, not proof the email caused the gift.
Business outcome
---
You see what giving followed each Mailchimp appeal, measured honestly, to guide your next campaign.
scenario
-
Donors with an email address on file in DonorPerfect should be hearing from you through Mailchimp, but nobody checks until a newsletter goes out light. Comparing the donor base with the audience by hand means checking each address one at a time.
What popdock provides
--
Name the Mailchimp audience and optionally a minimum lifetime giving level, and it reads DonorPerfect donors with an email and checks each against the audience, matching addresses regardless of case or spacing. Donors are sorted into not in the audience, in it but unsubscribed or cleaned, and subscribed or pending. The missing donors are listed by lifetime giving, with a note when results hit the read limit. Nothing is added or changed in either system.
Business outcome
---
You know exactly which donors are not hearing from you by email, ranked by giving, before deciding who to add.
scenario
-
Bouncing emails in Mailchimp usually mean a wrong address in DonorPerfect, but nobody connects the two until a major donor misses an important appeal. Finding which donor holds each bad address, and where it is stored, means searching record by record.
What popdock provides
--
Choose a lookback period, 30 days by default, and it reads Mailchimp bounces, grouping by email with the latest date, type and number of campaigns that bounced. Each address is matched to a DonorPerfect donor or an additional address record, showing where it is held. Hard bounces and repeated soft bounces are listed, ranked by lifetime giving, and single soft bounces are left out as temporary. It is read-only, so staff decide what to correct.
Business outcome
---
Your most valuable donors with a bad email address are corrected first, before the next appeal goes out.
scenario
-
When a donor unsubscribes in Mailchimp, staff working in DonorPerfect have no idea and may still email them directly. Carrying each unsubscribe across means matching addresses to donors and setting a flag by hand, which falls behind quickly.
What popdock provides
--
Name the DonorPerfect flag and a lookback period, 30 days by default, and it confirms the flag is active, reads recent Mailchimp unsubscribes and matches each email to a donor. Donors already flagged are skipped, and an email matching several donors is held until you pick. You see the donors to flag with the unsubscribe date, campaign and reason, and nothing is written until you confirm. No one is ever resubscribed in Mailchimp.
Business outcome
---
Staff respect every Mailchimp unsubscribe in DonorPerfect too, keeping outreach compliant and donor trust intact.
scenario
-
A donor who clicks a link in your Mailchimp appeal is showing interest your fundraisers should know about, but that signal never reaches DonorPerfect. Logging each click as a contact by hand is tedious, and running it twice clutters the history.
What popdock provides
--
Name the Mailchimp campaign and an activity code, and it confirms the code is active, finds the campaign and collects each clicker's first click date and the links clicked. Each email is matched to a DonorPerfect donor, and anyone already logged with that code since the send date is skipped, so reruns are safe. You confirm the list before one new contact is logged per donor, never overwriting an existing contact record.
Business outcome
---
Fundraisers see which donors engaged with each appeal right in DonorPerfect, ready for timely follow-up.
scenario
-
Before calling a donor about an email appeal, you need to know whether they even receive your email. Their giving is in DonorPerfect and their subscription status, opens, clicks and bounces are in Mailchimp, so getting the full picture means two systems and several screens.
What popdock provides
--
Give an email address and a lookback period, 90 days by default, and it finds the donor in DonorPerfect, including through an additional address, and lists candidates if several match. It reads their giving and open pledges, then their Mailchimp audiences, status, engagement rates, recent opens, clicks, bounces and any unsubscribe. Observations call out mismatches such as an active donor who unsubscribed or an engaged subscriber who has never given. It is read-only.
Business outcome
---
You understand a donor's giving and email engagement together before reaching out, so the conversation fits.
scenario
-
After an email series runs in Drip, the fundraising team wants to know whether recipients gave. Answering that means exporting the campaign subscribers, searching each email in DonorPerfect, pulling gift history and filtering by date by hand. It is slow, and it is easy to credit the series with gifts that were really coded to a different appeal.
What popdock provides
--
Name a Drip email series and a lookback window, and it lists the series subscribers, matches each one to a DonorPerfect donor by email, including emails stored on additional addresses, and totals the gifts made inside the window. You get a summary of how many subscribers are donors and how many gave, plus a table of givers with their gift counts, amounts and DonorPerfect campaign codes. It notes plainly that enrollment shows exposure, not cause, and keeps Drip campaign ids and DonorPerfect campaign codes apart. Nothing is changed in either system.
Business outcome
---
You see what an email series audience actually gave in DonorPerfect, with an honest note on attribution and no records touched.
scenario
-
Before calling a supporter, you want both sides of the relationship: what they have given in DonorPerfect and how they engage with your Drip emails. That means two logins, a search in each, and checking secondary addresses because DonorPerfect does not always keep the email on the main record. A major donor who quietly unsubscribed is easy to miss.
What popdock provides
--
Give an email address, and it finds the donor in DonorPerfect, checking additional addresses when the main record has no match, then reads their gifts and flags. It looks up the same email in Drip for status, lead score, lifetime value, tags and every email series they are in. The profile lays out identity, giving, flags and email engagement side by side, then calls out up to three mismatches, such as a major donor who has unsubscribed. It matches on email only, never on name, and changes nothing in DonorPerfect or Drip.
Business outcome
---
One read-only view of a supporter's giving and email engagement, with conflicts flagged before you reach out.
scenario
-
Putting a segment of donors into a Drip email series usually means exporting them from DonorPerfect by gift total and donor type, then importing into Drip. Done by hand, people already in the series get added twice, and worse, someone who unsubscribed can be pulled back into your marketing.
What popdock provides
--
Name a Drip email series, a minimum gift total and optionally a donor type, and it picks up to 50 matching DonorPerfect donors with an email. Anyone already in the series or unsubscribed in Drip is dropped, and you see who will be enrolled and why the rest were skipped, including a note that Drip creates subscribers who do not exist yet. Nothing is written until you confirm. It warns if the series is not active, never re-subscribes an unsubscribed person, and re-reads the series afterwards to report enrolled, failed and skipped counts.
Business outcome
---
The right donors join the Drip email series once, with unsubscribed people kept out and every result accounted for.
scenario
-
Donors with an email on file in DonorPerfect should hear from you in Drip, but nobody knows how many have slipped through. Checking means pulling a donor export by gift total or state and searching Drip for each address, and people who deliberately unsubscribed get confused with genuine gaps.
What popdock provides
--
Set a minimum gift total, an optional state and how many donors to check, and it reads DonorPerfect donors with an email and looks each one up in Drip. You get a table of donors missing from Drip, sorted by gift total with their organization and last contribution, plus counts of donors checked, found and missing. People who are in Drip but unsubscribed are listed separately, not as gaps, so you do not chase someone who opted out. Emails are compared ignoring case and spaces, and nothing is written to either system.
Business outcome
---
A ranked list of donors your email program is not reaching, with opt-outs kept apart and no changes made.
scenario
-
Your most engaged Drip subscribers may care about your cause but have never given. Finding them means sorting Drip by lead score, then searching DonorPerfect for each email, including secondary addresses, to see whether they are a donor at all or a donor with no gifts. It rarely gets done, so warm prospects go unasked.
What popdock provides
--
Choose a minimum lead score and how many subscribers to check, and it reads active Drip subscribers at or above that score and looks each email up in DonorPerfect, falling back to additional addresses. It returns two tables ranked by lead score: people not in DonorPerfect at all, and donors on file with no gifts, each with lifetime value and tags. Matching is by email only. It is read-only, so no donors are created and no Drip tags or series are touched.
Business outcome
---
A ranked prospect list of engaged email readers who have not given, ready for your fundraising team to work.
scenario
-
When a supporter unsubscribes in Drip, DonorPerfect still looks like they are happy to receive email, so staff send appeals by hand to people who opted out. Keeping the donor record honest means exporting unsubscribers, searching each in DonorPerfect, and setting a flag one donor at a time without doubling up.
What popdock provides
--
Name the DonorPerfect flag to use, and it reads Drip unsubscribers, matches each to a donor by email, including additional addresses, and drops donors who already carry the flag. It checks that the flag code exists, then shows you who will be flagged and how many were not found or already flagged. Nothing is written until you confirm. If one email matches several donors it skips that email rather than guessing, it never changes anything in Drip, and it re-reads each donor's flags afterwards to report what was set.
Business outcome
---
Email opt-outs from Drip show up on the right DonorPerfect donor records, with ambiguous matches left for you to resolve.
scenario
-
Donor files in DonorPerfect should show every touch, but email series run in Drip never appear in a donor's history. Logging them means exporting the series subscribers, finding each donor, and adding a contact record by hand, with no easy way to tell who was already logged last time.
What popdock provides
--
Name a Drip email series and a DonorPerfect activity code, and it matches the series subscribers to donors by email, including additional addresses. Donors who already have a contact naming this series are skipped, and the activity code is checked so you are warned if it is unknown. You see who will be logged before anything is written, and nothing happens until you confirm. Each confirmed donor gets a new dated contact noting the series, never an overwrite of an existing one, and you get logged, failed and skipped counts.
Business outcome
---
Email outreach from Drip appears in each donor's DonorPerfect history once, without overwriting existing contact records.
scenario
-
Segmenting Drip emails by how much someone has given needs the giving data from DonorPerfect. By hand that means exporting donors over a threshold, finding each one in Drip, and tagging them individually, while making sure you do not tag unsubscribed people or create subscribers who never signed up.
What popdock provides
--
Choose a Drip tag and a minimum DonorPerfect gift total, and it reads qualifying donors and sorts them into already tagged, to tag, and not in Drip. If the tag does not exist yet it tells you tagging will create it. Nothing is tagged until you confirm the groups with names, emails and gift totals. Unsubscribed subscribers are skipped and listed, donors missing from Drip are never added, and each tag is read back afterwards so the counts of tagged, skipped and failed are accurate.
Business outcome
---
Drip segments reflect real giving levels from DonorPerfect, applied only to existing, subscribed people.
scenario
-
GL codes typed on gifts drift away from the chart of accounts, and the mismatch usually surfaces only at month end when the books will not reconcile. Checking means listing every code used on gifts in DonorPerfect and searching for each one in NetSuite.
What popdock provides
--
Give a date range, and it reads the gifts from DonorPerfect, groups them by GL code with a gift count and total, and counts the gifts with no code. Each code is then looked up in the NetSuite chart of accounts, by account number first and by name if needed, with name-only matches flagged as weak. The result lists missing codes first with their gift totals. It is read-only, and neither DonorPerfect nor NetSuite is changed.
Business outcome
---
Gift GL codes with no NetSuite account are caught during the month, with their amounts, instead of at month end.
scenario
-
Campaign results sit in DonorPerfect and in NetSuite and are compared by eye, so campaign codes with no matching NetSuite campaign, or the other way round, are missed. Titles rarely match exactly, which makes manual matching slow.
What popdock provides
--
Name a campaign code, or leave it blank for all, and it reads the campaign codes from DonorPerfect, totals the gifts for each over your date range, and looks for the campaign in NetSuite by description and then by code. The table shows gift count and total next to NetSuite revenue, total cost and profit, with a Match or Missing status. Close names are shown as suggestions only, never as matches, and codes with no NetSuite campaign, and NetSuite campaigns with no gifts, are listed. It is read-only on both systems.
Business outcome
---
Campaign giving and NetSuite campaign revenue are compared in one table, with unmatched codes and campaigns listed and nothing changed.
scenario
-
Preparing for a donor conversation means opening DonorPerfect for gifts and pledges and NetSuite for invoices and payments, then guessing whether an open pledge and an open invoice are the same obligation.
What popdock provides
--
Give a donor ID, and optionally how many recent gifts to show, and it reads the donor's giving summary and recent gifts from DonorPerfect, noting open pledges. It then finds the matching NetSuite customer by email and reads open invoices, balance and recent payments. The profile ends with one line on whether pledges and invoices look like the same obligation or separate ones. If there is not exactly one matching customer, it reports only the DonorPerfect side. It is read-only, and neither system is changed.
Business outcome
---
Leaders go into a donor conversation with giving, pledges and receivables in one profile, with no data changed in either system.
scenario
-
Large donors are recorded in DonorPerfect, but nothing forces a matching customer to exist in NetSuite. Someone has to pull donors above a giving level and look each one up in the accounting system, so a gap usually surfaces only when billing is needed.
What popdock provides
--
Give a minimum lifetime giving amount, and optionally how many donors to check, and it lists DonorPerfect donors above that level. It then looks each one up in NetSuite by email and falls back to name, and donors with no email are checked by name only and flagged as weak. Results come back largest giver first with counts of matched and missing donors. Nothing is changed in either system, and it tells you when the donor limit was reached so the list may be incomplete.
Business outcome
---
Major donors without a NetSuite customer are named, largest first, before billing is needed, with no records touched.
scenario
-
Matching a donor to an accounting customer means opening both systems and comparing names, emails and phone numbers by hand. When the only link is a name, it is easy to settle on the wrong record.
What popdock provides
--
Give a donor ID, and it reads the donor with their email, phone and address from DonorPerfect, then looks for the NetSuite customer by email and falls back to name. A table compares name, email and phone field by field, with the customer ID and balance, and states the confidence as strong for email, weak for name only, or none. If several customers match it lists them and does not pick one. Emails are compared ignoring case and phones by digits. Nothing is changed in either system.
Business outcome
---
Each donor is tied to the right NetSuite customer, or flagged as weak or missing, with the field differences visible.
scenario
-
A gift recorded in DonorPerfect should show up in NetSuite as a payment or deposit on the same donor, but finance compares the two lists by hand. Missing receipts, amounts that differ and pledges that are not cash all get mixed together, so mismatches go unnoticed until an audit.
What popdock provides
--
Give a donor ID and a date range and PopdockAI reads that donor's gifts in DonorPerfect and the donor email. It finds the one NetSuite customer with that email, and stops if there is not exactly one. It then reads the customer payments and deposits for the period and pairs each gift with a receipt of the same amount within 5 days. Matched pairs, gifts with no receipt, receipts with no gift and the total on each side are listed, and pledges are skipped because they are not cash. Neither system is changed.
Business outcome
---
Finance sees which gifts have no NetSuite receipt and the exact difference in totals, without comparing two exports by eye.
No items found.
Ready to unlock your data?
Start building tools that turn your business systems into AI superpowers
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.