01
Connect sources
Bring Donorbox, LaunchGood, Stripe, Fundwise, Givebutter, webhook, CSV, Zapier, CRM, and commerce data into one donor operations layer.
Operating loop
One workflow, not a drawer of unrelated tools.
Your donation platform should keep doing checkout. Treply sits above it so every gift, reply, receipt, recurring lapse, Zakat warning, and board report connects back to the same donor.
02
Know donors
Normalize gifts into a canonical donor profile with recurring status, duplicate cleanup, household rollups, country hints, and Hijri-aware context.
03
Engage supporters
Use guided campaign launch, templates, surveys, automations, Donor Agent, SMS, MMS, and WhatsApp to reach the right supporter with the right ask.
04
Operate and report
Review receipt failures, delivery health, attribution, analytics, board reports, billing, and developer workflows before the next send goes out.
Console map
The app is organized around nonprofit jobs.
The console navigation mirrors the same operating loop, so teams learn where each feature belongs before they click into it.
Today
The triage lane for messages, failed deliveries, and anything a human should review before the next campaign.
DashboardInboxNeeds Review
Engage
The outbound lane for campaigns and follow-ups across SMS, MMS, WhatsApp, automations, surveys, and AI-assisted replies.
CampaignsGuided LaunchTemplatesAutomationsDonor AgentSurveys
Donors
The donor intelligence lane: contacts, groups, donor profiles, recurring givers, duplicates, opt-outs, and donation widgets.
Donor ProfilesContactsGroupsRecurring DonorsDuplicate DonorsClean Contacts
Operate
The operating layer for donation sources, receipts, board reporting, delivery health, analytics, integrations, and developers.
Donation SourcesReceipts LedgerBoard ReportsDelivery HealthAnalyticsIntegrations
Capability index
The same features, grouped by the work they unlock.
Nothing disappears. SMS, MMS, automations, reports, analytics, CRM, commerce, WhatsApp, and AI features are tied back to the donor operations system they support.
Connect Sources
Know Donors
Engage
Operate
First run
Onboarding teaches the next useful job.
New teams see contextual cards for connecting a donation source, cleaning donors, launching a campaign, reviewing receipt failures, and previewing a board report. No heavy tour. Just the next operational move.
Connect a source
Clean donors
Check Zakat warnings
Review receipts
Preview board report
Practical guidance
How donor operations connect your fundraising work
A campaign begins before the message is written and continues after the gift arrives. The team needs usable contact records, clear preferences, an appropriate follow-up, and a way to explain what happened. That is the connection between messaging and donor operations.
What to review before you start
Evaluate the workflow end to end using a small example. Follow a source record into a donor profile, review the planned message, and check how the result would appear in reporting. Confirm early-access features and source coverage before committing to an implementation plan.
- Map the source, donor record, message, reply, and reporting steps.
- Choose who reviews exceptions at each handoff.
- Verify the features required for your first workflow in a demo.
Common questions
Does Treply replace our payment processor?
The donor operations workflow sits alongside donation sources. Review payment processing and integration responsibilities for your setup with the team.
Can we start with one workflow?
Use the evaluation to define a focused first workflow and the features it requires. That makes it easier to check fit before planning a broader rollout.