Blog

Author: Anja Culverhouse

PhoneTools features in your Trialforce org

by Anja Culverhouse in PhoneTools Trialforce December 9, 2025

PhoneTools screens telephone numbers stored in your Salesforce org against the UK Telephone Preference Service (TPS) and corporate TPS (CTPS) databases – helping you to remain compliant with UK data-protection and marketing laws. 

If you haven’t already, get more information on the setup of your Trialforce org by reading the Introduction to your PhoneTools Trialforce org article.

Screening Statuses

Here’s a quick breakdown of the simple screening status PhoneTools provides for each number: 

  • Green – Not Listed   
  • Red – Listed   
  • Blue – Not Screened  
  • Orange – Due for screening  
  • Grey – Excluded from screening (due to a formula field)   

These statuses are displayed in the PhoneTools lightning record page component alongside each of the phone numbers that are configured for screening – additional information is revealed by hovering your mouse over the status icon. 

The status will show as Red – Listed if the number is found in either of the TPS and CTPS databases. This means the Green – Not Listed status represents the number not existing in either of the databases.

PhoneTools will populate a Next Screen Due date 21 days from the initial screening where the status will change to Due for screening to remind you to rescreen all numbers within the 28-day legal requirement. It is recommended to automatically screen records enabling the inbuild functionality. This will process all Not Checked/ Due for screening numbers at a daily time, or for further customisation you can create a Flow to programmatically fire screening. 

The Grey – Excluded from screening status only appears if there is a formula field present and the number does not meet the requirements to be screened with PhoneTools. For example, in the Trialforce org any Lead or Contact record without a UK address will be excluded from screening due to the formula field created.

Record Level Statuses 

Under the Contacts and Leads tabs in the pinned list views, you’ll see a ‘Record Screening Status’ which summarises the screening status for all numbers on that record: 

  • Safe to Call (not listed) – All numbers on the record are considered safe to call as they are not listed. 
  • Caution (partially listed) – The record contains both numbers that aren’t listed as well as numbers that are.  
  • Do Not Call (listed) – All numbers on the record are listed in either database 
  • Not Screened – The record contains phone numbers that have not yet been screened against the configured databases or are excluded. 
  • Error – There is an issue with one or more of the numbers that exist on the record 

These record statuses give you a quick overview. For a detailed breakdown of each status, use the Lightning component inside the record itself. 

What to do on your org

For some introduction tasks to get you acquainted with PhoneTools look at the Tasks to complete on your PhoneTools Trialforce org article. This will guide you through some of the basic features of PhoneTools using the preconfigured Trialforce org, looking at screening records, formula fields and batch screening processes. 

We hope you enjoy exploring PhoneTools and it gives you a clear understanding of how it will help you maintain compliance and manage your phone-based outreach safely and efficiently. If you have any questions or would like further guidance, our team is here to help. 

Introduction to your PhoneTools Trialforce org

by Anja Culverhouse in PhoneTools Trialforce December 1, 2025

The PhoneTools Trialforce org gives you a way to explore all the features of PhoneTools without the needing a custom installation or setup. Use it to evaluate how PhoneTools can help you manage phone number screening against TPS and CTPS databases in your Salesforce environment before committing to a full implementation.  

If you haven’t already, head to the Salesforce AppExchange and sign up for a PhoneTools Trialforce org to get started. 

How the org is set up

When you first log in to your Trialforce org, navigate to the Platform app shown below. You’ll see tabs for Contacts, Leads and PhoneTools Administration. 

We have pre­populated this org with sample Contacts and Leads (including telephone numbers) so you can begin testing right away. Make sure to select List View in the top right of the Contact page, similarly for Leads.

You can see all Contacts by selecting the “Contacts for PhoneTools Testing” list, similarly for Leads.

Feel free to pin these list views for ease, as they include a column for ‘Phone Screening Status’ so you can see immediately which records have been screened.  

We have also created three ‘Favourites’ – sample Contact/Lead records – so you can quickly access representative examples. These are accessed from the top-right of the screen in the dropdown next to the favourites star.  

Record Pages

When you open a Contact or Lead record, you’ll find the PhoneTools Lightning component in the top-right of the page.

Below the PhoneTools component are two information blocks that explain: 

  • How the PhoneTools component works, 
  • How the formula field is used to determine whether the record should be screened. 

The PhoneTools features are outlined in these information blocks, but if you would like an in-depth explanation take a look at the PhoneTools Features in your Trialforce org article.

PhoneTools Administration Tab

The PhoneTools Administration tab takes you to a Configuration sub-tab. You can see all the objects and fields where PhoneTools screening is enabled. There is also a reference to a custom formula field which provides exclusion from screening for records that meet given criterion.

There is also a Screening page (found along the top options) where you can set up scheduled or batch phone number screening jobs, along with viewing screening settings and credits.

