Blog

Updating your solutions for Legacy API Retirement in Summer ‘22

What Legacy APIs are Salesforce retiring?

As part of their Summer ‘22 Release, Salesforce has announced the retirement of a number of legacy APIs.

Versions 7.0 through 20.0 of the Salesforce Platform SOAP, REST, and Bulk APIs will be deprecated and no longer supported as of the Summer ’22 release.

This means that these legacy APIs, and third-party integrations that rely on them, will cease to function after the release.

When are the Legacy APIs being retired?

Salesforce announced that June 10 and 11 2022 is the final release weekend when all remaining Salesforce instances are upgraded if they haven’t been already.

Legacy API Retirements and ProvenWorks solutions

To ensure that you do not encounter any issues with AddressTools, SimpleImport, IndustryComplete or PhoneTools, we recommend ensuring that your current version is or is later than the versions listed in this post. If you need advice on how to upgrade an AppExchange managed package, please see the resources linked at the end.

We have listed the version of each tool, including a link to its latest AppExchange listing, that you must be on in order to be using supported APIs.

AddressTools Premium:

7.75+

AddressTools Free:

6.20+

Address Verification Flow Component:

1.72+

SimpleImport Free:

2.47+

SimpleImport Premium:

2.57+

ManagedImport:

1.15+

PhoneTools:

2.0+

IndustryComplete:

2.16+

Resources

Prepare for Legacy API Retirement in Summer ’22 – Salesforce Developers’ Blog

Salesforce Platform API Versions 21.0 through 30.0 Retirement – Salesforce Help

Salesforce Summer ‘22 Release — Here’s What to Expect – Salesforce News

Salesforce Summer ’22 Release Notes

Don’t Miss These Key Dates: Summer ’22 Sandbox Preview

How to upgrade your ProvenWorks solution

We wrote a handy four-step guide to walk you through how to upgrade your AppExchange solutions.

Contact us

If you’re worried about how the API retirements might affect you and your ProvenWorks solution, please don’t hesitate to contact us.

How to automate Address Verification via a Record-Triggered Flow

Introduction

Salesforce Flows give admins a chance to implement advanced processes into their org with clicks, not code. Here at ProvenWorks, we want to empower admins to do more, so building on the capabilities of Salesforce Flows, AddressTools Premium allows you to configure an automated address verification process with no coding knowledge.

This article covers configuring a Salesforce Record-Triggered Flow to queue an address verification process on a record that invoked the flow. This produces a verified address within moments of the flow being triggered. It is dependant on Salesforce Future Methods so be aware that there is expected to be a slight lag between the record being inserted/updated and the address being verified.

Pre-requisites

The component used in the flow comes as part of the AddressTools Premium package. An additional purchase of address verification credits will be required.

If you’re new to AddressTools Premium, please contact info@provenworks.com with your Org ID to have the team enable your org for batch address verification. Without doing this your org will be unable to verify addresses.

With AddressTools Premium installed, the following configurations will require:

  • An address block to be configured in the AddressTools Administration page,
  • An address status field for the address block,
  • Verification enabled for the org and specifically the address block.

If you need assistance on any of the pre-requisites, please refer to the AddressTools Premium Installation Walkthrough before getting started.

Create a Record-Triggered Flow to verify addresses in Accounts

The following example is going to follow verifying the billing address block on accounts using a Record-Trigger Flow on insert and update. This process can be adapted to any object and address block of your choice assuming it’s configured with AddressTools.

  • Go to Salesforce Setup | Flow.
  • Select New Flow.
  • Choose Record-Triggered Flow.
  • Search and select the object that you are configuring the process for.
  • Set Trigger the Flow When to A record is created or updated.
  • Select Done.

Configure Start

  • Object Account
  • Set entry conditions.
  • Configure Trigger A record is created or updated.
  • Condition requirements All Conditions Are Met (AND).
  • We’ll choose the address status field configured with the address block. For this scenario: pw_ccpro__BillingAddressStatus__c Equals Not checked.
  • When to Run the Flow for Updated Records Every time a record is updated and meets the condition requirements.
  • Optimize the Flow For Actions and Related Records.
  • Done.

Configuring an Apex Action

  • Click the plus sign to add an element
  • Add Action| Filter By Type | Apex Action
  • Action: Premise-Level Address Verification
  • Label Verification of addresses
  • API Name Verification of addresses
  • Set Input Values
  • Country-Field API Name: BillingCountry (This value is the API name of the country field configured in the address block. For example, the Mailing Country on Contact would be MailingCountry).
  • ID of record to validate: {!$Record.Id} (This takes the record ID from the record that invoked the flow).
  • Done.

