Developer Programs

Learn

Docs
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.

Developer Resources

API by Reference > Customer Relationship Management > Customer Relationship Management Prospect Modification > Developer Resources

Details

SoapActionhttp://jackhenry.com/ws/CRMProspMod
Input NameCRMProspMod
Output NameCRMProspModResponse
Input Namespacehttp://jackhenry.com/jxchange/TPG/2008
Group NameCustomer
ContainerTPG_CustomerMaster.xsd

XML Examples

CRMProspMod Request

XML
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
  xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <SOAP-ENV:Header>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
    <CRMProspMod xmlns="http://jackhenry.com/jxchange/TPG/2008">
      <MsgRqHdr>
        <jXchangeHdr>
          <JxVer></JxVer>
          <AuditUsrId></AuditUsrId>
          <AuditWsId></AuditWsId>
          <AuthenUsrId></AuthenUsrId>
          <ConsumerName></ConsumerName>
          <ConsumerProd></ConsumerProd>
          <Ver_1/>
          <jXLogTrackingId>122222222</jXLogTrackingId>
          <Ver_2/>
          <InstRtId>011001276</InstRtId>
          <InstEnv>TEST</InstEnv>
          <Ver_3/>
          <BusCorrelId></BusCorrelId>
          <Ver_4/>
          <WorkflowCorrelId></WorkflowCorrelId>
          <Ver_5/>
          <ValidConsmName>{Insert}</ValidConsmName>
          <ValidConsmProd>{Insert}</ValidConsmProd>
          <Ver_6/>
        </jXchangeHdr>
        <Ver_1/>
        <Ver_2/>
        <Ver_3/>
      </MsgRqHdr>
      <ErrOvrRdInfoArray>
        <ErrOvrRd>
          <ErrCode></ErrCode>
          <Ver_1/>
        </ErrOvrRd>
      </ErrOvrRdInfoArray>
      <CRMProspId>222222224</CRMProspId>
      <CRMProspInfoRec>
        <CustType></CustType>
        <TaxId></TaxId>
        <PersonName>
          <ComName></ComName>
          <FirstName></FirstName>
          <MiddleName></MiddleName>
          <LastName></LastName>
          <x_PersonName>
            <TitlePrefix></TitlePrefix>
            <NameSuffix></NameSuffix>
            <LegalName></LegalName>
            <SalName></SalName>
            <Ver_1/>
            <AbbName></AbbName>
            <Ver_2/>
          </x_PersonName>
          <SvcPrvdInfo/>
          <Ver_1/>
        </PersonName>
        <Addr>
          <FreeFormAddrArray>
            <AddrLineInfo>
              <AddrLine></AddrLine>
              <Ver_1/>
            </AddrLineInfo>
          </FreeFormAddrArray>
          <StreetAddr1></StreetAddr1>
          <StreetAddr2></StreetAddr2>
          <City></City>
          <StateProv></StateProv>
          <StateCode></StateCode>
          <PostalCode></PostalCode>
          <DlvryPt></DlvryPt>
          <County></County>
          <Cntry></Cntry>
          <CntryType></CntryType>
          <BusAddr></BusAddr>
          <FornAddr></FornAddr>
          <InvAddr></InvAddr>
          <SvcPrvdInfo/>
          <Ver_1/>
          <StreetAddr3></StreetAddr3>
          <Ver_2/>
        </Addr>
        <BirthDt>1951-03-22</BirthDt>
        <EmplName></EmplName>
        <CRMOffArray>
          <CRMOffRec>
            <CRMOffCodeText></CRMOffCodeText>
            <CRMOffCode></CRMOffCode>
            <CRMOffDesc></CRMOffDesc>
            <Ver_1/>
          </CRMOffRec>
        </CRMOffArray>
        <PhoneArray>
          <PhoneInfo>
            <PhoneNum></PhoneNum>
            <PhoneType></PhoneType>
            <PhoneTime></PhoneTime>
            <PhoneExt></PhoneExt>
            <Ver_1/>
            <ConStartTime>21:49:23.613Z</ConStartTime>
            <ConEndTime>21:49:23.613Z</ConEndTime>
            <MobPhoneInfo>
              <MobPrvdCode></MobPrvdCode>
              <MobPrvdCodeDesc></MobPrvdCodeDesc>
              <MobPrvdDom></MobPrvdDom>
              <MobBB></MobBB>
              <MobSendTestText></MobSendTestText>
              <Ver_1/>
            </MobPhoneInfo>
            <Ver_2/>
            <Ver_3/>
            <PhoneNumDsp></PhoneNumDsp>
            <Ver_4/>
          </PhoneInfo>
        </PhoneArray>
        <EmailArray>
          <EmailInfo>
            <EmailAddr></EmailAddr>
            <EmailType></EmailType>
            <Ver_1/>
          </EmailInfo>
        </EmailArray>
        <Custom></Custom>
        <Ver_1/>
        <CRMProspPfArray>
          <UserDefInfo>
            <UserDefTxt></UserDefTxt>
            <UserDefCode></UserDefCode>
            <UserDefDesc></UserDefDesc>
            <UserDefDt>2019-03-21</UserDefDt>
            <UserDefInfo1></UserDefInfo1>
            <UserDefInfo2></UserDefInfo2>
            <UserDefInfo3></UserDefInfo3>
            <Ver_1/>
          </UserDefInfo>
        </CRMProspPfArray>
        <Ver_2/>
        <CRMOptInfoArray>
          <CRMOptInfo>
            <CRMOptCode></CRMOptCode>
            <CRMOptDesc></CRMOptDesc>
            <Ver_1/>
          </CRMOptInfo>
        </CRMOptInfoArray>
        <Ver_3/>
      </CRMProspInfoRec>
      <MrgTgt>
        <CRMTgtProspId></CRMTgtProspId>
        <TaxId></TaxId>
        <CustId></CustId>
        <CRMRelCode></CRMRelCode>
        <Custom></Custom>
        <Ver_1/>
      </MrgTgt>
      <ActIntentKey>Upd</ActIntentKey>
      <Dlt></Dlt>
      <Custom></Custom>
      <Ver_1/>
    </CRMProspMod>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope> 