Finally, there is a Help & Support page with links and FAQs. 

What to do in your org

For some introduction tasks to get you acquainted with PhoneTools look at the Tasks to complete on your PhoneTools Trialforce org article. This will guide you through some of the basic features of PhoneTools using the preconfigured Trialforce org – looking at screening records, formula fields and batch screening processes. 

We hope you enjoy exploring PhoneTools and it gives you a clear understanding of how it will help you maintain compliance and manage your phone-based outreach safely and efficiently. If you have any questions or would like further guidance, our team is here to help. 

Tasks to complete in your PhoneTools Trialforce org

by Anja Culverhouse in PhoneTools Trialforce

Now you have installed the PhoneTools Trialforce org, have a go at the following tasks to get to know the product using our preconfigured data. 

If you haven’t already, get more information on the setup of your Trialforce org by reading the Introduction to your PhoneTools Trialforce org article.

Task 1: Test the screening on record pages 

For this task find and click the Contact Leanne Tomlin from the favourites bookmark in the top right corner of the screen. 

In the PhoneTools Lightning Component located in the top right of the record page you can see the screening status for both Mobile and Business Phone numbers. 

For more information on screening statuses, take a look at PhoneTools features in your Trialforce org.

  • Hover over the blue icons to see the current screening status. 
  • Press Screen in top right corner of the component to screen both numbers. 
  • Now hover over the icons again to see the new screening results. 

You will see that the Mobile Phone number is ‘Not Listed’ on either TPS or CTPS databases so is safe to call. The Business Phone number is marked as ‘Listed’, and by hovering the mouse you can see it is not listed on the TPS database but it is listed on the CTPS database. 

Now try this out for the Lead Jim Steele, which can also be found under the favourites bookmark.  

  • Repeat the previous steps on the Phone number: look at the screening status, press Screen, then look at the new screening status. 

You will see that this number is marked as ‘Listed’, where it is found on the TPS database but not the CTPS. 

  • Edit the record by changing the phone number to 07700 900123. 
  • Notice what changing the number has done to the screening status. 
  • Now click Screen on the record and check the new status. 

Adding or updating a number will automatically reset the screening status to ‘Not Screened’ so it will need to be screened again. 

Task 2: Testing the formula field 

Details on the formula field used in the Trialforce org can be found in the “PhoneTools Formula Field” information block along the right side of the record page. 

For this task, find and click the Lead Andy Smith in the favourites bookmark. 

  • Notice the screening status for this Phone number is Excluded from screening and hover over the icon to see a Next Screen Due field is not relevant in this case. 
  • What happens when you press Screen? 

You will notice that the component will not screen numbers which are excluded so the status will remain unchanged. 

The Phone number in Andy Smith’s record is excluded because of the formula field placed on the Lead Phone in this org.

For the purpose of seeing how a formula field works, we are going to change this Lead to comply with the PhoneTools formula conditions in place:

  • Edit the Lead Address Country to United Kingdom. 
  • See how the screening status has changed. 
  • Now press Screen and look at the new screening status.

After Screening, the Phone number is shown as ‘Not Listed’ (this makes sense as is not a UK number), the formula had saved an unnecessary screening of a non-UK number which would not have been on the TPS or CTPS databases. 

Task 3: Batch phone screening 

For this task you will have a brief look at how batch phone screening can be implemented, and test this on the Contact and Lead phone numbers preconfigured in the org. 

  • Go to the PhoneTools Administration tab.
  • Select the Screening tab along the top of the page. 

In a production org when you want to automate screening of numbers – you can set up a ‘Scheduled Screening’ which will process all ‘Not Screened’ or ‘Due for Screening’ numbers at a daily time. 

For now we will test an immediate batch job – useful if lots of new numbers have been added to your org at once. 

  • It is good practice to check the count first to see how many numbers are due for screening: press Calculate Now next to Screening Count. 
  • The Screening Count now shows you each object with the relative Qualifying numbers and Due numbers. 

The Due number indicates how many numbers would be processed if a batch screening job was run.  

You will notice that the Due number is lower than the Qualifying, this is because you have already screened some numbers in the org, so they do not need to be screened again until 21 days have passed. 

To start the batch job and screen all the Due phone numbers:

  • Next to Batch Screening select Screen Now 
  • This will show you the Object and related Processed jobs in real time throughout the batch job, ending with the Total job count and showing any errors and further details. 

At the end you will see that credits remaining, shown at the bottom of the page, has decreased from the original 250.  

Look through the Contact and Lead tabs to see the new screening statuses of all the records. Where the record still says ‘Not Screened’, view it to check that specific Contact/Lead is excluded from screening by the formula field. 

Note: for easy viewing select List View in the top right and then choose “{Object} for PhoneTools Testing” and pin this list – as this includes the Phone Screening Status in the list view.