Save the Flow

  • Select Save in the top right.
  • Provide a Flow Label to help you identify the flow in the future.
  • The Flow API Name will autofill.
  • Click Save.
  • Activate the flow.

Testing the Flow

With the flow created and activated, we can now test it in the org.

Note: before testing the flow, we recommend ensuring you have the Batch Verification Alerts Email field populated in AddressTools Administration with your email address.

  • Go to a test account in the Org.
  • Edit the billing address.
  • Save the record.

This will invoke the flow and it may take a few seconds to return the status. If the address status field has not updated by the time the page refreshed, give it a moment and refresh the page.

Prepare your address data for the Custom Address Field Type in Salesforce

If you, like many of us, have been eagerly awaiting the custom address field type in Salesforce (it’s only been like 10 years or so?), then you’ll be pleased to hear that Salesforce has announced it is in Beta from the Summer ‘22 release! 

At ProvenWorks we’ve been fortunate enough to participate in the closed pilot since day one so we have been able to follow its progress. We’re now excited to be able to share with you some information so that you can be prepared for its release.

Isn’t the custom address field just like the standard address field type?

Sort of – however, be prepared that State & Country picklists are enforced for all new custom address fields in Salesforce, regardless of your existing org settings. This is largely why we’re writing this article.

State & Country picklists provide a neat solution for ensuring clean data at the point of entry, but admittedly, we’ll be the first people to warn you about the integration issues, customization headaches, and maintenance anxiety you may face when using Salesforce State & Country picklists.

…Nevertheless we are address experts in Salesforce so we’re going to embrace State & Country picklists head on and let you know how to prepare if you wish to migrate from custom text fields to the new address field type.

Important: If you’re steering clear of State & Country picklists and you wish to remain using text fields then keep doing what you’re doing! There is no need to change if it works for you. The rest of this article may still be helpful to understand how to standardize data stored in State and Country text fields.

Standardization is critical

Keeping org data clean is the driving force behind Salesforce’s decision to enforce State & Country picklists for the new field type. If you, like many others, have been excited to migrate away from five custom text fields to a single address compound field, then we’re going to have to standardize that data before the migration process.

The rest of this article will walk you through a fast and efficient way to standardize your existing data from within Salesforce using AddressTools Premium. We’ll cover two approaches:

  1. Create a standardization trigger leveraging AddressTools and run a “mass update” to execute the logic.
  2. Export a standardized list of address data ready for reimporting back into Salesforce.

Both approaches require the same initial steps for configuring AddressTools’ standardization functionality so we’ll start there and break out into the two options later.

The use case

The scenario we’ll be following will be looking at a custom object called “Warehouse”. The Warehouse object contains five custom text fields that when put together create an address. We will refer to these fields collectively as an “address block”.

The five custom fields are:

  • Street
  • City
  • State
  • Postal Code
  • Country 

The fields are populated from a number of different sources – web forms, integrations and user entries – so we cannot guarantee that the data is standardized. 

To prepare this data we’re going to expedite the process by using AddressTools Premium available on the AppExchange. As users (and developers) of the package we have heaps of experience and even some hidden tricks that’ll save days. It shouldn’t take more than a couple of hours from start to finish.

Installing the AddressTools Premium trial

If you’re not already using AddressTools Premium in your organization you’ll need to first install it from the AppExchange. You can do this in a sandbox if you want to test the functionality before pushing it to production.

Note: AddressTools Premium is a paid-for product that comes with a 14-day free trial. This could save you days of work so the cost may be something worth considering, especially if you have wider address requirements.

  • Go to the AddressTools Premium AppExchange listing.
  • Select Get It Now.
  • You may be prompted to log in if not already.
  • Select Install in Production or Install in Sandbox depending on your requirements. It is best practice to test in a sandbox before moving to production.
  • Agree to the terms and conditions.
  • Select Confirm and Install.
  • You may be prompted to log in again. If so, log into the org you want to install the package to.
  • Select Install for Admins Only.
  • Press Install.
  • Check Yes, grant access to these third-party web sites.
  • Select Continue.

Let the process install the package. AddressTools Premium has a lot of features so it may take some time to install (you may receive a warning saying it’s taking a long time, this is normal). When the package has completed its installation you’ll receive a success email.

Once the package has been installed, navigate to the AddressTools App (via the App Launcher) and open the AddressTools Administration tab. You’ll immediately be on the Installation sub-tab.

  • Under the Installation tab, select Create Token.
  • A green tick will appear next to the first step.

