Creating Address Lists

Address lists can be useful tools for users, but poorly planned address lists can be frustrating. Before you create address lists, make sure that they will make sense to users. Avoid creating so many address lists that users are not sure where to go to find a recipient. Consider surveying users to learn how they would interpret your proposed address lists. Finally, name your address lists in such a way that when users glance at them, they know immediately whom they can expect to find. If you are not sure, have fewer address lists, and remind users that they can find anyone in your organization by using the global address list. For detailed instructions on creating an address list, see How to Create an Address List.

When you plan your address lists, consider whether to use subcategories. For example, you may want address lists for both city and state, with city being a subcategory of state. Notice that both New York and Washington have cities named Auburn. When the query for Auburn, New York runs, it first finds all recipients with the state attribute New York, and then queries the result list (all recipients in New York) for all recipients in Auburn. In this way, you establish different lists for Auburn, New York and Auburn, Washington.

Address lists with subcategories

To additionally simplify the user experience and organize your lists, you may want to create an empty address list. Because no query has been created for an empty address list, it returns no recipients, and serves strictly as a parent container that organizes other lists. In the previous example, you may create an empty address list named States.

Adding an empty address list