addInteraction

Louise Jones phones a call center and requests marketing information. The customer service representative (CSR) records the interaction and adds the request to the database.

Jenny Smith, who is not a Party in the database, calls on behalf of her husband, John Smith, who is a Party in the database. The CSR records the interaction to note that Jenny Smith called on behalf of her husband and that she is the source of the interaction.

John Smith called to change his address on his life insurance policy. In this example, the regarding detail would include John Smith's life insurance policy number. The CSR records the change of address by selecting Customer service request under Category and Minor change under Type.

Each interaction record includes a date that records when the interaction occurred, the method of the communication (such as fax, telephone, or e-mail), the reason and the details for the communication and, in particular, the source of the interaction. The source of an interaction is often an individual (Party), but interactions can also be recorded when the source is another system, a system user, an agent, or some other third party.

The interaction can also be about a contract, a party, an individual who is not a party in InfoSphere MDM, or another entity such as a grouping. If the interaction is about an individual that is not a Party in the database, the individual can be recorded as a name or other identifier such as a user ID or an account representative number.

Interaction types let a company predefine how the information for an interaction is categorized and typed.

When using this transaction as a coarse-grained transaction, the following simple transaction may also apply:

• addInteractionRelationship

Must either have a valid PartyId for the InteractionParty or a valid EntityName and InstancePK.

• InteractionPointType
• RecordedDate
• InteractionShortDescription
• InteractionParty
• InteractionDate

If EntityName and InstancePK are not provided or are blank, the InteractionParty must provide a valid PartyId value.

If a valid EntityName and a valid InstancePK are provided, the InteractionParty value is still required, but the input can be freeform, such as a name, relationship description, or a PartyId. If EntityName and InstancePK values are provided, the EntityName may only be of type Contact or Contract. If the EntityName is a Contact, the InstancePK returns records for this case, as well as the case where the InteractionParty = InstancePK, as supplied to the transaction.

<TCRMTxObject> TCRMInteractionBObj

<TCRMObject> TCRMInteractionBObj

with associations

with associations