© 2017-2019 Ashley Rossi

AGENT LOCATOR

The primary goal of the Agent Locator project was to provide users the option to locate, quote and purchase insurance directly through a local agent offering Hagerty products. A secondary goal was to boost SEO through geo targeted pages residing on the hagerty.com domain. This tool is widely available from the Hagerty website, appearing alongside the online Quote CTA on every page.

My Roles: UX, UI, IxD

 

Tools Used: Axure, Photoshop

Client: Hagerty Agent Team 

Who I Worked With: Project Manager, Developer, Graphic Designer, SEO Copywriter

DISCOVERY

There were two user types to consider​ when designing this tool: 1. The prospective client searching for a local agent, and 2. The agent him/herself. Each user type required a different user flow and interface.

EXISTING AGENTS

The database was to be pre-populated with existing agents who met a specified set of criteria (i.e. # of policies written per year as a basis for determining their activity level), then sent an email notification of their inclusion in the locator with options to view/manage their listing, update their contact information, or request removal from the directory upon account login:

PROSPECTIVE CLIENTS

Prospective clients would access the agent search page from the "Find local agent" link located alongside the primary Quote CTA button on every page of the hagerty.com website. The search radius default was initially set to 10 miles, and bumped to 25 miles post-QA:

In desktop and landscape tablet views, the search results were displayed in list format sorted by distance, alongside a corresponding Google map. In mobile and portrait tablet, the search results defaulted to list view with the option to toggle the map view:

500 TERRY FRANCOIS STREET SAN FRANCISCO

MON-FRI 7AM-10PM |SATURDAY: 8AM-10PM

I also needed to accommodate for scenarios in which 1. No agents were located within the user-defined or default search radius, and 2. No agents were located within the maximum search radius of 50 miles. These scenarios were handled via messaging on the search results page: