everydayhero integration

Transcript

1. everydayhero integration Proposed Solution
2. Architecture
3. Core data sync • Sync ◦ Fundraisers ◦ Donors ◦ Gifts • Fully automated and transparent • Default frequency hourly
4. Constituents • Fundraisers and Donors in everdayhero create Constituents in RE NXT identified with Constituent Codes • Relationships created automatically • Fixed field mapping for essential constituent fields • Constituent Codes configurable • everydayhero ID destination configurable
5. Gifts • Donations in everdayhero create Gifts in RE NXT • Fundraiser can be automatically soft credited • Gift categorization can be automatically populated ◦ Appeal ◦ Fund ◦ Campaign ◦ Package • Default values can be set for these four categories • Alternatively these can be populated based on the everdayhero campaign set for that donation.
6. De dupe • Simple deduplication logic is applied before importing constituents • Existing records will be updated • Otherwise a new constituent record is created • A positive match is determined by ◦ Full name (fuzzy) ◦ Primary email address
7. User Interface • Self service user interface • Setup authentication to both applications • Configuration options ◦ Gift categorisation defaults (appeal, campaign, fund, package) ◦ Gift categorisation per campaign settings (appeal, campaign, fund, package) ◦ Constituent code settings (fundraiser, donor) ◦ Everydayhero ID field destination • Transaction History ◦ History of transactions processed including status ◦ Filtered to exceptions by default • Separate web app styled using Sky UX
8. Questions - THANK you! 1. Are there any other features you would consider essential? 2. Are there any other features you would like to see? 3. Does this represent a solution you would consider switching to over your current processes? 4. Any other feedback or suggestions?