For further exploration of the tool, feel free to add your own Contacts or Leads and play around with all of the features. 

How to: Configure functionality for a Custom Address block

by Anja Culverhouse in AddressTools Support October 1, 2025

This article will cover how to create and configure your custom address block with AddressTools allowing for all trigger based and interactive functionality. 

Note: Custom address block functionality requires AddressTools Premium. If you use AddressTools Free, start a Premium trial.  

In the following example, we will be covering how to configure a custom address block that we have created on a custom object that uses individual custom fields for each address field. The same steps can be used with a custom address field type; however we recommend using individual field elements due to the limitations that Salesforce State & Country/Territory picklists enforce.  

Task overview: 

  1. Create the address block fields on the object.
  2. Create the address verification fields (Premise-Level only).
  3. Configure the address block and verification in AddressTools.
  4. Create the custom trigger.
  5. Optional: Add the override component.
  6. Optional: Add the on page component.

Create an address block in the custom object

The following steps assume you are taking the approach of using individual fields for each address element. It is recommended to review this step even if you have already created your address fields. This is the ensure each field is of the right type before moving forward with the rest of the configuration.  

  • Go to Setup | Object Manager | [Your Object] | Fields & Relationships.
  • Select New to create each of the following address block fields: 
    • Street – Text Area (255).
    • City – Text (255).
    • State – Text (255).
    • Country – Text (255).
    • Postal Code – Text (255).

Create address verification fields (needed for Premise-Level)

If you want to utilize address verification functionality with the new address block, you will be required to create an Address Status field at a minimum. For optional fields such as County or Address Label that are also populated when using Address Verification, see the article: Creating additional fields for address verification.

  • Go to Setup | Object Manager | [Your Object] | Fields & Relationships. 
  • Select New.
  • Choose the data type: Picklist.
  • Select Next.
  • Add a Field Label (we suggest the address type plus address status, i.e. Billing Address Status) 
  • Select Enter values, with each value separated by a new line.
  • Add the following values to the text area: 
    • Not checked *mark as the default value 
    • Not matched 
    • Parsed but not found 
    • Ambiguous
    • Verified 
  • Uncheck Restrict picklist to the values defined in the value set. 

  • Select Next.
  • Provide visibility to all the users who will be verifying addresses, this can also be handled in a permission set afterward if preferred. 
  • Select Next and Save.

Configure address block and verification.

With the objects and fields created, it is now essential to map them with AddressTools via the Administration page. 

  • Go to App Launcher | AddressTools Administration | Address Blocks.
  • Select Add, choose [Your Object] from the dropdown.
  • If you desire functionality on a specific record type, choose the record type from the options. Leaving this blank will apply the functionality to all. 
  • Select Next.
  • In Postal Address Fields, complete each dropdown with the corresponding API name from your object.
  • In Additional Address Fields, complete the Status Field (and any additional fields) by choosing the corresponding object API name from the dropdown. 
  • If necessary, in Address Verification Options, select Enable Premise-Level Address Verification.
  • Enable settings as required for the address block and Save. 

Create custom trigger

A trigger is required on the objects that contain address fields that are configured with AddressTools. Without the trigger, most functionality will not fire and other functionality may appear to not behave as intended. 

  • Go to Setup | Object Manager | [Your Object] | Triggers. 
  • Click New to create a trigger. 
  • Replace the default code in the text field with the following code snippet: 
trigger ValidateOBJECTLABELCountryFields on OBJECTAPI (before insert,
before update) { 
   pw_ccpro.CountryValidator2.Validate (Trigger.new, Trigger.oldMap);
}
  • In this code snippet, replace OBJECTLABEL with the object name and OBJECTAPI with the correct API name. 
  • Save your new trigger. 

How to add the override component 

The AddressTools Override component is an advanced lightning component built to replace the standard “New Record” popup that your users experience when creating a new record in Salesforce. 

To override the New Record model in Salesforce Lightning: 

  • Navigate to Setup | Object Manager | [Object to override] | Buttons, Links and Actions. 
  • For the New button, select the arrow to reveal options and choose Edit. 
  • Set Lightning Experience Override to Lightning Component. 
  • Choose pw_ccpro__AddressToolsOverride from the picklist. 
  • Select Save.

Repeat the above steps for all of the objects you want to override the new record model with. 

How to add the on page component 

The AddressTools Record Page Component is your one-stop widget for handling anything address related on a record. The component is designed to sit on a lightning record page where an address block exists giving your users quick access to everything they need without distraction. 

To add the AddressTools Record Page Component to a lightning record page: 

  • Navigate to Setup | Object Manager | [Object] | Lightning Record Pages. 
  • Select New or if a Lightning Record Page already exists, select Edit. 
  • Drag the AddressTools Component from the components list onto the layout. 
  • Choose the Address block. 
  • Optionally, type into the Component header title to add a custom title. 
  • Select Save.

