Identity and communication
Individual or organization, household, preferred name, channel, consent, recognition preference, anonymity, and do-not-contact status.
Accurate acknowledgement and communication without unsafe list copying.Give development teams a usable donor record from first gift through finance handoff, acknowledgement, promise, follow-up, renewal, or respectful lapse management.
The populated Jodoo dashboard shows gift types, restrictions, reconciliation, acknowledgement status, constituent context, and the relationship queue behind each signal.
A donation total is not a relationship history. Preserve the context that determines what the organization should do next.
Individual or organization, household, preferred name, channel, consent, recognition preference, anonymity, and do-not-contact status.
Accurate acknowledgement and communication without unsafe list copying.Gift or pledge reference, date, amount, type, campaign or appeal, fund, restriction, matching context, and finance reconciliation.
The right stewardship action without claiming the operational record is the accounting ledger.Receipt reference, acknowledgement method, owner, due date, status, personal promise, supporting note, and exception reason.
Visible service after the transaction instead of gratitude by memory.Segment, relationship owner, interaction history, next action, due date, interests, program connection, lapse signal, and outcome.
Relevant engagement rather than repetitive mass follow-up.Each stage should add useful context and complete the promised follow-up.
Connect the transaction reference to the constituent, fund, restriction, and relationship owner.
The record can be reconciled without storing payment credentials.Choose the correct method, owner, message context, and due date.
Overdue and exception cases appear in a dedicated queue.Complete receipts, requested information, introductions, or program updates.
The outcome is recorded against the original promise.Schedule the next relevant interaction using interests, history, consent, and segment context.
Managers see open work without reading private notes.Record the relationship outcome and the reason behind future follow-up or no further contact.
The next cycle starts from evidence rather than assumption.Exception queues help staff focus on the few records where a standard workflow is unsafe or incomplete.
The intended use may not match an existing fund or program.
The organization risks making the donor feel unseen.
The commitment and expected cash timing no longer match.
Giving and consent history may be split across identities.
Giving or engagement fell outside the expected pattern.
When the program changes, update the operating record and the action around it.
Add a free-text value and explain it in email.
Add controlled fund and restriction choices, a review rule, a finance view, and acknowledgement context.Copy the tracker and maintain a separate follow-up list.
Add the segment, cadence, owner queue, reminders, and dashboard filter in the same relationship model.Filter rows and send manual reminders.
Route aging records to the relationship owner and manager with drill-down to the gift and donor.Jodoo coordinates the people and work around a donation. Confirm required payment, accounting, and fundraising capabilities in the systems that provide them.
Donor record, gift reference, restriction, acknowledgement, promise, stewardship, owner, and next action
Card or ACH processing, settlement, refunds, chargebacks, and PCI controls
Pass transaction identifiers and status—not sensitive payment data.Finance handoff and reconciliation status
General ledger, fund accounting, tax treatment, and audited financial reporting
Record the ledger reference and unresolved question while finance remains authoritative.Segments, relationship actions, and consent-aware follow-up
Mass-email deliverability, peer-to-peer fundraising, wealth screening, and campaign execution
Sync permitted outcomes and engagement signals where they improve stewardship.Focus on the operational record and its boundaries.
Track constituent identity, household or organization, consent, gifts and pledges, funds and restrictions, finance references, acknowledgements, promises, interactions, segments, relationship owner, next action, due dates, lapse signals, and outcomes.
This application is designed to manage donor and stewardship operations, not to claim native payment processing. Connect trusted payment and accounting systems using stable transaction references and statuses.
Donor management focuses on giving, acknowledgement, pledges, stewardship, renewal, and fundraising context. A nonprofit CRM can cover a broader constituent relationship across volunteer, member, partner, program, and advocacy roles.
Yes. A trained administrator can adjust fields, choices, segments, forms, review paths, role views, reminders, permissions, and dashboards as the organization’s stewardship model evolves.
Connect the finance reference, acknowledgement, stewardship promise, relationship owner, and due date in one operational record.