Next we’ll want to install the AddressTools Premium dataset. This is a list of countries, states, alternative names, ISO codes, (and heaps of other address-related data).

Warning: This dataset is large. Ensure you have enough storage available if you’re testing this in a sandbox. If your allocated storage is low or you are unsure you can select Only install sample data but beware this will not populate any alternative country and state values that will be used to expand the acceptable standardization data for countries and states. This can be manually added later if you so wish.

  • Under Data Installation, select Get Started.
  • Optionally choose Only install sample data.
  • Select Install.
  • A final warning will appear in relation to storage size. When you’re ready press Yes.

This may take some time and will preconfigure some functionality for your org. Feel free to continue reading this guide so that when you’re done you’ll be ready to rock.

  • Once the installation has finished, refresh the page to see that green tick.

Disabling the out-of-the-box functionality

A trigger is provided out of the box for the Account, Contact, Contract and Lead objects. If this is a fresh installation of AddressTools Premium in your org we’ll want to disable these triggers so that we don’t impact current business processes when we begin enabling functionality further down the line.

After the data installation:

  • Select Settings from the left navigation.
  • Scroll to Trigger Settings.
  • Disable each of the trigger settings in this section.
  • Select Save.

If the address fields you want to standardize exist on one of the four objects, the triggers can be re-enabled at a later point.

Configuring the address block

As mentioned earlier we’ll be referring to the five custom text fields as an “address block”. We need to configure AddressTools Premium with each of the text fields. This will allow the tool to execute standardization on the custom State & Country fields. 

  • On the AddressTools Administration page, select Address Blocks from the left navigation.
  • Use the Add button in the top right.
  • Select the object where your address block exists. We’re choosing Warehouse__c.
  • If you have record types enabled on the object, leave None chosen.
  • Select Next.
  • Under Postal Address Fields, select the relevant fields for each picklist:
    • Country
    • State
    • City
    • ZIP/Postal Code
    • Street

With the object and address fields now specified, it’s time to choose the settings we want to enable for the block.

Whilst still on the new address block modal:

  • Scroll down to Global Settings.
  • Check Standardize Country.
  • Check Standardize State.

Note: there are plenty of other settings here that may take your fancy. A tooltip is provided next to each giving you some insight into what’s available. You can come back to this page at any time should you wish to explore the other capabilities of AddressTools Premium.

  • We’ll complete this step by selecting Save.

Configure standardization values

Standardization is the process of converting multiple acceptable values to a single value. For example let’s take a look at the country Egypt:

  • Full name – Egypt
  • ISO-2 – EG
  • ISO-3– EGY
  • Local name (Latin characters) – Miṣr
  • Local name (Native characters) – مِصر

Each of the above values are technically correct entries for Egypt but a picklist won’t allow all of these values to be entered. Using a text field to accept all the variations of the country name will ease the stress for end users, integrations and streamline future expansions of your org. It’s then best practice to standardize the values to a single preferred format for analytical purposes after the data is inserted.

To identify the acceptable values for each country we’ll take a look at the Countries object installed with AddressTools. This is one of the objects that the data installation will have populated records for and is fundamental to the standardization functionality.

  • Select App Launcher.
  • Search and select Countries.
  • Select All from the available list views.
  • To help understand the data, select the United States country record from the list view.

Looking at the Country record, you can find dedicated fields for:

  • Full name
  • ISO-2
  • ISO-3
  • Local name (Latin characters)
  • Local name (Native characters)

The good news is that each of these field’s values are automatically configured to be accepted in text fields configured with AddressTools Premium. When the AddressTools trigger functionality is enabled the values will be standardized to a defined format on insert and update.

Let’s take a look at another example for acceptable data by talking about United Kingdom, or do I mean Great Britain, or England?… You get where I’m going…

State & Country picklists don’t support the inputs of these variations, and these variations also don’t fit into the five dedicated fields on the Countries object. This is where we introduce Alternative Country Names.

  • Whilst still looking at your existing country record, select Related.
  • Select Alternative Country Names.

This list may be empty depending on the country you’re looking at or because you only installed the sample dataset. Don’t worry, you can add as many records here as you find necessary. 

To add a new Alternative Country Name:

  • Select New.
  • Write the value into the Alternative Country Name field.
  • Ensure the Original Country field is populated with the Country.
  • Is Obsolete: Unchecked.
  • Select Save.

And it’s that simple, you’ve now added an Alternative Country Name that AddressTools will be able to identify during the standardization process.