If the page has not yet been activated, a prompt will appear asking you to activate it. Follow the steps below to assign the page in the organization. 

  • Select Activate.
  • The page can be assigned based on different levels, for example set the Org Default by pressing Assign as Org Default. 
  • Review the page assignment changes. 
  • Select Save. 

How to: Solve “Address verification returning ‘Verified’ with a warning symbol”

by Anja Culverhouse in AddressTools Support September 5, 2025

If there is a warning symbol when an address is “Verified”, it is usually because the AddressTools trigger isn’t enabled for the object. Standard objects can use the built-in triggers, while custom objects will require a custom trigger. 

How to fix it? 

  1. Enable the provided trigger for standard objects: Account, Contact, Contract, Lead, or;
  2. Create a trigger for custom objects. 

Step-by-step resolution guide: 

1. Turn on triggers for supported standard objects.

  • Go to AddressTools Administration | Settings. 
  • In Trigger Settings, select Enable {Object} Trigger and save.  

Note: supported objects are Account, Contact, Contract, Lead.

2. Create a trigger for a custom object. 

  • Go to Setup | Object Manager | [Your Object] | Triggers. 
  • Click New to create a trigger. 
  • Replace the default code in the text field with the following code snippet: 
trigger ValidateOBJECTLABELCountryFields on OBJECTAPI (before insert,
before update) { 
   pw_ccpro.CountryValidator2.Validate (Trigger.new, Trigger.oldMap);
}
  • In this code snippet, replace OBJECTLABEL with your object name and OBJECTAPI with the API name. 
  • Save your new trigger. 

 

If you are still experiencing issues and need assistance, contact support@provenworks.com. 

How to: Solve “Report isn’t visible for selection in the Batch Address Verification app”

by Anja Culverhouse in AddressTools Support

If a report isn’t visible within the Batch Address Verification app, this is usually due to the report being saved in the wrong folder or the report is missing the Record ID field.

How to fix it?

  1. Save the report in the AddressTools folder. 
  2. Add the Record ID field to the report. 

Step-by-step resolution guide:

1. Make sure the report is saved in the AddressTools folder.

  • Go to Reports | [Your Report] | Edit. 
  • In the dropdown next to Save, select Properties. 
  • Under Folder, choose Select Folder. 
  • Go to All Folders | AddressTools. 
  • Click Select Folder at the bottom of the page, then save. 

2. Include the Record ID field in the report.

  • Go to Reports | [Your Report] | Edit. 
  • In the left sidebar, select Outline. 
  • In Columns, add the relevant {Record} ID (e.g. for Accounts add Account ID). 
  • Save the changes making sure it is in the correct folder from Step 1. 

If you are still experiencing issues and need assistance, contact support@provenworks.com . 

How to: Solve “US states are standardizing to full names, but should use ISO codes”

by Anja Culverhouse in AddressTools Support

This typically occurs when the United States country setting is configured to use state names instead of codes, or when state standardization isn’t enabled for the address block.

How to fix it?

  1. Set the United States to use ISO state codes at the country level. 
  2. Turn on Standardize State for the specific address block. 

Step-by-step resolution guide:

1. Configure the country to use ISO codes for states. 

  • Go to AddressTools | Countries.  
  • Select All and find the relevant country from the list (United States). 
  • In Preferences, select Use Subcountry Code in State field and save.

2. Enable standardization on the address block.

  • Go to AddressTools Administration | Address Blocks.
  • Click  Edit next to the relevant object’s address block. 
  • In Global Settings, check Standardize State and save. 

If you are still experiencing issues and need assistance, contact  support@provenworks.com. 

How to: Solve “Country isn’t standardizing to the full name when saving a record with AddressTools”

by Anja Culverhouse in AddressTools Support September 4, 2025

If the country value doesn’t standardize, it’s usually because the AddressTools trigger isn’t running on that object or standardization isn’t enabled for the package or address block.

How to fix it?

  1. Enable the trigger for your object.
  2. Turn on standardization and choose your country format.
  3. Turn on Standardize Country for the specific address block.

Step-by-step resolution guide:

1. Make sure the AddressTools trigger is on for your object. 

2. Turn on standardization and choose the country format. 

  • Go to AddressTools Administration | Settings.
  • In Feature Enablement, select Standardization Enabled. 
  • Set Country Standardization Format to Name (or other choice) and save.

3. Enable standardization on the address block. 

  • Go to AddressTools Administration | Address Blocks. 
  • Click Edit next to the relevant object’s address block.
  • In Global Settings, check Standardize Country and save.

If you are still experiencing issues and need assistance, contact support@provenworks.com.