Too many times we rely on the back end batch process to scrub and cleanse our address data. Experienced data processors would say the batch process has been around forever, so why the change in attitude. With today’s advanced batch engines, the coding rates are at an extremely high percentage, but the postal problems of Undeliverable As Addressed (UAA) still persists.

In order to combat the UAA problem, advancements in real-time validation, correction and confirmation is a must. Real-time validation is not technically complicated; the complication comes in the form of getting an approved business policy and application updated.

Real-time validation is not technically complicated; the complication comes in the form of getting an approved business policy and application updated.

With front end address validation, your call center agent can ask questions to ensure an address isn’t missing an apartment number or has the correct firm name. These items can not always be found in a batch process, and would require some extensive research and contact with the user.

Today’s software products can be implemented tightly through application program calls or loosely through local workstation interfaces. So, how can we get our IT or department programmers to perform the work. We should first start with the business ROI.

  1. Keystrokes saved. For every keystroke reduced, can be calculated as time savings for each call center agent over a time period.
  2. Eliminate 1% bad addresses. If this process can eliminate just 1% of your bad addresses, it can really mean something. So you think 1% sounds small, but 1% of many millions can really add up.

Just what are your thoughts on getting address validation on the front end of your business? If you think you have an issue and can’t justify the ROI, consider a Mailing Assessment where G1 staff can help you research your issues.