You can integrate BriteSuite policies with SmartyStreets to validate addresses and standardize them to USPS specifications. This also provides geocoding; geocoding refers to locations using latitude and longitude, which is more accurate than describing a location’s address with street names.
Geocoding offers several benefits:
- Makes risk assessment easier and more accurate.
- Pinpoints risk/asset locations.
- Enhances risk assessment accuracy for perils/natural calamities, such as earthquakes, floods, and hurricanes.
- Increases data management efficiency.
- Improves coverage pricing for local offices and consignments.
You have two options to implement SmartyStreets with BriteSuite:
- Use BriteCore’s SmartyStreets plugin to provide address autocompletion. If you choose to use our prewritten plugin, all you need to do is map your data (Step 2 and Step 3).
- You can write your own plugin using custom logic.
Our team provides data mapping as an additional service.
Plugins are currently available only in the quote flow for Auto policies.
To learn more about plugins, please refer to BriteCore’s plugins documentation.
This tutorial walks you through implementing SmartyStreets in BriteCore if you want to write your own plugin. It also helps you understand how SmartyStreets integrates with BriteSuite.
Autocomplete offers a type-ahead search when you type address line 1. A list of potential address values displays. Select one of the values and the rest of the fields are prefilled. You can then optionally add the apartment or unit number if applicable.
Multiple option selection
With multiple option selection, you will enter Address Line 1 and Zip Code. After typing in the initial information, press a button for a pop-up window to appear with the standardized addresses; then, select the correct address.
Longitude and latitude
With this option, there will be two fields available to return the latitude and longitude. The latitude and longitude fields are automatically filled once the address is entered. This field can be hidden from agents.
Set up SmartyStreets in BriteSuite
To set up SmartyStreets in BriteSuite:
Step 1: Contact the BriteCore Support team
Contact the BriteCore support team to install SmartyStreets on your site via BriteDeploy. You will need to provide your Vendor Security Key.
Step 2: Consider your configuration options
Consider your configuration options and fill out the SmartyStreets configuration questionnaire.
Step 3: Create the data mapping
Map the data from SmartyStreets to your Lines configuration. Take your specific user-defined fields from Lines and map them to the data you’re receiving from SmartyStreets (and back).
To learn more about how data mapping works in BriteCore, please refer to our data. mapping documentation.
Sample data for a POST/mappings request.
Step 4: Write the plugin
Important: If you’re using BriteCore’s SmartyStreets plugin, skip this step.
To write your own plugin, interface with our SmartyStreets API endpoints.
Add the following script to the header of your HTML file:
<script src="https://unpkg.com/@britecore/ui-plugins-client"> </script>
You can now use the BriteCorePlugin helper so your plugin can communicate with BriteCore:
Step 5: Host your plugin in a public location
If you’re using BriteCore’s SmartyStreets plugin, BriteCore hosts the plugin for you. Otherwise, each plugin is an HTML document rendered in a hidden iframe. BriteCore’s UI queries the plugins available and renders any plugin on the specified pages.
Since BriteCore’s UI runs in a browser, the request for the plugin must occur without credentials to a publicly available location, or BriteCore must host the plugin placing the HTML file behind our authentication.
Step 6: Register the plugin in BriteIntegrations
If you’re using BriteCore’s SmartyStreets plugin, BriteCore registers the plugin for you. Otherwise, you can register your plugin using our Plugin Manager web UI.
Sample plugin implementation code
Below is example code for how you can implement the plugin.
Note: Don’t cut/paste the code. It won’t run without inserting it into a build and manipulating it. Use this code as a reference.