- The companies both use the same data provider
- The companies use a different data provider
In the second instance, this is not possible since the identifiers are specific to the data provider. In order to exchange data directly, the companies would have to exchange name and address information. This suffers from several drawbacks, the most important being the possible breach of legal restrictions imposed by the data providers to protect their Intellectual property. Other drawbacks include the necessity to data match each and every call that is exchanged in order to associate the call with the correct person in the target system.
Fusion Integration offer a service that is composed of two key components:
Data Matching
Fusion Integration receive data feeds direct from Binleys and from Dendrite. We have created a carefully customised matching process specifically for these two data sets and maintain a bridging database between them. Our bridging database contains matched pairs of identifiers (keys), one from each data set.Call Bridging
Fusion Integration supplies an Inbox and Outbox FTP location to each client that wishes to share call data. Each client posts and receives files containing keys appropriate to their data supplier. The Fusion Call Sharing Server acts as middleware and processes incoming files by substituting Binleys keys for Pharbase keys (or vice versa), applying any data transformation rules, and posting the resulting files to the appropriate outbox.Any calls containing unmatched keys are held until a match is available as a result of new data in the bridging database. If no match is available after a client-determined period of time, the call is deleted.
This process is shown graphically below:
