- Addresses and other contact information are not validated at the point of capture.
- The formats of captured names and addresses are not normalized.
Many organizations have taken a first step towards improving address capture at these customer touchpoints by implementing AutoComplete or TypeAhead solutions, such as our GlobalTypeAheadUSCAN service, where the customer can start typing their address and a list of matching addresses pops-up for the customer to select.
Although this solution may be convenient for the customer, it does not solve all the addressing problems.
Addresses presented by typeahead service typically include building addresses, both with and without suite, or apartment numbers. This means a customer may select their correct building address but may have overlooked that they selected a non-deliverable address by not including their apartment number.
- The GlobalTypeAheadUSCAN (or GlobalTypeAheadInternational) services provide candidates as the user types. This guides the user for a better choice and reduce the chance that the address has been mistyped.
- The ValidateMailingAddressRecommendUSCAN or ValidateMailingAddressRecommend (for global usage) services standardize and verify the address against trusted third-party source data (such as postal or geolocation data if you want) and returns a validated, postal deliverable or highly accurate geo-locatable address.
If the candidate address does not validate postal delivery or it does not meet geolocation accuracy thresholds, a list of verified address suggestions is displayed for the user to select.
To choose these verified address changes, ValidateMailingAddressRecommend uses both phonetic and non-phonetic heuristics to determine the accuracy and relevance of address suggestions.
It takes advantage of additional data sources beyond the standard postal mail data (used by standard address validation services, such as ValidateMailingAddress) to find addresses that are not supported by the postal delivery services, such as the USPS. This permits you to understand that an address may not be deliverable by the USPS but can be deliverable by another delivery services such as DHL, FedEx or UPS.
Resource URL
https://OnDemandServer/soap/ValidateMailingAddressRecommendFor a list of Spectrum OnDemand servers, see Connecting to Spectrum OnDemand Servers.
Example
This shows a SOAP request:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:val="http://www.pb.com/spectrum/services/ValidateMailingAddressRecommend">
<soapenv:Header/>
<soapenv:Body>
<val:ValidateMailingAddressRecommendRequest>
<val:Input>
<val:Row>
<!--Optional:-->
<val:Name></val:Name>
<!--Optional:-->
<val:FirmName></val:FirmName>
<!--Optional:-->
<val:AddressLine1>6913 Antrim Rd</val:AddressLine1>
<!--Optional:-->
<val:AddressLine2></val:AddressLine2>
<!--Optional:-->
<val:City>Edina</val:City>
<!--Optional:-->
<val:StateProvince>MN</val:StateProvince>
<!--Optional:-->
<val:PostalCode>55439</val:PostalCode>
<!--Optional:-->
<val:Country>USA</val:Country>
<!--Optional:-->
<val:RecordKey></val:RecordKey>
<!--Optional:-->
<val:InstanceKey></val:InstanceKey>
<!--Optional:-->
<val:user_fields>
<val:user_field>
<val:name></val:name>
<val:value></val:value>
</val:user_field>
</val:user_fields>
</val:Row>
</val:Input>
</val:ValidateMailingAddressRecommendRequest>
</soapenv:Body>
</soapenv:Envelope>
This would be the response:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:ValidateMailingAddressRecommendResponse
xmlns:ns3="http://spectrum.pb.com/"
xmlns:ns2="http://www.pb.com/spectrum/services/ValidateMailingAddressRecommend">
<ns2:Output>
<ns2:Row>
<ns2:Name></ns2:Name>
<ns2:AddressLine1>6913 Antrim Rd</ns2:AddressLine1>
<ns2:City>Edina</ns2:City>
<ns2:StateProvince>MN</ns2:StateProvince>
<ns2:PostalCode>55439-1707</ns2:PostalCode>
<ns2:Country>United States of America</ns2:Country>
<ns2:LocationCode>AP05</ns2:LocationCode>
<ns2:MatchCode>S80</ns2:MatchCode>
<ns2:CMRA>N</ns2:CMRA>
<ns2:DPV>Y</ns2:DPV>
<ns2:DPVFootnote>AABB</ns2:DPVFootnote>
<ns2:DPVNoStat>N</ns2:DPVNoStat>
<ns2:DPVVacant>N</ns2:DPVVacant>
<ns2:USLACS.ReturnCode></ns2:USLACS.ReturnCode>
<ns2:RDI>R</ns2:RDI>
<ns2:SuiteLinkReturnCode></ns2:SuiteLinkReturnCode>
<ns2:Message>Deliverable Address</ns2:Message>
<ns2:USCountyName>Hennepin</ns2:USCountyName>
<ns2:HouseNumber>6913</ns2:HouseNumber>
<ns2:StreetName>Antrim</ns2:StreetName>
<ns2:ApartmentNumber></ns2:ApartmentNumber>
<ns2:POBox></ns2:POBox>
<ns2:StreetSuffix>Rd</ns2:StreetSuffix>
<ns2:RecordKey></ns2:RecordKey>
<ns2:ProcessedBy>USAH</ns2:ProcessedBy>
<ns2:ChangeScore>100</ns2:ChangeScore>
<ns2:AddressQuality>V5</ns2:AddressQuality>
<ns2:Country.ISO>US</ns2:Country.ISO>
<ns2:Country.UPU>USA</ns2:Country.UPU>
<ns2:user_fields>
<ns2:user_field>
<ns2:name></ns2:name>
<ns2:value></ns2:value>
</ns2:user_field>
</ns2:user_fields>
</ns2:Row>
</ns2:Output>
</ns2:ValidateMailingAddressRecommendResponse>
</soap:Body>
</soap:Envelope>