The State object is configured similarly. To access States navigate to the related list on the Country record. For example, navigate to the United States Country record, select Related, and here you’ll find a list of states belonging to the United States. 

Each State record has a:

  • Full name
  • ISO code

An Alternative State Name object is available where you can add a list of acceptable values. After all, we can’t seriously expect all our users to spell Mississippi correctly every time… So practically speaking if there are common misspellings or abbreviations you find in your org you can add them here to be standardized.

That covers configuring all of the acceptable values. Now we need to define the formats for the data to be standardized to.

Defining the standardized formats

Whilst we’re still looking at Country and State record data, we’ll configure the State format first. 

This is managed on the Country record and can be controlled on a per-country basis. 

  • Navigate back to a Country record (i.e. United States).
  • Enable or disable Use Subcountry Code in State field.

This option can be enabled/disabled to standardize the state value to either its full name or ISO value (i.e. Texas vs TX).

Lastly, we need to define the Country format. This is an org-wide setting and applies to all country values.

  • Go to the AddressTools Administration tab.
  • Navigate to Settings in the left navigation.
  • Use the pencil icon next to Standardization Enabled.
  • Check Standardization Enabled.
  • Edit the Country Standardization Format to match the desired format.
  • Select Save.

Note: These settings can be changed at a later date if you need to change your format. You’ll then need to run one of the following jobs to standardize the data to the new format.

It’s configured, now what?

We have two options to mass standardize the data:

  1. Enable a trigger on the object, run a mass update and have the trigger standardize all the data during the update.
  2. Invoke a job via the Developer Console to export a standardized list of data that can be manually reimported into Salesforce.

Choose the approach that best suits you. If you’re unsure what route to take we have instructions below walking you through both.

Option 1: Create a trigger on the object and run a mass update.

We’ve configured all the standardization settings so now we need to tell the object to follow them. As we’re working with a custom object in this example we’ll need to create a new trigger in the org to invoke the AddressTools functionality.

A trigger is provided out of the box for the Account, Contact, Contract and Lead objects. Follow the relevant steps to enable or create a trigger for the object where your address block exists.

If you’re working with either of the Account, Contact, Contract or Lead objects:

  • Navigate to the AddressTools Administrator tab.
  • Select Settings from the left navigation.
  • Scroll to Trigger Settings.
  • Enable the trigger on the object you’re standardizing.
  • Select Save.

If you’re working with an object that isn’t Account, Contact, Contract or Lead:

  • Go to Setup.
  • Navigate to Object Manager.
  • Locate the Object you want to create the trigger for.
  • Select Triggers and New.
  • In the box, replace the existing code snippet with the following:
trigger ValidateOBJECTLABELCountryFields on OBJECTAPI (before insert, before update) {
    pw_ccpro.CountryValidator2.Validate(Trigger.new, Trigger.oldMap);  
}
  • Replace OBJECTLABEL with the label name of the object you’re creating the trigger for.
  • Replace OBJECTAPI with the API name of the object you’re creating the trigger for.
  • Select Save.

With the trigger enabled for the object, we need to turn on the standardization setting in the AddressTools Administration tab:

  • Navigate to the AddressTools Administrator tab.
  • Select Settings from the left navigation.
  • Under Feature Enablement, check the box for Standardization Enabled.
  • Confirm that the Country Standardization Format is set as you desire.
  • Select Save.

Before we do a mass update we can test the standardization functionality on our address block. 

  • Navigate to a record where your address block exists.
  • Edit the record.
  • Change the country text value to a variation of the value currently present (e.g. if the country is United States, change it to USA or US).
  • Save the record.

The record will standardize to the format specified in the settings. (If you entered the desired format, the value won’t change on save as it’s already in the expected format. Try changing to another format to confirm the test).

Before save:

After save:

Now the test has been confirmed we need to invoke the trigger on all existing records. This will involve running an update on every record in the object. There are many different ways that you can achieve this so if you can already think of one then do what you know best.

If you need some guidance, we have a separate article on how to run a “mass touch” using Salesforce Flows. Check it out here.

Once the mass touch operation has successfully run, all State and Country values that matched the AddressTools dataset will now adhere to your defined standardization format.

There may be some leftover values and this will require some manual intervention. If you find a repeat offender you can add the value to the Alternative Country or State Name objects and re-run the process to catch them.

Option 2: Export the standardized data for importing later

Before we start, it makes sense to see the result of these instructions so let’s take a look at what our exported file will contain.

For every record on the configured object that can be standardized, the data will be exported with the following data in the file:

  • Record ID
  • Current text field values (Old)
  • Standardized versions of the text field values (New). 

