Supporter contact and transactional data flows to and from systems

Supporter data changes. Existing records are altered, and new records created. Understandably, the vast majority of these changes tend to be entered only once into one specific system. Copy-and-pasting these changes over into all other remaining systems manually would be a full-time job in itself, difficult to audit, susceptible to human error.

Automatic integrations offer peace of mind by:

• Running overnight (every night), polling systems for recently added or altered data.
• Bringing this data back to one centralised hub where new data can be compared like-for-like with old, changes audited and where one definitive up-to-date record can be compiled per supporter.
• Delivering updates, where appropriate, back to the transactional systems, as well as the front end CRM and Single Sign On master databases. Different systems have particular quirks: inbound integration processes that translated data into one universal schema can be reversed to bring updates back to the source systems in their native schema.

Contact data kept synchronised across the Supporter Relations infrastructure guarantees the supporter is recognised equally on and by each system.