CRMProspMod FAQ

Question: I have created a few prospects in test with CRMProspAdd and manually converted them to a customer CRMProspMod based on instructions below but am not able to view them in SilverLake with CustSrch by TaxId.

Answer The Synapsys system doesn’t add client records to the core processing system (SilverLake, Episys, etc.). The Synapsys system allows for the addition of potential client records (prospects) to the Synapsys system. The core processing system has no concept of these potential client records (prospects).

During the nightly DBLoad process, Synapsys receives existing client records from the core processing system. Synapsys attempts to match these existing client records from core against the potential client records (prospects) in Synapsys by SSN/TaxId. If a match is found, the records are merged into an existing client record in Synapsys, resulting in the deletion of the potential client records (prospects) from Synapsys.

I should add that the prospect merge process in Synapsys requires one of the following for a Synapsys prospect record to be merged to:

  • A client record from the core processing system existing in the Synapsys system
  • A second existing prospect record in Synapsys

The customer can manually identify Synapsys prospect to client conversion opportunities and merge those records through the Synapsys Desktop application (prospect profile -> merge -> provide client info) and/or Synapsys jXchange Services (CRMProspMod -> MrgTgt -> provide client info). The example below shows how to merge a prospect to a client using the Synapsys jXchange Services CRMProspMod service.

Prospect Info: SSN/CRMProspId = 111222333 Name = Bobby Smith

Client Info: SSN/TaxId = 123456789 Portfolio/CustId = 98765 RelCode1/CRMRelCode = 1 Name = Robert Smith

XML
 <CRMProspMod xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns='http://jackhenry.com/jxchange/TPG/2008'>
  <MsgRqHdr>
    <jXchangeHdr>
      <InstRtId>[ABANumber]</InstRtId>
      <ValidConsmProd>[Product]</ValidConsmProd>
    </jXchangeHdr>
  </MsgRqHdr>
  <ErrOvrRdInfoArray />
  <CRMProspId>111222333</CRMProspId>
  <CRMProspInfoRec>
    [Ignored when MrgTgt values provided, suggest not providing]
  </CRMProspInfoRec>
  <MrgTgt>
    <CRMTgtProspId>[Prospect target SSN, do not provide if merging to a client record]</CRMTgtProspId>
    <TaxId>123456789</TaxId>
    <CustId>98765</CustId>
    <CRMRelCode>1</CRMRelCode>
  </MrgTgt>
  <ActIntentKey>[Any non-blank value, “test”]</ActIntentKey>
  <Dlt>[Ignored when MrgTgt values provided, suggest not providing]</Dlt>
  <Custom xsi:nil='true' />
</CRMProspMod>


Have a Question?

Did this page help you?

Last updated Wed Mar 4 2026