Note: The export will ignore records that are already in the desired format or that contain data that cannot be standardized (i.e. an unrecognized value).

To prepare AddressTools Premium to execute this export:

  • Navigate to the AddressTools Administrator tab.
  • Select Settings from the left navigation.
  • Under Feature Enablement, check the box for Standardization Enabled.
  • Confirm that the Country Standardization Format is set as you desire.
  • Add your email address to the Batch Verification Alerts Email Address field.
  • Select Save.

This process will need permission to send an email to the email address configured in the previous section. You may need to change your org’s Email Deliverability settings to support this.

To check/change your Deliverability settings:

  • Go to Salesforce Setup.
  • Search for Deliverability in the left search.
  • Select Deliverability from the left navigation.
  • Make note of your existing Access level, you can revert the setting back to this once you’re done.
  • Change Access Level to All email.
  • Select Save.

For some of you reading this guide, you may not have worked with the Developer Console before so follow closely and let’s execute some Apex! 

Note: If this is your first time we recommend doing this in a sandbox so you don’t affect any production data.

  • Go to the cog in the top right of your Salesforce page.
  • Select Developer Console.

The Developer Console window will open in a new window.

  • Select Debug | Open Execute Anonymous Window.
  • Under Enter Apex Code, type the code below 
pw_ccpro.BatchValidateAndGenerateCSV M = new pw_ccpro.BatchValidateAndGenerateCSV('OBJECTAPI');
Database.executeBatch(M);
  • Change OBJECTAPI to the API Name of your Object. We’ll be typing ‘Warehouse__c’.
  • Select Execute.

This will now begin the standardization process. The length of time it will take to execute will vary depending on how much data you have in your org.

Once the job is complete you will receive an email with a .csv attachment containing all of the standardized data from the address block ready for importing either into the existing fields or ready to migrate into your State & Country picklists. 

And there you have it – your standardized file is waiting for you! When you’re ready to import this data back into Salesforce, use an importing tool* of your choice and ensure to update the records matching the Record ID found in column A.

Warning: Be vigilant when running mass update operations in a production environment. Where possible backup your data first.

*Pssst if you’re looking for a new favorite importing solution, why not try out SimpleImport for this import job!

Summary

So there you have it, we’ve walked through how to standardize your existing data ready for the new custom address field type in Salesforce using AddressTools Premium.

If you have found this guide to be helpful, please ensure you share it with others so that they can learn how to standardize their address data stored in text fields. If it has saved you time then it may save them time too!

If you have any questions about AddressTools and any of its capabilities we’d love to hear from you. Get in contact with us at info@provenworks.com.

How to populate a state value from a US ZIP Code using a Salesforce flow

Reducing manual data entry results in better user adoption, less friction for prospects and overall a better user experience. 

In this example we are going to create a Salesforce flow that will fetch the State value from an entered US ZIP Code and populate the address’ state field. This removes the (often neglected!) requirement for end users to enter a State value at point of record entry. The ZIP Code data is part of AddressTools Premium which is available on the AppExchange.

Follow along with our step-by-step guide by installing a free two-week free trial of AddressTools Premium.

Create a flow to automate State population

  • Go to Salesforce Setup | Flow.
  • Select New Flow.
  • Choose Record-Triggered Flow.
  • Search and select the object that you are configuring the process for.
  • Set Trigger the Flow When to A record is created or updated.
  • Select Done.

Set entry conditions.

  • Condition requirements All Conditions Are Met (AND)
  • pw_ccpro__BillingCountryLookup__c Equals United States
  • BillingState Is Null TRUE
  • BillingPostalCode Is Null FALSE 
  • When to Run the Flow for Updated Records Every time a record is updated and meets the condition requirements
  • Optimize the Flow For Fast Field Updates 

The flow will now be ready to start adding elements to.

  • Select Get Records and drag it under the Start element
  • Label Get ZIP 
  • Object ZIP Code 

Set entry conditions.

  • Condition requirements All Conditions Are Met (AND) 
  • Name Equals {!$Record.BillingPostalCode}
  • How Many Records to Store Only the first record
  • How to Store Record Data Automatically store all fields 

Add another element.

  • Select Update Records and drag it under the Get Records element
  • Label Update Account
  • How to Find Records to Update and Set Their Values Use the account record that triggered the flow
  • Set Filter Conditions None-Always Update Record

Set Field Values for the Account Record.

  • BillingState {!Get_ZIP.pw_ccpro__State__r.Name}

Make sure the elements are connected and Activate your flow. 

Before:

After:

How can I run this for my historic data?

If you have existing records in Salesforce that you want to run this logic for check out our guide on how to run a mass update using Salesforce Flows.


AddressTools

Validate, standardize and verify your address data with our award-winning solution. Learn more and book a demo.

Verify addresses in a flow: Introducing the Address Verification Flow Component

Following Salesforce’s announcement that they will be retiring Workflow Rules and Process Builder, it’s clear that Flows are the future and the future is here to stay.

With that in mind, we are so excited to introduce our Address Verification Flow Component, now available on the AppExchange! Verify addresses in a flow using global postal authority data for over 240 countries.

Why should you verify addresses?

Did you know that verifying addresses up-front can reduce failed delivery rates by up to 70%? Improve customer experience and save wasted costs with verified addresses.

💡 Want to know more? Watch our 2 minute video: Why verifying addresses is important | Salesforce CRM.

Why should you verify addresses in a flow?

We’ve designed the Address Verification Flow Component to make it as easy as possible for Administrators to ‘hot-swap’ the vanilla Address component with our own component followed by a quick re-binding of any set flow variables.

So it’s easy to set up. How about some facts and figures too?

  • Create an exceptional user experience by reducing data entry time by 78% and errors by 20%.
  • Unlike Google, access global postal authority data such as Royal Mail, USPS, Canada Post for truly verified data, reducing failed delivery rates by up to 70%.
  • Autopopulate any address fields in 5 keystrokes or less.

The use cases

  • Digital Experience – Do you use an ecommerce checkout or a user registration portal? Verify addresses at the point of entry!
  • Internal Flow – Capture user addresses quick with type-ahead verified data. Perfect for Service Cloud users!
  • Endless possibilities – Wrap our solution in a custom Aura component for total flexibility!

Try out the Address Verification Flow Component

Why not start off with a free trial of the component?

  1. Install AddressTools Premium from the AppExchange (this is how you will manage your credit usage) 
  2. Install the Address Verification Flow Component from the AppExchange.
  3. Follow our brand new step-by-step setup installation walkthrough
  4. Drag and drop the component into your Flows and you’re ready to flow!

If you get stuck or have any questions, feel free to contact our Support team who are more than happy to help you: support@provenworks.com.

Interested? Chat to us

The Address Verification Flow Component is an extension of our popular solution AddressTools. Pricing of the Address Verification Flow Component depends on your use case. Get in touch with us to discuss your requirements and we’ll get you the most accurate information!

AddressTools: feature release for PowerSearch

Our team has been working on some really exciting feature releases for AddressTools that will make your PowerSearch experience even better!

What do I need to know?

We’ve added two extra features to PowerSearch’s settings to help specify and focus your searches, and optimize your address data entry.

Why should I be excited?

Select a priority country so that search results from the selected country will be shown first. Here’s an example of USA set as the priority country.

And/or, choose allowed countries, so that search results are limited to only the countries you select.

How do I access these new features?

Simply update your AddressTools Premium package to use these new features. You will need to use version 7.94 of AddressTools which you can find via the AppExchange.

Need an extra hand? Check out our 4-step guide on how to upgrade an AppExchange app.

If you have any further questions, please contact us!


AddressTools

Interested in learning more? Check out our award-winning package for Salesforce. Harness the power of address standardization, validation and verification in your org.

AddressTools Premium: Configure verification settings

Improving the PowerSearch results

PowerSearch functionality by default will search in over 245 countries up to the premise-level. Whilst powerful, this can lead to the results being diluted, especially if you know you are only working within specific countries, or have one country that you primarily work within.

To combat this, AddressTools has two settings to improve the results and customize them to your requirements.

  • Allowed Countries – PowerSearch address verification will only return address results from the listed countries. All available countries will be searched if this setting is left empty. You have the ability to choose up to 80 countries.
  • Priority Country – PowerSearch address verification will prioritize displaying results from this country.

To access these settings:

  • Go to App Launcher | AddressTools Administration.
  • Select Settings from the sidebar.
  • Click the pencil next to Allowed Countries or Priority Country.
  • In Allowed Countries, type and select the countries that your business will be verifying addresses in.
  • If your organization has a country that you’d like to prioritize in the search results, select this country from the Priority County picklist.
  • Click Save.

Note: these two setting will only impact PowerSearch address verification. Automated address verification relies on the country value entered in an existing address.

Batch address verification alerts

Batch address verification runs behind the scenes. This can be a fantastic option to automate address verification in your organization, however errors can happen! For example when a record is verified, an update will be pushed to the record when a result has been found. If, for whatever reason, this record cannot be updated, you need to know the operation has failed!

To ensure alerts are provided in the event of an error, a dedicated email address can be added to the AddressTools settings. By default the email address of the installing user will be populated in this field but you may wish to change this.

  • Go to App Launcher | AddressTools Administration.
  • Select Settings from the sidebar.
  • Click the pencil next to Batch Verification Alert Email Address.
  • Enter the email address to send the alerts to.
  • Click Save.

Note: your organization may be required to change the Access to Send Email organization setting to All email. This is located in Setup | Email | Deliverability.


Back to the AddressTools Premium installation walkthrough

Oxfam GB makes everyone a data champion with AddressTools

Thanks to AddressTools, we have supporter data that is accurate which results in a better supporter experience and a user base that is empowered to take ownership of data quality.

Philip Blaney, Solution Architect at Oxfam GB

Verifying and connecting with a clean supporter base means that Oxfam can focus on tackling poverty

Oxfam is a global nonprofit group of millions of people who share the belief that, in a world rich in resources, poverty isn’t inevitable. In just 15 years, extreme poverty has been halved. In 15 more years they believe they can end it for good.

The challenge: quality address data to match a quality CRM

Oxfam GB needed to ensure that the address data held in Salesforce for their supporters was accurate and consistent so that they could focus on communicating with their supporters, rather than worrying about whether it would reach them.

Oxfam GB were confident about the accuracy of the data they migrated into Salesforce from their old CRM platform. They needed to ensure that new supporter data entered was of the same standard. This meant storing consistent address data that was verified against the Postcode Address File provided by the Royal Mail.

The solution: empowering users to verify address data

With AddressTools, Oxfam GB has a solution that runs within Salesforce, integrating into each supporter’s record with a neat widget, showing at a glance if the address has been verified or not.

After an easy installation and setup, Oxfam GB has the flexibility to finetune their settings, making it as easy as possible for their end users to enter address data that is checked and verified.

The result: confidently communicating with supporters

Users across Salesforce can verify address data

“We have been able to empower our users across Salesforce to verify address data rather than it being tied to someone with elevated privileges or working in a particular team.”

Philip Blaney, Solution Architect

Reduced costs

Validating and formatting their address data means that Oxfam GB reduces overhead costs from undeliverable mail.

Trust in their CRM

Just as important, Oxfam GB has a supporter database they can trust. They can be confident that they connect with their supporters, knowing that their constituents will have a consistent experience.

A gift for Gift Aid

The Gift Aid process is a multi-million pound process for Oxfam and is underpinned by data quality, specifically postcode accuracy for UK addresses. AddressTools helps Oxfam keep any manual updates within this process to an absolute minimum (<0.05%*) enabling efficient and timely processing of Gift Aid claims.

(*0.05% based on 25 corrections per 50K records)

Why AddressTools?

“We have been really impressed with the team at ProvenWorks, they have been on hand to help out whenever we have needed them and the response is always swift, professional and friendly.”

Philip Blaney, Solution Architect


AddressTools for Nonprofits

Whether it’s connecting with a clean donor database, managing fundraising platform integrations or sorting out existing bad addresses, we’re here to help.

Got questions? Chat to us!

Do you want to learn more about how AddressTools could be a great addition to your Salesforce org? We’d love to chat! Use the scheduler to book a free call with our team and start your journey to better address data.

What are ZIP+4 Codes and why should you care?

ZIP Codes: a very brief history

ZIP codes, the postal code system used by the US Postal Service (USPS), were introduced in 1963. Their basic, and most familiar, format consists of five digits that indicate a specific delivery area. In 1983, the USPS introduced the extended ZIP+4 code.

ZIP+4 Codes

Also called “plus-four codes”, “add-on codes”, or “add-ons”, the ZIP+4 code starts with the standard five-digit ZIP Code. The four extra numbers are added after a hyphen to complete the ZIP+4.

So what do the extra numbers mean?

These last 4 digits represent specific delivery routes within delivery areas. This extra detail means an even more precise matching to a more granular level. It could represent a handful of houses on one side of a street, or even a single building that receives a high volume of mail.

So ZIP+4 Codes help the USPS more effectively sort and distribute mail. How does this affect you?

Why should you care about ZIP+4?

Faster deliveries

As we already discussed, using the ZIP+4 Code narrows down your delivery address to a handful of addresses. There are plenty of resources that suggest ZIP+4 accelerates the overall delivery process by one or even two days since it reduces the processing time needed at a mail center.

Reduced misdeliveries

As we already discussed, using the ZIP+4 Code narrows down your delivery address to a handful of addresses. There are plenty of resources that suggest ZIP+4 accelerates the overall delivery process by one or even two days since it reduces the processing time needed at a mail center.

Reduced misdeliveries

Delivery addresses do not require ZIP+4 Codes. However, ZIP+4 codes require an address to be first standardized and verified to exist. This means that an address with a ZIP 4 code can be sure to exist and therefore deliverable.

ZIP+4 Codes can change

Delivery addresses do not require ZIP+4 Codes. However, ZIP+4 codes require an address to be first ZIP+4 Codes are based on actual delivery routes. This means that they can change fairly regularly. Some resources state that the USPS can update a ZIP+4 Code as frequently as once in two months. However frequently or infrequently the case may be, it’s important to note that they can change. Sounds like you want some *cough* automated software to find that for you

Save money

The USPS discounts on bulk mailings if you do tasks that the USPS would normally do, like bundling mail, adding barcodes and, most relevant here, if you add the ZIP+4 Code extension.

PO boxes

If you frequently work with PO boxes, ZIP+4 Codes are incredibly useful. The USPS usually assigns each PO Box its own +4 Code, which matches the box number. In other words, the ZIP+4 Code will likely include the actual PO Box number in the +4 part of the ZIP Code.

Retrieve ZIP+4 in Salesforce

Now you know why you should care about ZIP+4 codes. The next step is how to start using them. If you use Salesforce then there’s some good news for you.

Easily retrieve the ZIP+4 for your addresses in Salesforce with AddressTools. Our solution includes US-specific interactive functionality to help you easily look up and verify full ZIP codes.

Book a free demo

We love talking about all things address related! See AddressTools, our address data solution that can retrieve ZIP+4 codes for Salesforce, on a free demo.

High Velocity Sales: save time and stay compliant

Sales reps only spend 1/3rd of their time selling

According to the third edition of the Salesforce State of Sales report, inside sales reps spend on average 34% of their days only selling. The rest of the time they’re busy seeking out prospects, planning tasks and entering data. In addition, reps end up using on average 6 different tools to manage their sales activity.

With this in mind, it’s clear that something needs to change.

High Velocity Sales: less admin, more selling!

Two of the main benefits of selling with High Velocity Sales are the Lightning Sales Console and Work Queues. With these tools you have highly tailored and centralized workspaces which enable your sales reps to view everything on one screen.

Reps can see and manage their work queue in one place whilst simultaneously viewing all of the relevant information related to the lead or contact. Viewing and interacting with tasks efficiently means more time selling!

See everything in one place with High Velocity Sales

How do sales reps know if they can call a prospect?

If you’re cold calling as part of your sales strategy, you need to be careful. The country you’re operating in might have a registry of numbers it is illegal to call. For example, the USA has the ‘Do Not Call’ registry and the UK has the ‘Telephone Preference Service (TPS)’. You can get hit with hefty fines for noncompliance.

If you don’t know about the Telephone Preference Service (and corporate equivalent), then don’t worry! Ruth, our Marketing Director, wrote up this really handy guide to tell you everything you need to know.

If you are up to speed, then ask yourself how efficient is your process? Your reps could be wasting a lot of time using an external service to screen numbers. And can you really trust that a process involving extra manual effort is actually being done?

PhoneTools provides manual and automated TPS and CTPS screening right from within Salesforce. This means sales reps can see at a glance whether the number is safe to call or not.

How do sales reps know when to call a prospect?

Having all of your sales information in one place is great, but it’s what your reps do with it that counts. This is where a nifty piece of AddressTools functionality comes in.

Reaching out to a prospect at 2am or scheduling a meeting without considering their timezone frustrates the client and leaves your sales reps feeling unproductive.

AddressTools is great for making sure your address data is verified, validated and standardized, but it also displays the current time to the sales rep. Best of all, it’s right there within Salesforce so no extra windows or manual effort for your sales team! This small piece of functionality can make a huge difference for both the sales rep and client experience.

High Velocity Sales: optimizing your sales process

In this article you’ve learned the importance of:

  • taking the time to review your sales process
  • cutting down on the number of different tools you need
  • keeping everything at your sales reps’ fingertips in Salesforce

What’s left? Make those changes and watch how you save time, stay compliant and ultimately sell more!

PhoneTools

Screen against the UK TPS and CTPS databases to stay compliant and avoid fines.

AddressTools

The award-winning package for address standardization, validation and verification.